This is what I've been trying to tell people... the fact that you can easiliy build an alternative, doesn't mean you should. Unless, of course, you enjoy burning tokens and not working on your actual product.
@PatrickHaede Sure, you can. You can also change your own oil. Most people who are building something serious still don't, because the hour it takes is worth more than the twenty bucks it saves. Every 80% clone someone vibe-codes is an afternoon stolen from the product only they can build.
@Jason Unmetered tokens change the ceiling... I'd still bet against the $10k local desktop going mainstream next year. Most people don't want to own the compute any more than they wanted to run their own mail server. Convenience beats sovereignty almost every time
@demishassabis The labs arguing about "open" all built on each other's open work to get here. Transformers, JAX, the papers. Whatever the right policy turns out to be, pretending the frontier was ever a closed garden rewrites how all of it actually happened.
@gregisenberg Shared compute is interesting... but "Slack killer" has been a tarpit for a decade, and it's never been about features. Nobody switches team chat until their whole team moves at once, and it's hard to get teams to move together. Open compute doesn't touch that lock in.
@buccocapital The open letter is the corporate version of a subtweet. If the product were losing on the merits nobody would need to sign anything, they'd just watch it happen.
@mattpocockuk Half the skillset, yeah. Ambiguity, delegation, stakeholders, deciding if the work is right. But you’re optimizing for different things when your report doesn’t want a promotion.
@SimonHoiberg Sort of related to this is the amount of people I've seen that don't know how to read a stack trace... I like to fling a stack trace over the wall as much as the next guy, but it's comforting to know that if I need to read it and understand it, I can.
@SimonHoiberg Sort of a blessing until it becomes a liability, tbh. It's nice that we keep building these levels of abstractions, but when the abstractions leak or break, not having the wherewithal to fix it is a terrifying place to be.
@businessbarista When hiring for an average senior software engineer at a series A company, I regularly got over a 1,000 applicants in a week. Similar experience where most were either slop or incomprehensible resumes (who submits a 9 page resume?)
@dhh Historically, the catch has been the 3 days you spend setting it up and the weeks afterwards where you fine tune it to get it to the state you want. Maybe that's a noop now with these configurable OSs...