zaro

Actually if you read the links in the 'What's new' section, most of them start with the reason why they needed to break the backward fucntionality for this feature.

Sure but what ws their recommended way instead of putting systemd in the image, just use supervisord. Not even comparable.

Anyway , the past is the past. Docker were clearly wrong in their decision to put off systemd inside containers, and was most probably for political reasons because it was very very requested feature.

And what drove my attention to the "I don't accept systemd patches" was the need to run systemd in docker container. Which by digging a litte bit about I found it will be possible in non priviledged mode, but docker didn't want to merge it.

I don't see anything philosiphical with that, it's just plain refusal to cooperate in any way with a potential compentitor.

This was several years ago, now this is not an issue anymore, but it's still telling of the toxic corporate culture Docker had back then.

Not a big loss, IMO. I still remeber when there was somebody on a dockercon with "I don't accept systemd patches".

I don't understand why the bug fuss about M1. After all M1 is 5nm CPU. AMD Renoir is better than Intel for the same reason, it's 7nm while Intel can't get below 10nm yet.

So while M1 is probably a great CPU I expect its advantages will mostly vanish once AMD and Intel move to 5nm also.

You should check Gnome Disks, it alrady has bencmarking builtin and is installed by default on Gnome environments.

ASIC stands for application specific, and since thei IC is application specific - used only in certain hardware along certain software, it's kind of correct to call it ASIC.

> but it still boggles the mind how these enormous companies, used to throwing their weight around in other tech spaces, keep getting video games so wrong.

This sounds naive IMO. It's not that they are getting it wrong. They are simply throwing their weight into changing it into direction that favors them.

I get the code is data thing, but I don't really find it that much useful. And there is a good reason most languages don't allow it - other people :)

The unless example is a good one. So while you can trivially implement 'unless' in lisp, most probably in a large code base, you'll en up with 'unless', 'if-not' and depending on how creative others are probably also 'negat-if'.

> In general, I'm not blown away with Canonical's track record.

Yeah, they really wanna be like Apple, but end up being more like Google, starting a lot of projects and abandoning them in couple of years.

I didn't even get to sync, stopped reading on 'save'.

Definitely. But then again if these brain compete to work on something like this, maybe they are not so big after all.

> The IPCC predict 2 degree rise by 2050, and a 6% reduction in gbp growth, not gbp.

IPCC models don't take into account the feedback loops. Also , things are moving faters alredy that they have been anticipating, so expect these predictions to be completely obsolte in few years.

> You don’t avoid using JS at all but only use it where it benefits the user. For example, the users benefit from having those forms having nice validation, dynamic lookups, etc. but they don’t benefit from using a vDOM on top of the far more efficient browser DOM or loading an entire general purpose templating framework instead of just using the DOM to update an existing form.

I am sorry, are you talking about example todo app ? because for most apps with complex navigation, data entry, and validation this is absolutely not true. Just use the DOM , might be somehow feasible with webcomponents, but they are years late to the game.