logoalt Hacker News

Aurornis • today at 5:25 PM • 4 replies • view on HN

Sharing open weights models is a way to break into a market where you need recognition and brand awareness.

Microsoft doesn’t need any of that. They have the market share, distribution, brand awareness, and a lot of their potential customers already use Microsoft products somewhere.

The phone comparison doesn’t apply, IMO. Phones are entire ecosystems and they’re very sticky. People don’t switch phone OSes casually because they only buy a phone every several years. Getting locked into a phone you don’t like is too risky.

AI plans are not like that. Not yet, anyway. Vendors push for contracts and one year lock ins via discounts, but individuals and nimble companies are changing AI providers all the time.

Even my wife’s big company technically has a contract with one AI provider for the company, but teams across the company are getting extra spending to use on Claude or other models of their choice and the favorites are changing every few months.

Trying an AI model is low risk. You can do it for a month or even just earmark a token budget and try it. Nothing like buying a phone that you’re stuck with for years.


Replies

igravious • today at 5:32 PM

Sharing open weights models is a way to break into a market where you need recognition and brand awareness.

Microsoft doesn’t need any of that. They have the market share, distribution, brand awareness, and a lot of their potential customers already use Microsoft products somewhere.

https://deepmind.google/models/gemma/

https://openai.com/index/introducing-gpt-oss/

➕ show 1 reply
hackerbrother • today at 5:32 PM

They just need to make VS Code’s tools as attractive as Codex/Claude. Their harness layer has fallen behind. (Could they just vibe one up? Hmm.)

poopingatwork • today at 5:59 PM

As AI grows, you might expect the Open Source movement to halt.

Sharing repos directly exposes your vulnerabilities and unpatched software to AI. So you close it, then spend your own money closing gaps.

As your code and infrastructure begins to harden (paid for with time and churn), your costs for churn increases.

As costs increases, you start looking to reduce labor to stay profitable, and you begin to cut corners to do more with less, and speed productivity up (paid for with increased complexity and vulnerability to outages).

Outages increase, so again you decide to close your source repos and begin working privately. But then who is hosting your source? So you lock in with a vendor that does both: hosting and thinking.

And we'll try this out for a while until it causes too much pain to the economy, and we'll reverse course again.

We'll demand quality, labor from real people: bring them back!

But there is nobody to bring back. All the talent retired. Nobody picked up the Mantle except for AI.

Forwards and up, for eternity, because everyone wants things cheap, fast, and of the utmost quality.

It's a retarded three body problem fueled by greed, time, and legacy.