https://en.wikipedia.org/wiki/Jevons_paradox
Better to write a solid inference engine, tell people to run it themselves, and externalize that cost.
1,284 karma · joined April 24, 2012
https://news.ycombinator.com/item?id=46192577
https://en.wikipedia.org/wiki/Jevons_paradox
Better to write a solid inference engine, tell people to run it themselves, and externalize that cost.
They are all impressive tech, but not actual stuff you can sell or distribute until you can answer those questions.
Entirely their fault, tbh. Mozilla's C suite has knowingly enriched themselves off this money for over 15 years now. If they were serious about surviving, they would have found alternative funding sources a long time ago.
Firefox isn't a true project. It's Google paying off someone to make Chrome appear not to be a monopoly at first glance.
A solid example of this right now is all of the Mullvad VPN ads I've seen on the Seattle Light Rail lately. Google used to have ads everywhere for Chrome. The only time I saw Firefox stuff was the rare t-shirt at a tech conference.
They also devolved into a work friendly variant of 4Chan's /g/ board. "Work friendly" as in nothing obviously obscene, but the overall tone and hostility towards newcomers is still there (among other things).
People are prejudiced, plain and simple.
This is true for both the engineering and business sides. Cyanogen’s failure showed that it ultimately doesn’t matter how good your software product is if your business side of things is poorly run. Same with the Pebble smartwatch - amazing product, terrible back office.
But they do work for pair programming. Which explains a lot of the tech layoffs we've been seeing.
Open vs closed web
Both of the open options are nice on paper, until you realize that they were largely being pushed by big tech. The same big tech that is scraping them hard for AI training, and possibly have been using them silently without respecting licensing agreements for an even longer period of time.
"Open" only works when everyone plays nice and fair. This whole kerfuffle of AI scraping has shown that this isn't happening, and likely hasn't happened for a long time if at all.
I was using a combo of Ollama + Roo Code for the front/back end but Ollama is kind of dumb when it comes to memory overload protections. I've since switched to LM Studio and it has a very annoying hard timeout of 2-3 minutes on its API server. Local isn't perfect right now, but when it does run you can see the potential as clear as day.
32 billion sized R1 and Qwen models blow GPT, Gemini, and Claude out of the water for coding tasks usually. And they can be made to run on a standard gaming PC off the shelf from somewhere like Best Buy or Costco. They will run really really slowly, though, but they will run.
* Star Trek everything (except Section 31 - worse than Star Trek V)
* South Park specials
* Frasier sequel
* Beavis and Butthead revival
The only reason people went to streaming in the first place was that Netflix was cheap and, arguably, a heavily subsidized monopoly in the streaming space.
So yeah, some kind of DVD/BluRay business could very well work in the US and Canada.
Local LLMs? A new renaissance. All that power without having to pinky swear with a cloud provider that they won't just take your generated code and use it for themselves.
Expect to see some awesome Windows and Mac apps being developed in the coming months and years. 100% on device, memory safe, and with a thin resource footprint. The 1990s/2000s are coming back.
I think this is a hard kick below the belt for anyone trying to develop AGI using current computer science.
Current AIs only really generate - no, regenerate text based on their training data. They are only as smart as other data available. Even when an AI "thinks", it's only really still processing existing data rather than making a genuinely new conclusion. It's the best text processor ever created - but it's still just a text processor at its core. And that won't change without more hard computer science being performed by humans.
So yeah, I think we're starting to hit the upper limits of what we can do with Transformers technology. I'd be very surprised if someone achieved "AGI" with current tech. And, if it did get achieved, I wouldn't consider it "production ready" until it didn't need a nuclear reactor to power it.
> Run asynchronously in the cloud
> cloud
Reality check:
https://huggingface.co/Menlo/Jan-nano-128k-gguf
That model will run, with decent conversation quality, at roughly the same memory footprint as a few Chrome tabs. It's only a matter of time until we get coding models that can do that, and then only a further matter of time until we see agentic capabilities at that memory footprint. I mean, I can already get agentic coding with one of the new Qwen3 models - super slowly, but it works in the first place. And the quality matches or even beats some of the cloud models and vibe coding apps.
And that model is just one example. Researchers all over the world are making new models almost daily that can run on an off-the-shelf gaming computer. If you have a modern Nvidia graphics card, you can run AI on your own computer totally offline. That's the reality.
That right there says a lot about where we are with AI now. We have AI models that can run on off-the-shelf name brand computers (think a Dell or HP tower at a Best Buy) with about the same memory footprint as a few Chrome tabs. Yeah, it'll be slow and stutter like crazy at only a few tokens per second of output. But it still works in the first place.
And that's the important part here. The fact that local on-device AI is here, it can produce output superior to cloud platforms in general, and it's only going to get better over time (especially zero shot training techniques - look it up). These firms' products are expensive developer front ends to some of the most expensive and proprietary models on the market - that they have to rent themselves. Why use them as a middle man when I can either go to the model provider directly or bring my own model?
Also, this trend of fully forking VS Code needs to stop. These coding apps could have been VS Code extensions, which would let devs have access to all of Microsoft's proprietary tooling. And the apps feel vibe coded themselves overall.
- IDs usually contain enough information to totally steal a person's identity (beyond just their name and mailing address).
- IDs usually have secret security mechanisms beyond what's publicly known for a government to verify if an ID is real or not.
- 3rd party business systems can only verify the publicly known security stuff. And because that security stuff is public, it can get faked easily.
- IDs are super easy to fake.
- The only entity that can totally verify an ID is a government, because you'd have to verify the secret security mechanisms as well.
And there's a million reasons why you wouldn't necessarily want a government to verify an ID for a private business transaction.