Earlier quoted context omitted.
Not really, honestly. My car is useful. An adaptable car would take more design effort, so likely cost more. I have no use for a monster truck, a boat, I can't pilot an aeroplane, and if I did sink or crash-land my car then I'm out one car that I have use for, and need. (Wheras, if I hire and crash a boat now, my car is still fine). And I don't want to imagine the insurance, MOT, or servicing cost for a vehicle which…
I think you're stretching the analogy beyond the limit of its usefulness :) A phone is always on you anyway, usually in your pocket. What disadvantage do you see from making it the "universal compute unit", so to speak, driving your tablet, your laptop etc - which then just become combo display/entry devices? If you don't need a device in a particular form factor, then you just don't buy one, and the question of stor…
The very fact that it's a compromise means it will be worse than each of the individual solutions, but it will enable something new - and I'm not seeing anything very desirable in this space to be worth the compromise.
What exactly the disadvantage is depends on the exact compromises made, but USB-C is a small socket, many more connects/disconnects will lead to failures. Wireless links will struggle to be good enough for display output. Losing your phone on a night out would be much more disruptive and render you digitally-stranded.
If it drives your tablet, you don't get to give your tablet to your kids to play with and retain your phone. If it drives your laptop, you can't lend your laptop to a guest. If it drives your TV to watch a film, you can't be sitting around with other people and receive a text message and glance at your phone like they can. If you're working on a fullscreen spreadsheet, you're not going to want to interrupt it for an incoming text - and now you have no phone to glance at.
In order to make it a universal compute unit you increase the amount of code on it - attack surface goes up, need for patching goes up, complexity goes up, room for bugs goes up.
So you have a phone which is small, personal and convenient, and you have an empty shell of a tablet, an empty shell of a laptop, and an empty shell of a desktop - all of them could have their own smartphone class ARM CPU for say 5-20% more cost, but without it they're all useless and taking up space and you can't use more than one at a time.
But you also have a phone where you have to fiddle with the software all the time when you switch roles - disable notifications, connect USB-C things, connect bluetooth device so you can carry on using it as a phone, plug mains power in, redirect audio out to be bluetooth only for phonecalls and system audio to go to speakers, deal with 'ok google/hey siri' listening so it won't fullscreen over your work...
And for what benefit? Where's the call for "I wish I was in a hotel carrying my smartphone and the husk of a laptop, that would be so much better than having an actual laptop". Where's the call for "I wish my iPad couldn't do anything unless I had a thunderbolt cable connecting it to my iPhone, that would be really conveninent". Where's the call for "I wish my main keyboard was a portable bluetooth foldup one" or "I wish I could take my employees' $400 laptop and instead give them a screen, a keyboard, a mouse, a mains cable, a port adapter, and a big sheet of instructions, and some more training".
I guess the disadvantage I see is that companies are awful at integration, awful at UI, and the experience on the user (me) is that many things related to connectivity and integration between systems don't work, much of the time.