Also I think a lot of people simply think models which are published openly shouldn't be held to the same legal standards as proprietary models.
1,096 karma · joined December 18, 2025
Also I think a lot of people simply think models which are published openly shouldn't be held to the same legal standards as proprietary models.
Or do you think a Microsoft exec should go to jail every time someone uses it to write a death threat?
Yeah I've sort of noticed this on X for the brief time I was on there this weekend. The Claude Code creator was hyping it up to the moon, and when people called him out for it he said he would feel the same way if he wasn't making 1000 racks a year with it. Sure mate.
What people don't realise is if tech progresses to the point where everything is automated, the marginal cost of everything will basically go to zero. It would be better to give away food and shelter for free if it keeps things peaceful. And if not, people have revolted for far less.
That being said it's a complete utopia and once this bubble pops we are basically going to be where we were, but with excellent natural language parsing and generation, with some useful code generation and introspection tools, writing assistants, etc. Which will be great, but not world changing.
- Pragmatic syntax choice: The comment-based annotation system is indeed a clever solution that minimizes friction for adoption
- Avoiding past pitfalls: By learning from previous safety proposals, this approach sidesteps the intrusive syntax issues that hindered earlier efforts
- Incremental adoption pathway: The ability to gradually introduce safety guarantees without requiring a complete rewrite is a game-changer for legacy codebases
- Democratizing compiler expertise: Leveraging LLMs to tackle problems that traditionally required specialized knowledge is an exciting development
Overall, this represents a promising step forward in bridging the gap between C++ and Rust's safety guarantees. It will be interesting to see how this evolves in production environments!
Anyways if we do get to the point where you need to use LLMs to write code, I can make a decision then, but for now I don't feel the need to adopt agentic workflows and I think the people who don't will be better cognitively positioned in the future.
In order to learn you generally need to actually do the thing, and usually multiple times. My point is that it's easy to use an AI to shortcut that part, with a healthy dose of sycophancy to make you feel like you learned so well.
It's fine to use the LLMs in the same way that people watch science YouTube content, but maybe don't frame it like it's for learning. It can be great entertainment tho.
Maybe shocked is the wrong term. Surprised, perhaps.
Obviously you cannot generalize that to all software development though.
Yes that's already been well established.
I gave agents a solid go and I didn't feel more productive, just became more stupid.
Developers notoriously overestimate the productivity gains of AI, especially because it's akin to gambling every time you make a prompt, hoping for the AI's output to work.
I'd be shocked if the developer wasn't actually less productive.