So we already have an effective way to store heat which can work for decades without servicing and is also cheap to produce (in terms of money and energy consumption).

Planned lifespan of Starlink satellites is 5years.

Is supported on more platforms, has more developers, more jobs, more OSS projects, is more widely used (Tiobe 2024). Performance was historically better, but c# caught up.

Copyright laws have quite strict rules on what constitutes a copy, and this was tested in courts many times. This rules also apply to works produced by LLMs.

I code in Go mainly (also Java and Rust) and never experienced what you describe: simple addition of a field to a struct does nothing if not used in code. And the use is simply checked by compiler.

However, I did work alongside a Rails team which had major gripes with this. They called it brittle tests: whenever they made a simple change (like adding a field), half of their tests would fail. This really lowered devs' confidence in their codebase and slowed the changes to a halt.

For example, CAs present in Firefox, that might give you pause: Beijing Certificate Authority, China Financial CA, Guang Dong CA

The CA system in browsers is inherently broken and it allows state actors to MITM you and see all your traffic if they: 1. have ability to capture IP traffic (requires cooperation with ISP) 2. have ability to generate rogue certificate via cooperation with CA

It is SSR with Velocity templates.

The problem is that at that point liquid hydrogen already spent 70% of the energy stored in it (80% efficiency of electrolysis * 40% liquefying efficiency) .

Who the f* writes this articles?