2,328 karma · joined June 27, 2012
Not to say you're wrong about commoditization. I don't think these companies will be able to raise their prices and keep them there to make enough money to keep building models like they've been doing.
There are people working on this.
It's the same in other industries. In your example, if labor went into building a whole new assembly line that pays itself off over several years, capex. If it just goes into building products to sell, opex.
No, not quite. It really comes down to opex vs capex and the depreciation schedule for your investment.
Software development is typically categorized as capex, on a 3-5 year depreciation schedule. You assume the software you write today will be generating value for you that long.
If a big, expensive model training project only gives you value for a year or less, that is not like most companies.
Source: My wife works IT for our school district.
But other things will:
- Liability rules
- Regulations that you get audited on (esp. for companies already heavily regulated, like banks, credit agencies, defense contractors, etc)
If you get the legal responsibility part right, then the education part flows from that naturally.
It's kinda shitty to steal someone's works, then use them to build a machine to also steal their jobs.
It works in isolation and fails miserably when trying to do a big demo of it in a conference talk when attempted by dozens of people in the same room.
What you own is the image copyright. But the right to copy is only one of the rights at issue.
Under various state laws (California in particular), you might not be entitled to do all the things with that picture that you could do of one that doesn't have my likeness. Privacy laws like the CCPA are one possible carve-out. A "right of publicity" is another.
There's an old saying about property law that "property is a bundle of sticks". The bundle can be subdivided.
In the beginning Twitter was very free and open with API access. There were plenty of alternative apps. Of course, that changed when they got serious about monetizing.
Would it really be any harder for Bluesky to switch from ATProto to a proprietary API than it was for Twitter to close their API? How many users are realistically going to download their archives and upload them to some other provider? If most people are using the website or official app, that's where the stickiness is. There would be a blog post with a title like "Supporting the Bluesky Community for the Next Century" and how it's better to have a centralized site that can feed its employees than an idealistic decentralized one that disappears. Things would seem OK at first. But enough years of chasing quarterly KPIs would put them in the same spot as Twitter and Facebook.
If cable television or restaurants or ice cream start causing harm that we want to deal with, we can vote on that when the time comes.
> I assumed the writer was a journalist or author with a non-technical background trying to explore a more "utopian" vision of where trends could go.
If you assume you're reading something from a person with intention and a perspective, who you could connect with or influence in some way, then that affects the experience of reading. It's not just the words on the page.
This is an interesting reversal in itself. If you make the specification protected under copyright, then the whole practice of clean room implementations is invalid.
There are lots of domains out there other than .com that are just fine.
The government shouldn't be able to buy data that would be unconstitutional or unlawful for them to gather themselves.
On the other hand if a company is just aggregating something benign like weather data, there's no need to bar the government from buying that instead of building it themselves.
Traditional karma scores, star counts, etc, are mostly just counters. I can see that a bunch of people upvoted, but these days it's very easy for most of those votes to come from bots or spam farms.
The important difference that I see with Vouch is not just that I'm incrementing a counter when I vouch for you, but that I am publicly telling the world "you can trust this person". And if you turn out to be untrustworthy, that will cost me something in a much more meaningful way than if some Github project that I starred turns out to be untrustworthy. If my reputation stands to suffer from being careless in what I vouch for, then I have a stronger incentive to verify your trustworthiness before I vouch for you, AND I have an ongoing incentive to discourage you from abusing the trust you've been given.
CPU instructions, caches, memory access, etc. are debated, tested, hardened, and documented to a degree that's orders of magnitude greater than the LLM-generated code we're deploying these days. Those fundamental computing abstractions aren't nearly as leaky or nearly as in need of refactoring tomorrow.
I could also see them being compared with companies still using venture capital to give stuff away for free. In that case, I'm OK with that tradeoff. I'm not really excited about changing my infrastructure every few years to keep getting a free lunch.
The Digital Ocean app platform I recently migrated to is a lot newer than the "rent a VPS" model that they've had forever. Yes, it's not free like the Vercel and Cloudflare Workers I've also used recently. But it also doesn't force my app into a weird shape or to use their preferred language.
On a continuum where AWS sits at one boring+expensive end of the spectrum, and all the subsidized-pricing "we might not be here tomorrow" PaaSes sit at the other, I like the in-between spot where DO sits.