When you say "everyone" do you mean "everyone in the US military establishment"? I remember very few independent commentators who suggested the US intervention in Iran was a good idea. (Personally I think it's too early to say.)
9,217 karma · joined November 30, 2008
When you say "everyone" do you mean "everyone in the US military establishment"? I remember very few independent commentators who suggested the US intervention in Iran was a good idea. (Personally I think it's too early to say.)
I think it's simply that making field names become functions that select from the record was a simple design that worked, and didn't require anything new to be added to the language.
Same, and now seven months later a GBP 20 per month Plus subscription gets me basically all the GPT-6-Luna-xhigh I can eat, which does a tremendous job of Haskell. It's even helped me with some really gnarly things like this, which require deep knowledge of the GHC RTS: https://github.com/tomjaguarpaw/bluefin/commit/c298733bdd67d...
It's possible it's much slower when working on Haskell than it is on other languages. I wouldn't know because I've only tried it on Haskell. But I'm very happy (and extremely impressed) by it.
You can try it now yourself in Haskell! This is my effect system, based on capabilities: https://hackage.haskell.org/package/bluefin
One of the common objections I hear to Bluefin is "isn't it too inconvenient to pass around capabilities everywhere?". Perhaps surprisingly, no, I haven't found it remotely inconvenient. I find it liberating, actually.
https://hackage.haskell.org/package/bluefin-0.0.7.0/docs/Blu...
On infection, I think it's a bit like being infected by mitochondria :)
But if you don't want an ironclad guarantee and instead you're content with making wrong code obviously wrong even if it's not formally verified, then I recommend Haskell with a capability system (what the Haskell world calls an "effect system"). As far is I'm concerned there are two practical choices in 2026, Bluefin (mine) and effectful (one of Bluefin's inspirations)
Bluefin is used in production, and as far as I know capability is not.
Not on Nitter! Which is the point, for me at least.
Does this view rest on the claim that the only use of the aristocracy is warfare?
Are you sure? All three servers I regularly use, as well as all of the mirrors that I found with a quick search, are down. If there are other servers still working then can you please give a hint about how I could find them?
> Like lazy evaluation and memoisation
Yes, that causes performance impact. If you don't want the performance impact then don't write code that uses those behaviors. Sure, that rules out large parts of the ecosystem, but I said Haskell was a systems language not that its ecosystem was generally suitable for systems programming.
> however Haskell manages memory
No, Haskell's memory manager is world class, with two (at least) tunable garbage collectors.
> But I’m not aware of Haskell beating rust in program performance & memory usage benchmarks
Nor am I!
> If Haskell were a viable systems language, I suspect the kernel would not have been converted to C.
I suspect they converted it to C because you can't write a kernel in a managed language with a garbage collector.
Yes, that was one of the things that I hope happens with the open source software I write.
> Would you be willing to do free work for a corporate entity whose entire business model is making sure they sit as a gatekeeper between your free work and others who would benefit from your work?
Sure, that's what doing SEO on one's own blog is, isn't it?
> For some it's demoralizing to know that your work will be broken down and atomized into language model mush, and the credit will go to the computer.
I think this is probably the crux: that writing is no longer discoverable because people aren't using search engines any more. It would be interesting to put some hard numbers on that. I reckon writing is still more discoverable (in absolute numbers) than it was when blogs first took off (over 20 years ago?)