HN user

random_mutex

13 karma
Posts1
Comments31
View on HN

I find the error story a horror one, mainly because it's quite easy to omit an error check when the err variable is reused which leads to weird crashes and garbage data, same happens when the error is explicitly ignored.

I wouldn't call tuples or error types weird, they're just poorly designed under the pretense of keeping the language (and first of all the compiler) simple.

It's not Go who popularized channel based concurrency, it's Erlang and Elixir.

In TypeScript or Python or any other language with unchecked exceptions you will rethrow and very likely the exception will be caught by te runtime when you least expect because someone else didn't bother handling it.

You failed to answer my question. Again is there a benefit to tricking your body that you are eating a meal which provides a high amount of energy?

Sugar isn't bad, it is a biological solution to the energy storage problem just like fat, and our bodies know how to deal with the sugar present in nature (in fruits). The sugar in an apple is absorbed slowly, without a dramatic increase in blood glucose unlike the one in a Coke can.

Is there any benefit in using sugar replacements? When you eat something sweet your body prepares itself for the sugar intake which, in the case sweetener usage, t never comes. What are the long terms effects of this imbalance? Let's assume your organism addapts to this situation and at some point you consume something that contains actual sugar, how will it respond to that?

One "meta feature" that was dropped was the ability to build the editor with or without different features. vim --version shows a long list of +/- features, neovim doesn't do that.

What's wrong with all features enabled by default?

I'm sure neovim dropped a lot but I don't have the full overview.

https://neovim.io/doc/user/vim_diff.html

Prominently it dropped support for giving !commands access to the actual tty. Commands that access the tty have to be used through the command :term instead.

Why would you run an interactive command with `:!` ?

Chromium devs create flags that break hw video every few months or so (and when the flags break you are forced to go on a random easter egg hunt to find out how to make hw video work again) and currently has a bug that leads to a memory leak. Sigh.

The Xorg leak was awful, it took me three days to find its cause.