honr

I'm not sure about the genetics of it (none of my family members seem to agree with me), but I also perform computer tasks far better in a dim light. A friend of me, who is also a night-owl, has the theory that when we get exposed to daylight, our cavemen heritage's natural reaction is to feel like going hunting/food gathering. While I don't buy the argument verbatim, I feel more like doing outdoor/physical activities on sunny days.

I kept seeing the following problem with several different LED lights we were installing until I found one that was better: Take your phone and take a video of the lights when on (normal framerate should be enough, try slow-motion for further investing). Most lights I got from the local hardware store were flickering quite visibly. And I'm pretty sure it's a design insufficiency of the adaptor electronics attached to it, not the LEDs themselves. If I were to guess I'd say most of them probably go the simple path of cutting off the negative half of the AC cycle and feeding the rest directly, without a decent low-pass filter to the LEDs.

What worked reasonably well for me, was getting a normal DC power supply and a few LED strips (with fairly dense and higher power LEDs) and installed that in a room. That light feels pretty satisfying to me.

All that being said, I don't like anything even remotely close to daylight level ambience when I am working on a computer screen; the custom lighting I set up is for other living areas.

Not really surprising to some of us. Definers Public Affairs and a couple of other firms have been working hard for it. At some point the hacker news community might become more immune to paid-for opinion shaping, but that time is not now.

So, I couldn't understand what "exposed" means in that article. Was any user's data obtained by someone not authorized to do so, or merely access to the data was possible?

Perhaps a correction, if we are talking about the phrase "don't be evil", literally, I can see it on: https://abc.xyz/investor/other/google-code-of-conduct.html

Perhaps "erased" is not quite accurate.

Compared to tilting my head to the second monitor, it is measurably faster to type ^3 (Control + 3) to switch to the space/virtual-desktop where my email window is open (~1.5sec vs ~0.7sec).

If one has to Alt+Tab or Command+Tab through programs, yes, that would suck the life out of productivity.

The only real benefit larger screen spaces (larger than a ~30 inch monitor) provide me with, are when I need about 4-6 open windows (maximized vertically) to switch between when dealing with large merges/patches. I haven't experienced any practical benefits beyond two ~30inch monitors.

Please kindly cut the BS and use the link and title of the study. The magazine it's published in seems to be the second highest impact magazine of its field (sorry I haven't done research in cellular biology to know the magazine well). So, the study is probably reasonable. The click-baity artistic interpretation of the study is what tarnishes this and numerous other works.

"Dietary fat, but not protein or carbohydrate, regulates energy intake and causes adiposity in mice."

https://www.sciencedirect.com/science/article/pii/S155041311...

Some of us do not subscribe to the "ends justify the means" theory. And with that, I'd consider this example a form of failed journalism. Regardless of whether or not there is actually an underlying point, this particular piece of pseudo-journalism didn't capture it. I chuckled when I read the author's description of himself/herself: "... who does extensive research into spreading technical awareness ...". One might think with the extensive research they have done so far, some of that technical awareness should have had reached the author, themselves.

I have used ports (if that is what you are referring to) albeit on a mac. It is very basic, without any of the interesting properties that make nix interesting. It essentially feels like a slightly improved "download && ./configure && make && make install" script.

As someone who hasn't actively used nixos (yet), only nix (the package manager) for a while:

I have always been curious and dumbfounded why he (Eelco) abandoned Maak (his build system, that I thought, would go together with nix). I think a proper, integrated build system (integrated with nix, the package manager) is a (or the?) missing piece to improve software development.

This sounds like a much better approach than our current "No V-Tech". Thanks for posting.

As I mentioned, I AM already using Google Fi on my iPhone. What does not work is the hardware feature of handing off between providers mid-flight. With my [now deceased] Nexus X, a call would seamlessly [to me, anyways] switch between providers during medium/longer commutes. With my iPhone using just T Mobile, calls get dropped during my daily route as there are certain "T Mobile blind spots".

I have to research deeper to be sure (there is some FAQ at https://fi.google.com/about/faq/#supported-devices-7). But skimming through that page, I suspect this is a new-ish feature not available on most smartphone radios.

This sounds a bit misguided. IIUC, Google Fi is really a mechanism of accessing two carriers from the same device. It consists of 1. A partnership between Google Fi (the cellular provider), T Mobile, and Sprint, and 2. A special radio hardware on the phone that is capable of working with two different "channels" at the same time. Since my Nexus device broke, I have personally been using "Google Fi" (the provider) on my iPhone which means I do NOT reap the full benefits of Fi without having the special radio hardware.

So, I don't think it is physically possible to do the "two provider at the same time" thingy without a special hardware (you'd need two parallel "radio" circuits on your phone).

And with that, your analogy falls sadly on its face, as you seem to indicate an artificial "software" limitation has been set to prevent us from using Google Fi on our iPhones.

I believe that is only in passing. I honestly think the majority of laptop manufacturers are not visionaries when it comes to product specs. Only Apple and a couple of niche ones truly seem to know what they are doing. The rest will have a delay to see the change in trends (but they do eventually see it).

I think consumer masses moving away from the laptop market has a dire implications for this market (far less competition, expect premium prices). But on the plus side it should shift the market towards productivity, which is a big plus for some of us.

I agree with most[1] of the issues he is aiming to solve. But the approach would have been useful if he would have built it on top a superior existing system which is Nix & NixOS. Docker is increasing popular while missing most of the problem NixOS (and the new vision of systemd) solve, so I'd say it is not wrong to assume there is definitely solid demand for this kind of app "packaging" (virtualization).

