ff_

Those projects are in good hands!

There are a few of us still at it :)

Though with the advent of LLMs it became very easy to spin up alternate backends for it, so it's very much alive outside of JS as well.

second paragraph of the article starts with:

> The sector contributed 0.25% to GDP and enabled savings on consumers' electricity bills of more than 4.6 billion euros in 2024, with an average reduction in the wholesale price of close to 20 euros per MWh.

(in mice)

To yourself - the code you just merged is now yours to maintain

Fresh pasta is an entirely different beast from dried pasta, so the two are hard to compare. I never made dried pasta at home, but I find it impossible (even in Italy) to buy fresh gnocchi that are as good as the ones that you can make at home.

I am all for improving the conditions so that signs can be removed (and this is valid with code too, e.g. a strong type system removes the need for a lot of documentation), but again we should not advocate for not documenting things, that's just asking for trouble.

And speaking of signs, we definitely don't have a good balance there either - in some places I experienced confusing situations where adding a few more signs could have helped.

Sure, but then the advice we should give is "please please document the WHY", rather than "stop commenting"

In any case, I personally find it very useful when I come to a new piece of code to find comments that summarise what it's happening in a few words without having to parse 10-100 lines of dense implementation - I have so much cognitive ability I can apply in one day, and any effort to optimise its usage should be welcome

"Remove half of the signs, they become outdated whenever we change the roads"

Software is written by humans for humans, and documentation is a fundamental part of it, and needs maintenance just like the rest. It is beyond me why one would want to maintain only half of the thing and say "discard the rest"

In all the Haskell teams I worked in, the candidate knowing Haskell was rarely a significant advantage (except for cases where the most experienced Haskeller leaves, and then you need to hire someone to direct your GHC-internals questions to).

If you are interested in a job using a functional language you can pick basically any of them and then jump ship to a different one. I wrote Clojure for many years before switching to Haskell.

> As for myself, I think what foods I choose to consume are none of the government's business

There is a difference though: it's not about choice as much as it is about "good defaults". As a state you should want your folk to have better food, but if some person wants the choice of micromanaging their diet then sure, go ahead.

I shouldn't be struggling to find non-processed food in a supermarket. This is often the case right now, which is why I would very much welcome some more regulation on this.

This game is very good, congrats!

I would like to play more, but the games seem to be unreliable - the moves from my opponents stop getting through at some point, typically after a few moves.