gsmiro

> Pule did it, I did it – we do this, as humans, we humanise seacraft. Vessels are christened under bottles of fizz. They’re given nicknames and ascribed character.

I find interesting that by even reading about boats one tends to humanize them but it seems to not happen with planes and cars.

Probably it has to do with the long relations kept by crews and the ships they sail in.

I have a 2013 MBP and mu wife a cheap 14" Dell bought around the same time. Fun fact: using my Samsung TV as a second display didn't work in MBP running Mavericks and worked in the Dell running Win 7. After I upgraded to Yosemite/Win10 things got inverted and now I have to stop coding in order my wife can watch Netflix in the TV with her girlfriends...

Bottom line: windows has crappy driver support for old hardware

> It's just a mess. I'd expect a relatively painless experience: install dev tools, start a new project, build and go! But no, it's jumping through hoops, requires understanding a myriad of different SDK/platform versions and a constant churn in keeping your apps up to date with new versions while trying not to break backwards compatibility.

> And a big part of this mess comes from the fact that device manufacturers and mobile operators are unwilling to keep old devices up to date (and Google can't force them, while I think they should with some kind of licensing contracts), leaving customers exposed to security flaws while keeping the developers churn high with multiple versions to be supported.

Is it only me or there are tons of similarities to C# and the .Net environment?! More and more I feel Google just ends up with the same solution MS came up with in order to handle the diversity of vendors using its platform and their conflicting interesse.

For an example of how oversight do nothing for the end user take a look at the Brazilian model of state regulation "agencies" and how they get influenced by the bigger companies.