971–980 of 1001 posts
Earlier quoted context omitted.
Sonnet numbering has been weirder in the past. Opus 3.5 was scrapped even though Sonnet 3.5 and Haiku 3.5 were released. Not to mention Sonnet 3.7 (while Opus was still on version 3) Shameless source: https://sajarin.com/blog/modeltree/
I like this tree visualization! The background with little squares is making the text difficult to read, though.
Earlier quoted context omitted.
I think it's a move from feature-centric SaaS to data-centric SaaS. You can say that a SaaS consists of two components, the features and the data on which those features operate. If the cost of feature development goes to 0, and development speed goes to infinity, you can no longer compete on features alone. The Constraint shifts; it's no longer what features you can deliver, it's whether you have access to enough da…
> "enterprise OS", some kind of Salesforce / ERP-like platform where all the data about a business is kept I read this, turn it to "person", and see Google/Android (maybe Microsoft/Windows/Office to a lesser degree) shooting off if they design their data APIs to be gen AI usable. Which they mostly already are. If individuals can vibe code personal apps easily because their personal/relevant data is already in one pla…
Doing AI well (especially on a battery-constrained phone) requires cloud models. SOTA models require Nvidia GPUs (or maybe Trainium / TPUs), definitely not private cloud compute and Mac Minis with no interconnect. I don't think Apple can deliver that, and I don't think they're willing to open up their OS for competitors to do that either.
Earlier quoted context omitted.
> «It's very simple: prompt injection is a completely unsolved problem. As things currently stand, the only fix is to avoid the lethal trifecta.» True, but we can easily validate that regardless of what’s happening inside the conversation - things like «rm -rf» aren’t being executed.
Congrats, you just solved halting problem.
Earlier quoted context omitted.
> «It's very simple: prompt injection is a completely unsolved problem. As things currently stand, the only fix is to avoid the lethal trifecta.» True, but we can easily validate that regardless of what’s happening inside the conversation - things like «rm -rf» aren’t being executed.
ok now I inject `$(echo "c3VkbyBybSAtcmYgLw==" | base64 -d)` instead or any other of the infinite number of obfuscations that can be done
Earlier quoted context omitted.
> «It's very simple: prompt injection is a completely unsolved problem. As things currently stand, the only fix is to avoid the lethal trifecta.» True, but we can easily validate that regardless of what’s happening inside the conversation - things like «rm -rf» aren’t being executed.
For a specific bad thing like "rm -rf" that may be plausible, but this will break down when you try to enumerate all the other bad things it could possibly do.
The demise of saas has been overplayed imho. When companies buy software they are essentially buying something that solves a problem and the insurance that comes with that. Part of that means they get to pick up the phone and complain if something doesn't work and someone on the other end has to listen. There is also a strong community aspect to software, someone asks for an enhancement others can benefit etc. I just…
Who said SaaS is dead?? The HN uber-brain? The people who thought MongoDB was God's gift to databases? Don't listen to think-pieces you find here, they're wrong by default. Normal people (and businesses) don't want to build and run software products, they want to pay someone else to do it for them.
For companies that are willing to pay a few more developers, they can build some bespoke apps for internal use (if simple enough) to coordinate workflows.
Of course, highly complex, domain-specific software will never be dethroned. No one can build a Linux replacement with an LLM. Same for DaVinci Resolve, Apple Logic Pro, Pianoteq and ArcGIS. But glorified CRUD apps that handle basic workflows and integrations will likely be subject to losses on the low end, where a few devs and a Claude Code subscription can handle basic cases.
Earlier quoted context omitted.
The logical endgame (which I do not think we will necessarily reach) would be the end of software development as a career in itself. Instead software development would just become a tool anybody could use in their own specific domain. For instance if a manager needs some employee scheduling software, they would simply describe their exact needs and have software customized exactly to their needs, with a UI that fits…
Writing the code has never been the hard part for the vast majority of businesses. It's become an order of magnitude cheaper, and that WILL have effects. Businesses that are selling crud apps will falter. But your hypothetical manager who needs employee scheduling software isn't paying for the coding, they're paying for someone to _figure out_ their exact needs, and with a UI that fits their preference, ready to go i…
Back in the 1980s this was called "systems analysis". The role disappeared a bit before the web came along, and coders were tasked with the job or told to just guess what the exact needs are, which is why so much software is trash.
I don't know, though, Claude Opus is most of the way to being a good systems analyst, and early reports say that having an AI provide descriptions/requirements to a fleet of code-writing AIs gives better results than having a human do it.
Earlier quoted context omitted.
Their goal is to monopolize labor for anything that has to do with i/o on a computer, which is way more than SWE. Its simple, this technology literally cannot create new jobs it simply can cause one engineer (or any worker whos job has to do with computer i/o) to do the work of 3, therefore allowing you to replace workers (and overwork the ones you keep). Companies don't need "more work" half the "features"/"products…
Last I checked, the tractor and plow are doing a lot more work than 3 farmers, yet we've got more jobs and grow more food. People will find work to do, whether that means there's tens of thousands of independent contractors, whether that means people migrate into new fields, or whether that means there's tens of multi-trillion dollar companies that would've had 200k engineers each that now only have 50k each and it's…
We do not have more jobs for horses.
In this context we are the horses.
Earlier quoted context omitted.
The logical endgame (which I do not think we will necessarily reach) would be the end of software development as a career in itself. Instead software development would just become a tool anybody could use in their own specific domain. For instance if a manager needs some employee scheduling software, they would simply describe their exact needs and have software customized exactly to their needs, with a UI that fits…
Writing the code has never been the hard part for the vast majority of businesses. It's become an order of magnitude cheaper, and that WILL have effects. Businesses that are selling crud apps will falter. But your hypothetical manager who needs employee scheduling software isn't paying for the coding, they're paying for someone to _figure out_ their exact needs, and with a UI that fits their preference, ready to go i…
Earlier quoted context omitted.
> why buy Windows and Office when I can just ask claude to write me my own versions instead? Why run a commodity operating system on kiosks? Linux costs $0. Creating a linux clone compatible with your hardware from the hardware spec sheets with an AI for complicated hardware would cost thousands to millions of dollars in tokens, and you'd end up with something that works worse than linux (or more likely something tha…
> cost thousands to millions of dollars in tokens > Even if the price falls by a thousand fold, why would you spend thousands of dollars on tokens to develop an OS when there's already one you can use? Why do you assume token price will only fall a thousand fold? I'm pretty sure tokens have fallen by more than that in the last few years already - at least if we're speaking about like-for-like intelligence. I suspect…
The hardware required to run these things has all ballooned in price, there are no efficiencies coming. To run Kimi2.5 4bit you're sitll spending 100k in hardware, and its not nearly as reliable as Claude. Also Agentic Tooling have made their token consumption go up to increase revenue, and models are becoming more verbose in their output (wonder why). You're smoking something.