If we struggle with leap seconds now I can't imagine how much fun a leap hour is going to be when it happens.

Y2K, 2038 and then the leap hour.

to OpenJDK.

We did so in 2019 when Oracle first started rattling the tin. It's a pretty easy transition now and with packaging like AWS Coretto, something everyone should be considering.

This nonsense again?

The EULA limits their liability to the software fees paid. They're never going to have an agreement that makes them liable to consequential losses if they can't control what they might be and charge accordingly.

Cover for consequential loss is never going to be included in a standard software license fee.

The same PC/Windows OS/Crowdstrike based system could be used for an office worker or critical infrastructure.

No single license fee would be suitable for the very different consequential losses in those two situations.

China is highly dependent on imported fossil fuels. It has little domestic oil and gas and at current rates of consumption its domestic coal reserves will last another 40 years.

It makes total sense for China to take the medium term view and move to as much renewables as possible. It will also steal a march on the west and profit from supplying the technology to the west.

Mean while Trump is owned by the oil barons and is interested in himself which is a short term goal.

Leap seconds happen every few years and while they may be a chore, they are a familiar chore and we can learn how to deal with them.

What are the chances that if we move to a leap minute every century or so we'll spend the next 75 years kicking the problem down the road, 20 years panicking about the upcoming massive change and 5 years working to replace or fix all the systems that don't support a leap minute? Y2K again anyone?

Better to properly handle leap seconds now and for evermore I think.

You'll need to buy a license key on line.

This disk will just be a distribution for large files (not every one has high speed broad band yet) and advertising medium.

When it comes to technology, most people are 'kiddies'. They just want something that works and it easy to use. They follow the script like any kiddie. Most people what something that works and does something useful - they're not interested in how it works.

An iPhone app that can read the ink is special to them because it's available and works.

You have a link local address AND a different global address. It's the global address that will be routed.

Link local addresses are useful locally. There's even a link local system for IPV4 but hardly anyone seems to know about it. From Wikipedia and various RFCs - "In IPv4, the block 169.254/16 is reserved for this purpose, with the exception of the first and the last /24 subnet in the range. "

This would allow the IPv6 world to talk to all of the IPv4 world but does nothing to allow the IPv4 to talk to the full IPv6 world.

How would an IPv4 user connect to a new IPv6 service that did not also have a corresponding IPv4 address? You'd have to limit the IPv6 address space size to that of IPv4 which rather defeats the object!