Comment by agile-gift0262
1 hour ago
> I am becoming dependent on AI to make a living
IMO, if you depend on AI to make a living, I'd invest in hardware for local inference, and learn on how to effectively make a living using AI inference you control, on hardware you control. Sure, economically speaking it's way cheaper to use one of these heavily subsidised services (for now), and their models are faster and more capable, but if your livelihood depends on AI inference, and you are renting AI inference, you are a being a serf of the tokenlord. And your livelihood depends on the whims of the tokenlord. They can increase rent prices, they can decide you can no longer do whatever you are doing, and you have no recourse, because you are dependant on them to make a living.
There are a lot of things in my toolchain pre-AI that I did not own and relied on to make a living. Mobile developers are in even worse shape, and iOS developers doubly so. The idea we were somehow less beholden before AI, I think, is silly.
None of us can wholly do our trades without support. Local inference is a fun idea, but you'll be out-competed by the serfs, as you call them.
Except there's a huge gulf of self-hosting and using API hosts - no way you can reach the economics of a shared host. Privacy is a problem but you can chose who you host with and where it's hosted (which jurisdiction).
When privacy/compliance really starts to matter it's up to the client/business to provide you with tooling - you're not running that on your own hardware anyway.
So the local AI for individuals is just a hobby/gimmick at this point not a rational decision. Self-hosting for business is a different story.
I'm not sure. The problem with the cloud llm's is they are complete black boxes that change frequently and randomly day by day.
If you run Qwen 3.8 on your own hardware, every single day, it's the exact same model running in the exact same way.
Yes, it's no where near as "smart" as the cloud based models. But it's consistent.
So the workflows/processes/ways of working you create will work mostly similar day to day.
With Claude/OpenAI you frequently find days where the models are useless, and days when they are out of this world.
So I guess the choice comes down to:
1. Randomly the smartest thing on the planet with unpredictable rate limits that is mostly amazing, but frequently messes with your workflows
2. A really good local coding model that is consistent every day with no rate limits
I'm not sure. My gut feeling is maybe the right answer is a mix of both.
Gambling on the biggest models, hoping they are working smart that day, when planning or doing very complex work. Then doing most of the tasks/daily work using local models??