First class effects and type system enforced purity have made my life as a programmer so much better. They dramatically reduce the size of the state space that must be reasoned about, and having all context being declared in a function definition makes it trivial to really grasp what any given function does.
I do agree with the points about language extensions (and I have certainly cursed my fair share of operator heavy point free code), but until someone makes something better (maybe that thing is even lean4?) Haskell still brings me more joy than any other production ready programming language.
Both Haskell and OCaml are fantastic. It is really astonishing the degree to which advancement in mainstream programming languages these days is just copy pasting ideas from either.
I don't think they really "want" you to die; it's just that their priorities do not align with your well-being. Consequently, their actions negatively impact the welfare you could have enjoyed if this power structure prioritized your needs more. Allocating billions to Ukraine and Israel doesn't necessarily directly worsen your situation per se, but it is one of the reasons why the state can only provide $750 USD to families affected by Hurricane Milton if they applications go through.
I don't think the hurricane Milton support has any relation to arms funding in Ukraine and Israel.
The hurricane victims don't get money because Americans don't want the government to pay disaster assistance, and military aid is given because Americans like buying guns.
You could drop military spending to zero, and there would still be peanuts paid out for disaster relief.
There is some limit where the US runs out of money to spend on anything, but we're already long past a balanced budget, and instead the government spends whatever it wants, and the debt ticker goes up
And it was just high inflation (albeit still lower than the inflation in other countries). Not the depression Weimar Germany had experienced in the late 1920s and early 1930s.
I find the nix language to be quite pleasant. There are some syntax quirks and types would be nice, but in general the “json with functions” vibe is imo great and a very nice fit for the domain. Lots of other modern config languages (e.g. dhall, jsonnet) have ended up in this part of the design space too.
With that said tweag has been working on a kind of nix 2.0 / nix with types for a while with the aim (I think) of being able to use it in nixpkgs: https://github.com/tweag/nickel
I also quite like nixlang for config tasks - in theory! In practice its really annoying. I think the main problem is the interpreter and the bad error messages / bad debuggability.
Part of that just comes from lazy evaluation, which makes debugging a lot harder in general (you feel this in Haskell...), but also just from nix not being a big popular language that gets lots of polish, and being completely dynamically typed.
Nix is ok. I like jsonnet more, and once I've tried to write a converter from jsonnet to nix, but it turned out this is much harder than expected (some idioms don't transfer from nix to jsonnet well.
Me as well. As a haskell / ML programmer, it is extremely intuitive. It's non-innovative (In a good way). Literally it's just a functional scripting language.
It’s a forked and tweaked version of the nix daemon. There have been some efforts to build a pure guile replacement, but afaik it’s not yet the default.
The ecosystem is in my experience very well fleshed out (7 yrs of use), as long as you don't require a knowledgebase/wiki/ up2date documentation, it's not been a issue for me since I could always fall back on Linux knowledge and just looking for how other distributions do x / how the thing itself is configured , and looking at how perhaps a existing nix module wraps that
