3,760 karma · joined May 10, 2020
Depends on the distro. I used to break Arch all the time. It's fun and teaches a lot, but at some point it gets on the way of productivity. It's a choice.
If you're on Windows and want to try Linux, start with Ubuntu. You can do your daily business for years without breaking anything.
I'm not saying this is an intrinsic moat, just that there's a barrier to change.
It's analogous in the API space. OpenAI is demonstrating to be reasonably good at it for developers. They've been shipping significant features and improvements. Unless they lose pace, they have a moat, at least temporary.
I'm sure they have at least a couple jumps in their bag.
Let's not forget inertia, as well. Migrating models is not a trivial project. To gain OpenAI customers, competitors need a considerable jump to justify, which I don't expect any of them to achieve before OpenAI itself delivers their jumps.
The main issue here is "are there mistakes, in the first place?".
Maybe people will become tolerant to machine mistakes. Engineers make mistakes, but it's expected. And the kinds of mistakes engineers make are human.
Machines make mistakes that look silly. The kind of mistake "an engineer wouldn't make".
So these apps will probably tackle an unserved demand (things not valuable to justify an engineer). Anything else I predict will continue to use engineers - more productive with AI support.
Nuclear powers don't want to facilitate other countries joining their club. Popularizing nuclear reactors will, as it did with India.
Then they should not publicize it. They could license only to Google, but Google isn't interested. Instead, publishers need to publicize, which is... expected? Once they publicize, they can't claim the public is not allowed to read. It's like sharing a printed newspaper with my friends. Publishers shouldn't be able to prevent it.
The LTD idea misses one point that could apply to a larger (most?) subset:
Let initial LTD customers be patrons that have insider view and an active role in the product development and roadmap.
Early adopters would love this opportunity, if they buy into your vision. Some might even perceive more value in the product influencer / insider role than the MVP itself, at first.
I mean, we are a heavily communicative species. The most of all species by a very, very large margin...
Understandably, since, in this case, surface area is more intuitively captured by our brains than volume.
Also because we are very small. The amount of water, from our perspective, makes it look like a water planet.
Because browsers have an autocomplete feature.
Yep, they started with our eye balls. In exchange, we are getting "relevant ads".
Also our frontal lobe. In exchange, we get depressive dopamine releases.
C'mon folks, they're opening up for free to 99.99% of potential users what cost hundreds of millions of dollars, if not in the ballpark of a billion.
Let's appreciate that, instead of focusing on semantics for a while.
Ok, in some cases I see why html would make some sense. In those cases, my opinion is: send text and invite the person to view markup content in their browser.
The e-mail context is not suitable for markup, styling, and all this stuff.
Especially when using a modern storage medium, which most servers nowadays use, I doubt that filesystem I/O will be a bottleneck for the vast majority of use cases.
I/O is extremely fast and will be negligible compared to other stuff going on to serve those requests, even running queries themselves.
The CPU work done by SQLite will vastly outshine the time it takes to read/write to disk.
It might be a bottleneck to reading if you have a very large database file, though.