The big downside is that, for backwards compatibility, the default must still be unsafe code. Ideally this could be toggled with a compiler flag, rather than having to wrap most code in “safe” blocks (like rust, but backwards).

One potential upside that people don’t seem to be discussing is that the safe subset could also be the place to finally start cutting down the bloat of C++. We could encourage most developers to write exclusively in the safe subset, and aim to make that the “much smaller and cleaner language” trying to get out of C++.

I always thought that people using searx etc over duckduckgo were just gluttons for punishment. Having gone an entire morning without search, maybe now is the time to dive down that rabbit hole…

Thanks, fixed! (TIL you need the https:// bit on Lemmy)

There is, they just don’t publicise it. Actually one of my favourite features of the service tbf. Just load up a web page and all my messages are there, regardless of where they came from.

Underrated comment.

I do wonder what percentage of Linux users reject the survey compared to Windows users. Not that it’s changed much, but every little helps right?

Is that an issue if you need to login first?

So yeah, going 100% air-source heat pump if you’re area regularly spends time around -30°C (-22F) might not be the best idea. Though even the last report you cited said it might be 1.5-2x as efficient as resistive heating. And that Site 1 with bad COPs was because they manually lowered the fan speed…