Once you have that in play, companies will tend to standardise on one DB platform for most deployments because (a) you don't want to have to keep multiple skillsets up to date and (b) you never know when that new application will suddenly evolve into requiring feature X which MySQL doesn't support properly, possibly simply by organic data growth.
Also, in some cases, it's probably more expensive proving you can run on MySQL than it is to simply open your wallet to start the deposit for Larry's next yacht...
1) The state legislature is run by people. People are (a) greedy and (b) want to stay in power. When car company lobby groups see potential competition, it's cheaper for them to bribe, sorry, "provide campaign funds" to a pet politician than to actually compete. Those people take the money and decry the horrible, horrible Tesla company for daring to defile the hard working people who they've been speaking to (read - taking wodges of cash from).
2)There are some reasons, e.g. here and various Google searches would give you differing opinions. Perhaps it's simply that, because of their current low sales volumes, dealerships just can't provide the right environment to sell Teslas.
And before someone points it out, yes, I'm aware the mortality rate from Ebola isn't comparable to the flu, but the overblown hype about it stands.
In specifics - the advertisement to sell the ticket is an "invitation to treat". Proferring money to the seller is the "offer" and it's implicit that the offer is on the terms of sale advertised in the invitation to treat (including terms regarding prohibition of cameras/filming) and the seller accepts the offer. The buyer could place an offer whereby they offer to buy the ticket buy allowing filming. The seller can then reject the offer and/or present a counter-offer (e.g. you can film if you pay some fee to allow filming).
The argument from the premier league is around videoing clips off the TV and posting online which is pretty clear copyright infringement.
The 30 days "record" does seem to imply he's doing more than others have done which is rather misleading; it's certainly different from submarines, though.
No, you don't use main memory as a write cache, that would be idiotic. You use it for read cache. Any updates will be written to disk (and memory) before acknowledging to the client.
In any case, it doesn't matter how good your batteries/UPS are if your server or DB software crashes for any reason and you have uncommitted writes in memory, hence why caching writes on a database is a Bad Idea (TM).
Bullshit. Well, either that or our network admins are numpties. We had a switch go down in a data hall. We knew the switch was fubar as we'd lost connectivity to a number of devices at the same time. Networks wouldn't admit a fault. We eventually got moved to new switch ports and lo, everything started working.
The usual approach to any network fault in our place is "replace your NIC". That has, in my memory, fixed maybe two faults.
As for modifying code yourself, that requires a whole set of skills & disciplines many admin teams don't have - I know our team/organisation would struggle with that. There are, of course, 100s of companies who are quite happy downloading source & patching/maintaining it themselves.
Other than that, there's some good advice in there. Version control & release/test cycles are key for any software product.
Dead? No excuse for laying off work.