Wish I had mod points for you today.

I recently made the change on a firmware product. It took me 1 week of dedicated time, and about a week of test time. The big time waste for me was that we use mysql++ so I had to get that to link against the maria c libs, then build rpm's for everything. Other than that it was a drop-in replacement and a search-and-replace on the library to link against.

You mean all the good stuff except the ability to access more than 4GB of RAM.

I'm in Ontario, I pay under $50 for 28Mb, 300GB cap. Stop going to Bell and Rogers.

I'm sure they'll show us the proof, just as soon as the car comes out of beta.

You forgot the warning that it is known to cause cancer in the State of California.

Fuzzing should not cause a crash - a crash would be an indication that there may be a vulnerability since something isn't validating input properly. A non-production system would be worthless since there's no guarantee it would mirror the production setup. Any Internet accessible server should be able to handle any security threat that comes in. Especially a server with medical data. So long as they aren't pushing enough traffic to be a DOS attack there shouldn't be a problem with the server if it's properly programmed and configured.

As with most countries, the US is easy if you know what to tell customs. For the US, you're attending a business meeting. If you're visiting a client or selling a service you'll be grilled, need tons of documentation, and spend hours at the border. Visiting India? Know who to bribe and how much they'll expect. Every country has an answer that will make your life easier.

You mean like those pilots that missed their airport by 200 miles a few years ago despite an atc yelling at them because they were on a laptop trying to figure out their company's new bidding system? People don't always follow the rules where there is a low probability of being caught, regardless of consequences.

The mariadb c connector license is LGPL, the mysql one is GPL. Not a lot of companies will create a derivative work of the database server, but a lot will want to link against the client api.

We can say the light bulb was revolutionary now, since we can see the result, but I'll bet at the time it would have been reasonable to view it as just the logical extension of scientists playing with electricity, which they had been doing for some time at that point. It's not like everyone switched from candles to lightbulbs overnight, it would have taken quite some time. While the switch was happening people probably discounted the light bulb as not being good enough, needing electricity that many people didn't have, burning out too quickly, broken glass being dangerous, etc.
If you want something recent on the same scale look at GPS. It was first deployed less than 20 years ago, and only now have most industries that rely on location data made the switch to using it as the primary source of location data. We probably have inventions today that are going to obviously be huge, revolutionary inventions in 10 years, but it's nearly impossible to tell which inventions will end up being important until everyone already relies on them.

Go talk to someone actually working as a civil engineer sometime and tell them that. Once they stop laughing they'll probably have lots of stories to tell you about drawings being wrong in hilarious ways, materials having the wrong tolerances being discovered too late and the quick patches they did to fix them, and how all modern construction is done as quickly and cheaply as possible. The difference between their bugs and our bugs? They have a group of people building their structures who can see if something is off during construction. We have a compiler that will blindly follow whatever we tell it to build, no matter how obvious the bugs.