Re: Penny in the air?
"Maybe I can get a promotion to manglement when I return to work ... ?"
No, you need to do more work on your IQ.
40471 publicly visible posts • joined 16 Jun 2014
"It's suggested this won't happen again"
What won't happen again?
This particular problem - maybe not now it's fixed unless, of course, somebody reverts to an older version or looks at the new code and thinks "That's not right for a child"?
Or developing against an insufficiently detailed spec that assumes culturally specific knowledge on behalf of the developer?
"Clearly welding extra money on phones for development of Android isn’t going to be favourable with users"
Go back to your 2nd paragraph. Android was and OS project before Google took it over - and they still have to make the kernel OS because of GPL. If the smartphone manufacturers had chosen to collaborate in developing it - as, for instance, Intel has with the kernel - they could have provided themselves with a GPL core. It would still have raised the problem of non-collaborating manufacturers trying to use it so they'd need to have added a non-GPL collaborative userland. Of course the costs would have been added to the purchase cost but spread out over many of millions of units and wouldn't favour one make over another.
TL:DR It didn't have to have turned out as it did.
There's an entirely different way of looking at this.
An OS is simply a part of a computing device. Without one the device is incomplete. A vendor can develop their own, buy it in or, as a middle way, develop one in collaboration with other vendors. Developing their own was, of course, the original way of doing things.
The OS can be supplied to the purchaser by various means. It could be licences as a one-off payment as part of the original package. It could be leased. It could be a mixture of initial payment with an optional support contract. It could be ad-supported. And, of course, the collaborative development approach* has enabled the free download of Linux and the BSDs inter alia.
It would have been feasible for smartphone manufacturers to have got together to develop a Linux distro which could have been provided to their customers as part of the one-off payment for the device. However Google has managed to divide and conquer them with its own Linux distro at the ongoing expense to their customers of eternal slurping.
*If you look carefully you'll find that H/W makers such as Intel contribute a lot of Linux development so in fact one-off payment as part of the the H/W applies even if you run some other OS. We Linux users thank you Windows users for your contributions.
How about we make that paying for a specific service such as email? In that case, yes. I pay for a domain and for someone to provide an email service for that domain. It gives me the freedom to choose not to use an ISP email address and hence to change ISP if I wish and also freedom from having my activity tracked by "free" email providers.
I need to have a gmail address as the system ID for my Android phone. It's actually a garbage address with no meaningful personal ID attached - and now Google seem to want me to provide its profile with a date of birth on "legal" grounds. The legality of that demand seems to be negative under GDPR.
"an old spare tower PC I had at the time, I ended up with a very expensive doorstop"
Almost by definition something that's old and spare is no longer expensive as you'd already written off its value. And if you'd kept the Windows distribution disk (or did you transfer the licence to another machine) you'd have been able to reinstall it.
"They are just people who need a tool to accomplish a job and use the best one they can find or afford."
I seem to spend a lot of time these days putting together various PDFs including the weekly one for my wife's patchwork group* and the more occasional but bigger ones from our history group's out of print books**. I've no idea what Windows & Mac software would be would do or cost but in all cases final assembly is done by the simple pdfunite, image manipulation by Gwenview, Gimp, Pinta and Kolorpaint as required, OCR of scanned pages*** with ocrmypdf****. Vi is the tool of preferences for sorting out the OCR artefacts although sed would be an alternative. QGIS handles occasional mapping work. LibreOffice, of course does the word processing and spreadsheets and conversion to PDF. I seriously doubt that I could find a more useful set of tools for any amount of money whether I could afford it or not.
* SWMBO does her illustrated notes by hand, rather like that old book on BASIC, I do the photography. NextCloud syncs the results between our laptops, both of course, running Linux.
** The PDFs produced for the printers with whatever tools were used there are far too big. I discovered that Word lies when it "crops" images. The .docs were bloated by masked by uncropped images, in one case multiple copies. From LibreOffice it was a case of Edit with external program using Gwenview to crop and reduce the resolution.
*** The scanner on my Brother AIO saves PDFs to an ancient Buffalo NAS which I assume runs an ancient Linux, otherwise I'd point it at the Pi running NextCloud on a more recent Linux.
****The inevitable OCR layout curdling resulting from the image not being precisely aligned for scanning is dealt with by a tool I knocked up years ago using Lazarus to deal with the same problem in downloads from archive.org. I could have used Delphi for that. I last used Delphi about the same time as I last used MS Office - about 14 or 15 years ago.
"traditional employment models"
It depends on what you mean by "traditional".
A tradition hereabouts was that of the domestic textile industry which was essentially that of self-employment. In fact my father was the only one I can trace in my male line who spent his entire working life in what you probably consider a traditional employment model.
I once got a handed a system to work on of which the C component was obviously somebody's "My first C program". "Somebody" was the boss and he'd been a COBOL programmer. He'd discovered macros and introduced a few - MOVE was one - to make it a bit more COBOL like. As I worked on it I realised that some of the code I needed to modify was wrapped up in some of the instances of the macros so eventually (fairly quickly, in fact) I just ran the whole thing through cpp. This was actually the distant 2nd or, as I discovered some months later, 3rd biggest problem that the system had.
NextCloud on a Pi as the NAS. Nextcloud client on the laptop just has a look round on start-up, syncs if it finds a network with the server on it, shrugs & waits until next time if it doesn't. As the server has a shared folder sor stuff that I have to work on for SWMBO it quietly syncs the two laptops.
"I am NOT spending the rest of my life being blamed for the fact that she lost all of her photos for the fifth, sixth, and seventh time."
When my cousin's wife lost all her photos and everything else for the first and only time - Windows & ransomware - it was a live Linux CD that got them back (early ransomware wasn't that clever, it didn't actually overwrite the original files) and installation of Linux that has stopped it happening again.
Having to open a terminal to get something to work is rare. Choosing to open a terminal because it's easier and/or less opaque than the GUI alternative is less so.
A more frequent use of a terminal session is do stuff like whois or ping because I like to see who and what might be lurking behind some link somebody's trying to interest me in. The most frequent, of course, is to use a Real Editor if I've got some big chunk of text to operate on.
SCO, as was, did not come from any sewer. SCO were a perfectly respectable company selling a good small-system Unix*. It was the basis of a lot of SME on-prem business systems in the '80s, '90s & early 00s.
However their pricing reflected a near-monopoly situation. When Linix came along they didn't have sufficient commercial nous to recognise viable competitor when they saw it. They should have adjusted their price. Not to zero but to one which reflected their quality advantage over early Linux but recognising that they were competing with free-as-in-beer in terms of functionality.
After the ensuing debacle resulting from Linux becoming a suitable platform for running the likes of Oracle & Informix they were bought out by a business that decided that litigation was their only salvation. That's when things got awry.
*Originally they were a reseller of Xenix but then took over development of the next generation.