efstajas

"Version" is definitely used commonly to describe two different ... versions of the same thing, without implying that one is better than the other or supercedes it. There are two versions of the PS5, one with and one without a disk drive. There are many different versions of Windows, like Home or Enterprise. You can get hardcover or paperback versions of many books. Etc. Etc.

Mozilla "sold their soul to Google"? What did I miss?

Your iPad sounds pretty broken, that's not normal.

Like what?

Honestly, I've worked with a few teams that use conventional commits, some even enforcing it through CI, and I don't think I've ever thought "damn, I'm glad we're doing this". Granted, all the teams I've been on were working on user facing products with rolling release where main always = prod, and there was zero need for auto-generating changelogs, or analyzing the git history in any way. In my experience, trying to roughly follow 1 feature / change per PR and then just squash-merging PRs to main is really just ... totally fine, if that's what you're doing.

I guess what I'm trying to say is that while conv commits are neat and all, the overhead really isn't really always worth it. If you're developing an SDK or OSS package and you need changelogs, sure. Other than that, really, what's the point?

Holy shit go touch some grass. Jesus Christ

So you're talking about SaaS / business tooling then? Again though, that's just one of many segments of software, which was my point.

Also, even in that market it's just not true to say that there's no incentive for it to work well. If some new business tool gets deployed and the workforce has problems with it to the point of measurable inefficiency, of course that can lead to a different tool being chosen. It's even pretty common practice for large companies to reach out to previous users of a given product through consultancy networks or whatever to assess viability before committing to anything.

Then we're very far away from the 21st century though.

I don't really get this point. Of course there's a financial motive for a lot of software to work well. There are many niches of software that are competitive, so there's a very clear incentive to make your product work better than the competition.

Of course there are cases in which there's a de-facto monopoly or customers are locked in to a particular offering for whatever reason, but it's not like that applies to all software.

I gotta say mRNA vaccines. It's not technically a 21st century invention, but much of the work to make them viable started in the early 2000s. The speed at which the COVID vaccine got developed and widely deployed was honestly incredible and a massive W for humanity. I remember thinking a vaccine would be years away.

There's no reason your clients can't have public, world routeable IPs as well as security.

There are a lot of valid reasons, other than security, for why you wouldn't want that though. You don't necessarily want to allow any client's activity to be traceable on an individual level, nor do you want to allow people to do things like count the number of clients at a particular location. Information like that is just unnecessary to expose, even if hiding it doesn't make anything more secure per se.

They sell AirTag location data? I honestly find that hard to believe. What's your source on this other than big tech bad?