The same shit is happening today, except it's Chrome instead of IE6. We have an entire generation of webdevs who learned fuck-all from the previous round of the browser wars.
I'm a fairly young person but I've had a bit of interest in the history of computing from Unix onwards. It's all documented and out there in public archives, accessible by anyone. It ignited an interest and let me identify more deeply with my profession, plus it highlighted just how much the history of computing is cyclical (especially the mainframe->thin client->mainf^Wcloud cycle), and therefore shown me how much of the old history we can dust off and put into good use again in the modern times.
History is context. One is doing themselves a disservice by not doing some cursory reading around it.
The situation when every webdev was forced to support IE6 would be like if developers today had to support Chrome from 2011.
Not the same but pretty close.
I really doubt it’s something sinister in enterprise sized logistics. Mainly because the big guys don’t need to be al 90’ies Microsoft about it in the modern world of leaned up Enterprise. The service the big global brands come with do save the carriers a lot of money, but it’s done perfectly legal.
First there is the logistics. As a smaller carrier, you won’t really have to worry about doing BI on sales projections and what not, because Apple, Samsung and so on will simply tell you how many phones you can expect to sell, which is basically how many they’ve already produced for your region. They’ll handle everything from warehousing to shipping to your local stores pretty much without you having to do anything but sign the extremely “take it or leave it” sort of B2B contract, that also includes the big companies not charging you for products that don’t sell. What this translates to is that you can basically run your company without a logistics department or any BI related to the actual phone hardware. This saves you money both on manpower but also on not having too much inventory.
Then there the support side of things. By carrying big well known brands with a very low degree of user freedom for modifications you cut the non-carrier related support you need to offer to almost nothing. You could probably offer good money to get carriers to sell, even a well known brand like the fairphone, and they’d still turn you down because it would cost them too much money to do so.
Is this really the case anymore? Why would you buy a phone from a third party like that?
Most people I know buy their phone direct from Apple or an Android device from Amazon retail.
Remember, by being wealthy, we frequently have to pay a lot less than people who get by month to month. There should be no shock here.
On the other end of the scale, though, are the subsidies carriers pay to anyone who switches and trades in a quality device. When my partner joined my plan T Mobile paid a $700+ subsidy for his iPhone 11 in exchange for an iPhone 8.
So customers across the entire income scale finance. It’s just a matter of how lucrative that financing is for the customer. At the higher end of the scale where the customer has more choice it’s usually a much better deal.
This is a well studied phenomenon that wealthy people who can afford to pay everything on day 1, buy in bulk and all end up paying less than poorer people.
‘It runs Linux’ is not sufficient differentiation for people to be interested outside of hobbyists and highly specified niches.
If we can change that, then a low end disruption strategy could work.
Unfortunately the work on Linux desktops and phones mostly seems to be about making an iOS-alike experience.
https://www.omgubuntu.co.uk/2020/07/buy-pinephone-postmarket...
BTW, I think the convergence concept is totally valid and actually available now (although in a proprietary form) as Dex on Samsung Galaxy series devices.
Just plug the thing into a USB-C HDMI dongle and it shows a desktop interface on the display & has decent mouse and keyboard support.
Really nice for simple stuff like looking at photos you just took outside but on a big screen. And also a killer combo with the Wacom One pen display as you have your Clip Studio or Krita files all available on the big Wacom One screen yet can work on them on the regular device screen while on the go. :)
So now we just need that, but open source. :)
It could be a separate wayland session outputting to the external display with app GUI getting data from a backend via DBus. That way you could run the same up on both device and external screen at the same time while keeping the data model consistent. :)
That's the whole idea behind Librem 5 and PureOS and it already works well. All the phone apps there are just regular desktop apps made convergent to fit and work well on the phone.
See https://www.youtube.com/watch?v=onxBw5Pd45w and https://www.youtube.com/watch?v=9qB_5g2ZJYk
Why isn't it around any more?
(1) The carriers. Many people get a free or heavily subsidized phone from their carrier, who makes money from the data charges. Carriers were just not interested in phones from smaller manufacturers, and it's not entirely clear that there is no backflow of cash involved at higher levels. There is also the issue of controlling access to user metadata, always a profitable exercise.
(2) The manufacturers: why would they put a third-party OS on their phone when they control the entire stack from the silicon to the end-user's metadata through their in-house Android fork? They can sell hardware at a negative margin if they can profit from selling access to metadata, or possibly data.
(3) The apps. Developers want to target the biggest, most lucrative markets so they target Android and iPhone which already have a critical mass. You could provide a container to run Android apps on Ubuntu, but then you end up with no differentiating factor except your Android apps look like crap in desktop mode. Running in a container can also restrict the kind of data collection many apps rely on for monetization.
Another problem with apps is that many web services check to see whether the device is iPhone or Android and respond accordingly. Like the browser checks of yore ("you need at least IE 6 to use this site, try updating to a newer browser!") this gives a less satisfactory experience to end users.