They guarantee an uptime of 100%, but if they don't have much incentive to keep that guarantee.

A downtime of 4.32min gives a 1% credit on the monthly bill. Up to 43.2minutes gives a 5% credit, up to 7.2 hours 10%, up to 14.4 hours 25% and a downtime over 14.4 hours only gives a 50% credit.

https://docs.fastly.com/produc...

The problem is that as long as US laws are written the way they are, storage within the EU is not enough to secure the information. The US can require any American company to give out information regardless of where it's stored. The only way to secure the information is not to do business with companies based in the US. Microsoft, Amazon and Google are starting to see customers turn away from them since they cannot guarantee 100% data protection.

The big problem with solar energy is that it is not reliable.

A quick look at Germany and few other European countries' solar production, today Feb 2nd. (Source: https://www.electricitymap.org...)

Germany: 7.5% of installed capacity
Denmark: 24.11%
The Netherlands: 14.15%

Won't installing windmills work as a backup? Nope, wind can perform poorly at the same time as solar is performing badly.

Germany: 11.81% of installed capacity
Denmark: 4.45%
The Netherlands: 37.9%
Sweden: 12.54%

Solar & Wind perform well on a yearly basis, but that doesn't help those days when it is cloudy and there is little wind meaning that a considerable number of backup fossil powered plants must be maintained which is costly and not very environmentally friendly.

It is madness scrapping nuclear power which is a reliable and relatively environmentally friendly power source.

Back to the good ol' days of store and forward using uucp. No need to invent something new :)

Edge Chromium offers advantages to Chrome for some use cases so it is great that MS have decided to offer it.

• Synchronization of tabs/bookmarks/etc does not require a Google account.
• Native Win32/Winform/WPF/UWP applications will have access to the Chromium based WebView2 component
• It integrates with MS' different enterprise technologies such as Information Protection,
• It has IE Tab like functionality built in which makes it easier for business users that need to access legacy internal applications / computer management interfaces.

What? In what respect does OOP differ from any other programming paradigm when it comes to using other layers / libraries? Regardless if I am using C, assembler, C++, C# or F# I expect that functions / APIs / libraries / OS calls fulfil their promise. If I had to verify the whole stack including glibc and kernel each time I wrote code I wouldn't get much actual coding done. The BT code in question is written in C (not object oriented) and the bug is due unitialized stack variables and making a callback without checking if a handler has been set. The main reason we are seeing bugs like this pop up again and again is that we are still relying on code written in languages that do not protect against these type of bugs.

According to reports senior developers in the US have been replaced by outsourced developers with less or no experience from the aircraft industry. https://medium.com/@dodiyadhar...

People are imperfect and C is a non-safe language which allows the programmer to f-up without ever realising he/she has done so. Even experienced C-programmers make mistakes that have have more serious consequences than if the code had been written in a different language. That is why we are seeing serious bugs that have gone undetected for years and sometimes decades Raw pointers, variable arguments without type safety, nul-terminated strings and no bounds checking is a recipe for disaster. The saddest thing is that even though it has been known for decades how C code should be written to minimise the risk of serious bugs, text books and tutorials available today still have code which should never exist in production. New C programmers are doomed to make the same mistakes as new programmers did in the early 70's and the same mistakes I made during the 80's.and early 90's. Now that better alternatives exist it makes sense to start the move away from C to safer languages that also have been designed with concurrency in mind.

The examples I gave had nothing to do with increased production costs. It was examples of prices that were raised only because the companies could get away with it. Pharmaceuticals are not a normal type of product, with most other products it is easy to abstain from buying or buying a different product. But increasing the price several hundred percent of a life saving drug when there is no increased price in manufacturing is extortion and should be treated like it.

As long as the pharma companies have a fair pricing instead of raising prices when a drug becomes more popular then they should be fine. Extortionists as Mylan (EpiPen), Abbot (Norvir), Gilead (sofosbuvir) should be stopped from taking unfair advantage of their position.

As a developer Macbooks have traditionally been great for Windows developers with a stable host OS and the ability to run MacOS, Linux and Windows apps. An ARM Mac will not be as attractive since Windows performance will suck and even Linux will be less interesting since some tools are x86 only.

As a developer I use many applications that have a heavy use of function keys and I find it much harder hitting the right key on my MBP with touchbar compared to when using a physical keyboard. Also, there is no tactile feedback that a press has been registered which really sucks, With haptic feedback it would be a little bit better but Apple have moved from having the best laptop keyboards to having keyboards that more are on par with budget laptops,

I am quite confident that if I visit one of the larger Pr0n-sites I will be able to prove you wrong.

The Amiga was a great machine for games, but a terrible machine for businesses. To start with it had a low res display with low frequency making it difficult to work with for longer periods compared to Mac/PC. Then not enough effort was made to make sure good tools for software development existed.