Going from starting the project two weeks ago to already having a flashy marketing site is another tell, unfortunately. As much as I would love to see a trustworthy version of this idea.
Reading the comments in this thread, I think it's difficult for some folks here to accept that many, many people outside their bubble genuinely despise what they're doing, and it's not just a misunderstanding or a matter of branding.
Not security, but I ran into a related supply-chain issue recently. I needed a library to perform a moderately complex task, and found one in the ecosystem I was working with that had been around for a while, appeared reputable, and passed my cursory inspection. So I dropped it in, got the feature implemented, and moved on.
Some time down the line, I discover CPU being maxed out, which is showing up in degraded performance in other parts of the system. I investigate, and I trace the issue to a boneheaded busy loop in this library that no human with the domain expertise to implement the library would have written. Turns out I'd missed one deeply-buried mention in the README that maintenance was being done via AI now, and basically the whole library had been rewritten from the ground up from the reliable tool it used to be to a vibecoded imitation.
Yeah, yeah, sure, bad libraries existed before all this. But there used to be signals you picked up on to filter the gold from the dreck. Those signals don't work anymore.
Right, but it has many knock-on effects unfortunately. For example, it propagates to web content and causes some sites to break because they don't test with animations disabled.
Awesome! Is there a working way to do the same for Windows virtual desktops? I remember I used to do it with ViVeTool [0], but Microsoft removed the feature flag at some point.
This seems like it might be a good place to ask: does anyone know of a low-cost, readily-available SBC box with built-in dual Ethernet interfaces?
I've been very interested in some of Radxa's boards in the ~$30-70 range, like the E52C [0] and the E20C [1], but they don't have many distributors and seem to have stocking issues [2].
> This is the Windows 11 start menu. See that Recommended section at the bottom of it? That is built with React Native for Windows. No, that is not a full JavaScript framework in your start menu. There’s no web view / browser running gobbling up your resources. It’s React Native for Windows which is a flavor of React Native that directly calls Windows APIs including, you guessed it, WinUI 3.
I would still say that means Windows Start uses React, frankly.
I'm trans. This man has actively and intentionally made life harder for myself and my loved ones. So yes, I'm going to enjoy any news that weakens his ability to do that, and no, I won't apologize for it.
I got really excited reading this! The docs site is very polished and hypes up lots of features which click with things I've been wanting out of a language. But then I went to the repository [0] and realized that this is a week-old project, with every single commit written by Claude. I went to the playground page [1] and tried the example for effects, a headline feature and what drew me in the most, but it threw an "unbound symbol" error. I thought maybe the example could just be out-of-date, so I tried the example under the "Algebraic effects" heading on the homepage, which shows a different syntax, but that threw a parse error. The "Pattern matching" example is supposed to return 78.5, but it returns 15.700000000000001 when run in the playground. The example for "Mutation" on the ownership docs page [2] throws "unbound symbol 'set!'". The "Type Signatures" example from the types guide [3] throws another parse error. That's where I stopped.
> Now an outcome has been chosen for you, without your input. The situation is probably irreconcilable.
I think you've reversed cause and effect. SparkFun publicly cut off Adafruit in response to Adafruit's private contact with SparkFun. Only then did Adafruit put out a public post addressing SparkFun's vague public allegations.
The comments in that thread were shameful. If only the commit author names changed, then it would be trivial to run a git diff comparing the content of the old and new HEADs. But no one did - instead they dogpiled on the maintainer who got doxed and had their home address posted.
The implication is that the death toll is under-reported due to the disruption of the means by which those deaths would be reported and logged. In other words, those thousands of deaths are just the ones we know about.