Tying this to systemd is an "interestingly" bold move, to put it mildly. People don't switch to btrfs just for the sake of an initrd replacement, after all, and forcing them is openly asking for replacements. So, I would be very careful if were willing to see that vision materialize.

[1]: One obvious point of discussion is declaring exact versions of library dependencies, which in most systems leads to highly undesirable results: just compare the horrible world of maven packaging (i.e., the java world, mostly) to the efficient (but curated) world of debian packages. But when you have exact declarable dependencies (where any dependency dictates exact versions of its own dependencies), and reliably reproducible builds (the game changing factor), and hopefully some level of automated testing, you will be fine: You can quickly upgrade all your package portfolio to the newest version of the "security fixed" library, have the world get rebuilt against the newness, and get everything verified (using the tests that you have. You have some, don't you?). The problem of transferring only what actually changed is non-trivial but completely solvable in various ways (Example: only send diffs, and issue new encryption/hashes for the diffs through an automated trusted system that does the diffing).

You should probably do some research and find out what language(s) you like (note: there are many languages and stacks outside the MS ecosystem, some of them might be far more fulfilling than what you have experienced so far). In particular, take a look at functional languages and see if you like them. Look at some dynamic languages and see if you get happy with one. Also play with some properly typed languages (ML family and Haskell, for instance) to see how those fair. Then also consider C++ (the widely used, but frankenstein-style language) as it is not as horrible as it used to be. Some new languages might be fun too (I'd suggest looking at Rust, Go, and Clojure). Once you've done that, you can probably have a better picture; without looking at all these, you might be or feel missing out.

That all said, and as you might have already heard, the MS ecosystem is not as wide as many of these, but it is far more unified than most other frameworks.

My own opinion is that you will miss out on new price and competition that is happening outside the MS world, so I recommend having some hands-on experience there if you are serious about starting your own business.

Awesome dashboard and project! Bookmarked to come back to it and use it :-)

P.S.: Wish the title was not so poorly chosen. Remember that title really does matter when submitting anything to Hacker News.

The regulation you mention here is certainly outdated NOW, but when it was passed it was a very pragmatic decision.

The anti-bloatware law is more than welcome, because competition keeps failing to reach the desired outcome. Regulations are exactly the right thing to do when competition and market fundamentally fails to reach what constitutes sanity, and converges to a local minimum.

Needless to say, such regulations should certainly be revisited when the root cause vanishes.

I have yet to find a useful feature that I don't already get in bash (assuming you are capable of sudo apt-get install bash-completion).

Fish (that I don't use regularly), however, has useful features.

> If/when viable alternatives to petroleum fuels are available, the transition will happen.

"Are available"? You seem to misunderstand how things become available. Usually people spend time and effort to make them available. Financial incentives makes research departments and universities spend time on it.

> Companies like Tesla and every major automobile manufacturer have R&D going on in this area right now.

Surely that has not been enough.

> Grabbing $2 billion via a new tax on oil production will do nothing to further that, however.

"nothing"? You are horribly mistaken here as well. Progress is the direct result of people doing research. $2e9 pours many more researchers on the problem. I am curious to know how much R&D money has been spent on improving batteries in Sony, Apple, Tesla and other manufacturers altogether.

> Look at results of similar "stimulus" spending a few years ago.

Usually "quickly grab this money and do research" is less efficient than organic research. So, it all comes down to how the stimulus plan is executed. Nothing is wrong with the whole idea, though.

I agree. C is outdated and does not represent current machines very well. Nor does it benefit from fruits of years of programming language research. Different layers of cache? Multiple cores? Stream processing? A type-system that is the equivalent of stones and sticks in the age of guns? The joke of "macro"-system that is a miniscule improvement over sed expressions in your Makefile?

However, it is here to stay, just like Inch, Foot, and Fahrenheit. Not that the alternatives are worst, just the cost of switching over and training a whole lot of people is back-breaking.

Note that most unfortunately, it is being taken over by javascript (false == '0'), which is a far worse language in many aspects.

They do slightly different things. I think each can benefit by incorporating the main idea of the other:

- Working on multiple projects who need different JVMs running at the same time can be a hassle in clove (you have to create a service for each), so it can be fixed by doing that the same way drip does.

- Running scripts and having a persistent JVM is still very useful, and clove (albeit I haven't cleaned up its code properly) gives a terminal into the JVM, really fast. So, drip can use the same technique (passing capabilities; a *nix feature) to let you hook into a JVM very quickly. [see the "screenshot" part at the bottom of http://hovel.ca/clove]

Interesting idea (especially, hashing based on command line options, and probably also the libraries in the classpath); I should add this to Clove (http://hovel.ca/clove : a small persistent-jvm that I wrote for *nix, with VERY fast connection time, e.g. suitable for scripts; sorry for shameless plug).

Yes, Like IntegerFloatAdding. If a programming language needs a pattern for adding an integer and a float, well, you have to call this pattern something. Until such a language is made, we can forget about "IntegerFloatAdding Pattern".

I think wise people prefer programming in good languages that enjoy the benefit of hindsight. Common Lisp does not have the luxury of hindsight, and can hardly change its specification to reflect modern theoretical and practical PL results.

Personally, I slightly prefer Clojure over SBCL.

I think tools that generate or pass records or rows of data should certainly have the option of providing a schema based output as well. In addition to "find ... -print0" providing either of "find ... -proto" or "find ... -json", assuming the schema for the json is known as in a /usr/share/SOMEWHERE/find.json-schema or similar, is really appreciated. And let's not go overboard with this, as there are many cases where parsing is genuinely the sanest approach.