simplesocieties

SO’s demise was two conflicting user bases who wanted mutually exclusive things: the questioners a space to learn and grow without judgement, and the point collectors a glorified FAQ for programming and social media network.

The operators of the platform never grappled with the reality that these two users want opposing things, and LLMs were just the final nail in the coffin.

“Local pedo didn’t get an invite to his favorite pedo club, therefore he can’t possibly be a pedo.”

You’re right, if not for the countless innovations and designs NASA made SpaceX wouldn’t exist, therefore it owes its profits back to the taxpayers that funded its success.

"Seatbelts don't solve car crashes so there's no need to wear one!"

Just to put everything in perspective, I recognize fully that Cloudflare had a use case for tsrs with WASM sandboxing. I am addressing your larger point about this sort of thing becoming the norm.

> We cannot ignore individual benefits in contributing, but that is not everything.

Individual benefits are the very foundation of most collaborative efforts. Pharmaceutical companies get payouts via patents for researching life-saving medicine. Even with money taken out of the equation, many academics slave for years over their research in hope of recognition either via Tenure or Nobel Prize. Ignoring the fact that people want credit for their work is dangerous and irresponsible.

Forking projects that are near-complete or have already undergone major refactors just to snipe them last-minute with vibe coded efforts is going to kill collaboration. I'm never building another project in the open again because that is precisely what I'm aiming to avoid.

You are talking about banning the DeepSeek hosting provider which no one in this thread disputes would be a risk to national security. The issue is banning open weight models which are not software, they are data.

Some of the government bans have entered into the territory of banning the open weight model itself. This is like saying we must ban intelligence services or the military from using public weather reports in China for any operations. Public data is used all the time for these things, and an open weight model like DeepSeek should be treated with some level of care (e.g. putting it behind a firewall, having people study the model outputs, etc.) like you would for any foreign source of data, but that's all it is. data.

ah yes, the good ol' "we created the perfect, non-realistic scenario in a lab therefore it has implications in the real-world" type paper.

The hugging face hack was not a model gone rogue, it was intentional security malpractice. An open weight model cannot re-arrange electrons nor can it magically break a firewall that's setup properly.

Don't governments have tech literate advisers? What's to stop someone from distilling DeepSeek into the TotallyGrownInTheUSA model?

> It wasn’t “let’s build a faster Rust based Typescript compiler” at all. That was a nice side-effect.

Then why are the performance graphs the headliner topic in the article? The WASM sandbox is barely a footnote.

What are the problems in async the new trait solver will fix? Looking forward to building more on async Rust so I'm curious

AI isn't improving productivity if EVERYONE is trying to reinvent the same f*king thing. What are we doing here? Why publish any open source software at all if someone is gonna swoop in and vibe something better™ faster™ and more memory efficient™ the next day?

Too late I just shipped tsasic so you can have a custom-made board for every single application you will ever write.

These two things are mutually exclusive. They can store encrypted backups on a server somewhere, but unless they have the decryption keys from both parties (E2E) then no, it can't be stored in plain-text.

The productivity gains of people using their own "custom" harnesses and agent tooling (e.g. letting agents talk to eachother over a messaging board) is questionable at best a waste of time at worst. No one I've talked to is actually applying the scientific method and measuring how long and how many tokens it costs to get a certain task done with just a plain chat input vs all this custom harness/tooling crap.

All you need is the source code for your existing project and the claude code/codex/opencode cli and boom, you are ready to ship. Most people doing the impressive stuff with AI are just using it, not building harnesses or "agentic" tooling.