Compare and contrast to the stats for 2013, when solar power made up just 0.16% of overall electricity generation and a negligible 0.96% of residences were fitted with PV systems.

The UK and NL are time zone neighbours, so I'd argue solar energy / duration are close also. Apparently the sun keeps shining in winter or with overcast skies regardless.

Initially I also had my doubts, but it seems we've got solar everywhere before the nuclear power mega projects are done with construction.

Take the European Pressurised Reactor. A French 'mass production' design from 1995, constructed starting 2005 in Finland, and commissioned in 2023. France got theirs running in 2025. China managed to generate electricity from a European Pressurised Reactor just a tad earlier, back in 2018, but the stats are filled with inaccuracies.

The mass production hype has been exceptionally farcical, considering we ended up with only three units.

Corporate needs their Brand™ look precisely as specified in their expensive Style Guide. IBM wouldn't want the Google vibes of Android Material Design TextFields, I imagine.

Scratch beneath the visuals, and starker technical differences appear.

Safari on iOS (used to?) has a 350ms debounce delay on every tap / click, in case you want to do a multitouch gesture.

JavaScript (Frameworks) were the only way this arbitrary delay to user input could be reduced before 2015, when Apple finally released a native API for this.

https://webkit.org/blog/5610/more-responsive-tapping-on-ios/

Learning of RFCs is a pain lol. A random RFC8064 just appeared IMHO.

The terminology are bangers also: - semantically opaque interface identifiers - SLAAC, OUID and EUI64 - NAT64 / DNS64 - '6-in-4', '6-over-4' and '6-to-4' are different protocols - link local, ULA and GULA - DS Lite (the Nintendo?)

What even?

- Rule priority is decided by selector specificity also.

HTML has also answered your these needs with the locally scoped ShadowDOM.

Restrictions on building nuclear bombs are defined in the voluntary Non-Proliferation Treaty, and is not applicaple to non-parties (India, Israel, Pakistan, South Sudan).

Every foreign intervention done by US / NATO through-out has backfired, and worsened the problem it tried to solve.

Case in point: CIA covertly arms Afghan Mujahideen fighters to wage war against the Soviet Union by proxy in the 80s - 90s. But David Hasselhoff did a song, so the Soviet Union fell apart, and Afghan fighters pivoted to civil warfare as Taliban.

Sadam Hussein was a rogue US puppet-dictatorship gone wrong. But 'freeing' Iraq from Hussein entailed destroying their entire civilisation. Just the mayhem caused a million deaths through starvation, sectorial violence, collapsed healthcare, terrorists roaming the streets, etc.

We also destroyed Korea, Cambodia, Vietnam, Libya, Yemen, Guatemala, Chile, etc. (At least for a while)

Whether Maduro is a baddie or not, taking military action requires buy-in from the UN Security Council. Specifically: nine affirmative votes from the 15-member council, provided that none of the five permanent members (China, France, Russia, UK, US) cast a veto. And it's only allowed to 'maintain or enforce international peace and security'. The charter contrasts this to building

The US should've consider how their war-plans 'maintain or enforce international peace and security' before commencing. Or even fabricate' sexed up Dossiers' on weapons of mass destruction like when the US invaded Iraq.

Self-defence is the only valid excuse for using arms without prior security council approval and acting without a plan for peace and security.

If you look at sattelite images, a large part of Canada seems covered by native forests / mountains. That's different to EU where almost all land is divided in squares of varying colours, because a much larger part of nature was destroyed for agriculture.

Not ultra-processed; just ultra-marketed.

Russia and Iran are the second and third largest suppliers, but their goods are sanctioned. They also 'only' produce half / a quarter of US output.

Also contrast this with, China (#4) and Qatar (#6) that produce 258 and 170 billion m3 respectively.

Wi-Fi and ethernet also have different IPs. And what if you also add Wi-Fi peer-to-peer (Airdrop-ish), Wi-Fi Tunneled Direct Link Setup (literally Chromecast)?

If a vendor implemented simultaneous Dual Band (DBDC) Wi-Fi, that means it can connect to both 2.4ghz and 5ghz at the same time, each with their own mac & ip, because you're trying to connect to the same network on a different band. Or route packages from a 'wan' Wi-Fi to a 'lan' Wi-Fi (share internet on (BSS) infrastructure Wi-Fi A to a new (IBSS) ad-hoc Wi-Fi network B with your smartphone as the gateway on Android.

There's also 802.11 the IEEE 802.11 standard to add wireless access in vehicular environments (WAVE) and EV chargers or IP over the CCS protocol, etc. If all cars need to be 'connected' and 'have a unique address' NAT / CGNAT also isn't cutting it.

There's also IoT. Thread is ipv6 because it's the alternative to routing whatever between wan / lan / zigbee / Z-Wave / etc with a specific gateway at a remote point in the mesh network.

And how about the new DHCP / DNS specs for ipv6, you can now share encrypted DNS servers, DHCP client-ID, unique OUID, etc etc.

It's an infuriating post really. As if IP was only designed for a small scale VPN / overlay network service such as Tailscale.

Regardless, ipv6 was to have more IP addresses because of ipv4 exhaustion and NAT?

My Xbox tells me my network sucks because it doesn't have ipv6, but this is a very North-American perspective regardless.

Well actually, this is what the Apple[1] docs instruct devs to do. https://developer.apple.com/library/archive/documentation/Co...

For .NET on iOS, the difference between managed and unmanaged objects is of particular concern. In the example you provide, the Icon Assets are objects from an Apple Framework, not managed by .NET. You might use them in the UIKit views for list items in a UIKit List View.

iOS creates and disposes these list view items independently of .NET managed code. Because the reference counts can't be updated across these contexts, you'll inevitably end up with dangling references. This memory can't be cleared, so inadvertently using strong references will cause a memory leak that grows until your app crashes.

The following is a great explainer in the context of Xamarin for iOS. https://thomasbandt.com/xamarinios-memory-pitfalls

The above still applies with different languages / frameworks of course, however the difference is less explicit from a syntax perspective IMHO