Re: You DO eat rocks as food.
My house is an aggregate of bricks, mortar, tiles and other building materials. This doesn't make a brick a house.
27 publicly visible posts • joined 28 Oct 2020
It certainly might help. This was the push I needed to install Mint on my old but still good laptop.
The OS is increasingly irrelevant. How many users need anything that isn't available on Windows, Linux and Mac?
Moving for me highlighted just how shit Windows is nowadays. I now have an OS that can cope with a USB-C monitor with integrated hub without having to plug it in three or four times before the keyboard and mouse work. Better still, it includes a scanner tool that can handle multiple pages and create a PDF without having to search for a free replacement for the crap in Windows. I can use Docker without a massive faff involving WSL. Brilliant! There's certainly no going back.
You've asserted twice that the "vast majority" or "vast numbers" of git users have "no idea" how it works. What are you basing that on? I'm a daily user of git, so are all my colleagues, we know how it works or we couldn't use it effectively. Who are the users that don't know how it works? I would expect most git users to be developers whose job it is to understand this stuff.
I used Informix on a project in the late 90s as a whippersnapper. It seemed fine until someone from Informix had to come out and fix the database for us armed with a magic floppy disk. It had run out of storage and it was apparently impossible for us to fix ourselves because any operation, including anything that might have freed up space, required it to log that (maybe it was the rollback logs, this was all new to me at the time) and it couldn't - there was no space to do so.
No doubt there was incompetence on our part involved, and probably someone here can explain why that's all bollocks and that we could have fixed it, but that's how it played out. We stuck to Oracle and Db2 after that.
So a customer who fails to have adequate backups deserves to have criminals attacks its IT and destroy its data? You actually think that? All the hobbyists running little niche websites in their spare time to support some community or other deserve to have it all destroyed and lose all their email because they didn't have the money, time or expertise for off site backups? Yes hardware failures can happen but they are relatively rare and the storage, one would hope, would be resilient and replicated. People make a choice whether to accept that risk or not. Doesn't mean they deserve to have criminals destroy it on purpose.
I'm not sure that's right. It might be, I'm not a lawyer. My understanding is that I could fork the Linux kernel and distribute my fork under a licence with additional terms as long as it complies with all the requirements of GPL2 . If that's true, wouldn't if follow that the main project could change licence for future releases requiring source of any derivative works to be published openly to everyone?
Perhaps a silly question but if the Linux community is so outraged by Red Hat's actions, can we expect a license change to the Linux kernel along with the multitude of other upstream components Red Hat uses forcing them to make their source code freely available if they want to make use of any future release? The options for Red Hat would then be release their source code or maintain their own fork of today's latest version of whatever they use.
To answer your answer in one single word - bollocks
While it has its risks, cloud providers have massive advantages of scalability, expertise, etc. An in-house team of sys admins is unlikely to be able to keep up in the same way, be available around the clock, not be ill, not go on holiday, not be a bit shit at their jobs, be up to date on every patch and new feature. I've had far less trouble on AWS than I used to frequently had with teams of incompetent DBAs, Unix admins stuck in the eighties, etc - all blaming the devs of course and putting up roadblocks to getting to the bottom of things
This article is quite interesting in explaining the problem https://insideevs.com/news/376037/tesla-mcu-emmc-memory-issue/
Tesla's response has been woeful - eventually owning up to the issue but only agreeing to fix it once the car is broken and if it's done less than 100k miles. https://electrek.co/2020/11/09/tesla-emmc-failure-touchscreen-offers-extended-warranty/