12,241 karma · joined March 24, 2010
I am working on code generation at Bosun.AI. Previously CTO at Aeroscan.nl, and lead engineer at Phusion.nl.
[ my public key: https://keybase.io/tinco; my proof: https://keybase.io/tinco/sigs/0OUuceCURCXaFpxf5PCgpBOzDSX8K7Ux-FTuhO2zK9U ]
I think it's the hard work arounds that will eventually break it. Like we're already growing strawberries that are naturally sweet, in the future maybe our bread will be made of wheat that has "natural" sugars in it or something. But I feel that for that to happen the "no added sugars" labeling would have to be exceptionally effective.
For what it's worth the last time I had to procure a small cluster the offer Dell made was ridiculously overpriced, didn't meet the specifications I asked for, and the whole experience didn't inspire confidence in the software they were pitching either. We were a small underfunded startup so we were never gonna drop 200k on that storage solution (0.5PB HDD + ~80TB SSD), but if we did have that kind of budget we probably would have gone with one of the smaller but more focused parties there instead like maybe TrueNAS, I bet there's a beautiful market for Oxide as well in that segment.
If you remove that component from their value prop, they're not that much different from Dell.
I wonder when for the first time a team of humans will complete a full project based on a finding that turned out to be hallucinated in a sub step of an AI agent.
So when these regulations that OP would start to take hold, would we get companies to sponsor random open source dependencies like libxml2? Or would they gather around some stable proprietary ecosystem like Microsoft's and maybe some big innovative solutions built on top of Microsoft?
It's not the "safety critical" software that needs this fixed, it's all software in general. There's a million software systems that have important privacy sensitive data or safety relevant processes that fly under the "safety critical" radar.
I don't get why there's people trying to twist this story or come up with strawmen like the A2000 or even the RTX5000 series. Intel's coming into this market competitively, which as far as I know is a first, and it's also impressive.
Coming into the gaming GPU market had always been too ambitious a goal for Intel, they should have started with competing in the professional GPU market. It's well known that Nvidia and AMD have always been price gouging this market so it's fairly easy to enter it competitively.
If they can enter this market successfully and then work their way up on the food chain then that seems like good way to recover from their initial fiasco.
Since that still would take months I think I simply waited for the next upgrade and moved all the data to a new pool. And deleted the old one.
I've also never heard anyone argue that someone else should configure some different tab width, is there a specific language ecosystem you were in that had these insane takes?
I think it's a bit cynical that it would cost at least 4 years for this change to be admitted into the compiler. If the author is right and there is really no good reason for this rule, and I agree with the author in seeing no good reason, then it seems like something that could be changed quite quickly. The change would allow more code to compile, so nothing would break.
The only reason I could come up with for this rule is that for some other reason allowing non complying type parameters somehow makes the code generation really complex and they therefore postponed the feature.
Without that context however, the game is indisputably great. And the fact that they used vector graphics is a lucky win as it means the game renders crisply on modern TV's and monitors.
Perhaps you'd feel the same way about a machine or tool or toy that you used when you were 10?
Just compare a .csproj to something modern like a Cargo.toml and you'll see why someone might think .csproj is awful. It is immediately obvious what each section of a Cargo.toml does, and intuitive how you might edit or extend them.
Also, just talk to a C# developer, I bet over half of them have never even edited a .csproj and only use visual studio as a GUI to configure their projects.
I researched quite extensively prior to landing on SMB, but it really seems like there isn't a better way of doing this. The environment was mixed windows/linux, but if there was a better pure linux solution I would've pushed our office staff to switch to Ubuntu.