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
Readit NewsGuuD commented on Decompiling the New C# 14 field Keyword blog.ivankahl.com/decompi... · Posted by u/ivankahl
GuuD commented on Supply chain attacks are exploiting our assumptions blog.trailofbits.com/2025... · Posted by u/crescit_eundo
> it wouldn't be hard to get a bad update into a package (xz did that)
I'd actually call that quite difficult. In the case of xz it was a quite high-effort "long con" the likes of which we've never seen before, and it didn't quite succeed in the end (it was caught before rolling out to stable distros and did not successfully exploit any target). One huge close call, but so far zero successes, over almost 30 years now.
But typo-squatting and hijacked packages in NPM and PyPI, we've seen that 100s of times, many times successfully attacking developers at important software companies or just siphoning cryptocurrency.
Zero that we know of
GuuD commented on Nvidia's RTX Pro 6000 has 96GB of VRAM and 600W of power theverge.com/news/631868/... · Posted by u/mfiguiere
What's the limitation that keeps memory limited to 96GB? Could one put 512GB of memory on a card? I'm curious about what is the limiting factor.
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
People are alway going to make bad decisions. Sometimes that is out of a lack of experience or knowledge which can be fixed by better training (which also requires money). Other times it is out of apathy, laziness, or something else that can't be easily fixed. Either way, time and money can provide extra sets of eyes to find and fix those mistakes before they lead to a breach.
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.
GuuD commented on Simply explained: How does GPT work? confusedbit.dev/posts/how... · Posted by u/nitnelave
GuuD commented on Simply explained: How does GPT work? confusedbit.dev/posts/how... · Posted by u/nitnelave
GuuD commented on Binance halts deposits and withdrawals for customers in the UK bloomberg.com/news/articl... · Posted by u/alvis
Isn't it obvious? If the fire was responsible for burning down the house, then the fire must have also built it.
Feels close to the theory behind homeopathy. If something can trigger some symptom in a healthy person, then the same something can revert it in a sick person. They just remove any trace of it from the medicine to increase the effect.
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.
GuuD commented on Austral: A systems language with linear types and capabilities borretti.me/article/intro... · Posted by u/riidom
> I never figured out the brilliant insight about redundancy of operator precedence
As many things go, the Smalltalk designers had this insight a few decades ago, all "binary messages" have the same precedence.
I still think it's weird, but it makes sense.
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:)
GuuD commented on Austral: A systems language with linear types and capabilities borretti.me/article/intro... · Posted by u/riidom
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.