GuuD

We do know, because we used to have some Claude models identifying as Deepseek when prompted in Chinese

I feel like in a few more years and 2-3 major versions C# will have all the useful features of F#. It will also keep being much more exciting because our benevolent corporate visionaries manage to add new gotchas with every major and some minor releases

Zero that we know of

Bandwidth/GPU real estate in terms of area. Biggest GDDR7 chips are 3GB 32-bit, it has 512bit wide bus. And even this is going to moonlight as a space heater

Also, our defaults are opposite of safe (most of the languages are still mutable by default, rigorous type systems wildly unpopular, there is a straightforward way to concatenate strings inside a query etc), our disaster prevention tools and practices seem most often to be targeted at symptoms instead of the causes (god forbid we rethink our collective ways and create/adopt tools that are much harder to use incorrectly), and all of this keeps happening because there is no pressure for it stop. What’s the incentive to?

I don’t think that there is a room for a meaningful and honest discussion about individuals in these circumstances.

The difference is negligible on 2x 4090. There are more important differences like 4 bit KV cache.

I'm sorry. They were not, it was the joke from OP

Guid partition table. Older of GPT brothers, more of a blue collar guy

English isn't my first language either, and I know how confusing it can be, so let me help here. Here is the quote from the post: "If crypto people feel that the losses are because of Fed's actions, then they should also agree that the profits are because of Fed's actions". As we know, Fed's actions have changed: from providing "cheap" or almost free money (rate was something like 0.08%) to much more expensive ~4.5% now. It wouldn't be a huge leap of reason to assume that at least some of the impressive growth of crypto was driven by insanely low interest rates. But that's just my opinion, feel free to keep comparing monetary policy to homeopathy.

Fuck, I mean… yeah. Thanks for one more insight, by showing me that sending message/calling a method is a binary operation, seems so obvious but I never made that connection. This day started by shelling by Russian rockets, but reading the post and your comment somehow made it… good? I always get caught off-guard by how much baby we’ve thrown with the water with modern languages compared to some brilliancy we had in Lisp and Smalltalk. Both are extremely out of my cup of tea region, but I learn so much when I interact with them. The only thing JS and something like Java taught me is to stay away:)

This is fantastically written documentation. What is even more exciting for me, that this is almost exactly what I was dreaming and talking non-stop about for the last few years. I never figured out the brilliant insight about redundancy of operator precedence. On the more embarrassing note in numerous implementation not-quite-attempts I always ended up gutting loops as a feature in favor of recursion and went with effects for capabilities (among other things). Then I was usually caught off guard by either of those or my other darling — partial application interacting in unexpected way (only for me probably) with linear types, which always punched me back to square one. Extremely impressed with how sound and grounded in reality your choices are. Fantastic job.

I would have to respectfully disagree with you on the serializers part here. For me, after decades of fighting with “magic” stuff, simplicity is the key feature. So, everything that is a simple map function in disguise I tend to stick with functional languages and approaches.

The combination of caching Postgres queries (because you are making over 30 of them per page), but still deploying everything to 6 distributed regions is just perfect chef's kiss

In a more broad way — it’s also a tax on conscience. Bonkers.

It is, for people who think that the chance of meeting dinosaur on the street is 50% (you either do or don’t)

/s

I have no idea, but isn’t it the usual real-world case of “it’s complicated, and it’s both”?

Go is just shitty Pascal, change my mind.

On a more serious note. I decided to read Delphi documentation recently because I’m old enough to hear a lot about it, but not quite old enough to write anything in it. It had discriminated unions. It did! I can’t imagine my life without them, I write stuff exclusively in Ocaml-like languages, so the only question that I have in my mind is “how the hell we managed to go backwards?” It’s so weird.

Oh man. Are you me? Thanks for that comment.

For me functional programming was just like a “missing link”. Wait, I can just code like I think, not in this weird statefull way? It’s just so practical for me. I can deliver 10x the value for 0.1 the effort. It’s just not fair, I know for a fact that there are more people with the same model of thinking, I just want them to feel as liberated

They voluntarily withdrew their bid, because all 29 of the remaining Atlas 5 rockets (not built afaik, just planned and have engines ready in storage somewhere in Alabama) are already assigned to customers.

"Any headline that ends in a question mark can be answered by the word no."

https://en.m.wikipedia.org/wiki/Betteridge%27s_law_of_headli...

This has to be the most insane take I’ve ever read. There is no shortage of would-be fossil fuel producers if the price is high enough. Norway, on the other hand, by restricting consumption of fossils pays “early adoption fees” for greener tech. That’s not the most direct way to invest oil dollars in renewables, but it’s certainly one, and it works.

I think I successfully avoided writing for loops in application code for the last 3 years. I don’t miss them.

Wait. I always use logarithm for this kind of tasks, how exactly does it make me incompetent and terrible? This is literally what logarithm represents?

Fantastic. Knowing that my data was validated before being lost makes it so much better.

Yes they are, but it's not about being novel. Parser combinators are abstraction, and damn good one: they are easily composable, reusable, and what's most important approachable even for somebody who is familiar with the functional approach but have never written parser before. While I could appreciate neat and tidy imperative recursive descent implementation, I would very much prefer to enjoy it from afar, not inside my own codebase.

This is awesome project. For the last week I was developing essentially the same thing, but with F# as shell/REPL language. It's not yet ready to be open-sourced but if there is any interest I can clean it up and move to Github in a week or so.