Readit NewsIs this true? I couldn’t find another source discussing it. That would be insane behavior for a package manager.
For roads, brushes, wastewater, sewer, electricity - it's because these things are public utilities and ultimately there is accountability - from local government at least - that some of these things need to happen, and money is set aside specifically for it. An engineer can inspect a bridge and find cracks. They can inspect a water pipe and find rust or leaks.
It's much harder to see software showing lines of wear and tear, because most software problems are hard to observe and buried in the realities of Turing completeness making it hard to actually guarantee there aren't bugs; software is often easy to dismiss as good enough until it starts completely failing us.
A bridge is done when all the parts are in place and connected together. Much software is never really done because - it's rare to pay until we have nothing more to refactor - the software can only be as done as the requirements are detailed; if new details come to light or worse, change entirely, the software that previously looked done may not be. That would be insane for a bridge or road.
This effect gets accelerated when teams or individuals make their code more magical or even just more different than other code at the company, which makes it harder for new maintainers to step in. Add to this that not all code has all the test coverage and monitoring it should... It shouldn't be too surprising there's always some incentives to kill, change, or otherwise stop supporting what we shipped 5 years ago.
This works pretty well for fighting limited wars where part of the justification is to develop and maintain military readiness. Would it still be true in a large scale war against China - could you pump out a million drones a day - or would you wish for a doctrine that included reusable drones?
I think something to keep in mind, the US hasn't fought a war on the home front since 1865. The Spanish American war, WWI and WWII, Vietnam, Korea, the Gulf war, Afghanistan, Iraq - none of these were fought on American soil, with the exception of Pearl harbor, which was a navy base, not a major manufacturing site. So we haven't really had to reckon with what happens if our homeland is under fire - sure, we drilled for it during WWII, worrying about Nazi bombers and Japanese sabotage but neither actually happened.
It doesn't look like our wars are going to get closer anytime soon, but modern planes and rocketry have much greater range than in the 1940s the last time we were at war with countries with significant resources. If we ever come head to head with China, their missile capabilities could be a real concern.
But there is a customer experience reason. As an iOS user, I very much appreciate that I can ask Apple to cancel some bullshit subscription that used to otherwise try to lock me in behind a labyrinth of added friction and timewasting.
Not every problem is technological.
Anyhow I do see your point that narrowing user options can lead to better UX - if you actually like all the tradeoffs they make. The problem is if you don't, your SoL. And in this case the trade-off is Apple taking a giant extra cut so... I think it's reasonable that folks don't like that trade-off.
So it can carry the 2 extra people, it can carry some luggage, it can't carry both, and it can't carry neither?
20 minutes after that the Lyft driver keeps texting me “where are you?!”. Their turn to wait!
Saw later they just started the ride without me and drove to my hotel.
Lyft said “this trip was completed, no refund”. Welp, app deleted.
It's a smaller piece of a bigger pie.
To answer your question, the right question to ask is why go public when you can remain private? Public means more paperwork, more legalese, more scrutiny, and less control for the founder, and all of that only to get a bit more liquidity for your stock. If you can remain private, there really isn't much of a reason to not do that.