Local onboard ‘AI’ is used for image recognition, classification and target locking usually, and it flies using essentially agrodrone software missions (ardupilot). It’s not completely autonomous, just mostly hands off.

Enterprise distros often include gnome as part of default installation.

It literally isn’t.

the thing just doesn’t care about r*ssians (they don’t care as well), it could reverse the invasion or stop it any day, without any consequences.

tl;dr: they are trying to invent a way to get more money from retired people

Also stalin vs. spanish communists.

Повністю погоджуюсь зі словами авторки, але. На жаль ‘технологічний суверенітет’ це фантастичний звір якщо нема фундаменту на якому будувати цей суверенітет, це не більше ніж слова. Хоча велика війна і дала нам трохи копняка в бік розвитку, без нормальної освіти все це тимчасова історія яка веде в нікуди.

I’ve always had either problems with schedules or problems with environment because it has it’s own. Cron is fine as long as you are lucky. That isn’t to say there never were problems with timers, on debian 9, I think, shipped version of systemd had a bug where systemd-analyze parsed schedule correctly and timer just shit itself. But only for some specific case I can’t remeber which, but it was extremely frustrating to debug.

Nobody does handwritten calculations unless they are training (I think). Kropyva is insanely featureful app, it has every possible artillery piece, maps with very high zoom levels, heightmaps (you can do radio waves calculation as well >_-), and ballistic calculators, a lot of other useful stuff for artillery. UI is very bad and requires multi-hour videos of instructions on how to use it correctly.

I really dislike dumb and entitled takes like this. First he somehow complains about both GNOME and KDE when literally none of the complaint apply to KDE, second switching between different operating systems will break the way you are doing things anyway, and third - who cares.

You can explain timers the same way.

And then with your explanation it goes: cron job doesn’t execute for reason, crontab -l lists not all jobs, someone else put cron job in whatever directory like cron.daily, you’ve added or removed empty line at the end and now nothing works, debian crond and redhat cronie ahave different quirks, etc., etc.

I’ve dealt with insane cron problems for so long that switching to timers was like *whoa i don’t need to suffer?*

Don’t you know that exposing i*rael crimes is antisemitic? Straight to jail.

So it’s really not the same workflow at all? Just this month I’ve explained to really smart people how to use corner tiling in windows and hotkeys, most people today don’t even own a PC. For me, personally, the difference is negligible, for a lot of people it’s really alien.

First, it is usable just not the way Talon requires (and its developer doesn’t want to support wayland). Second people can use LTS distributions that will ship X11 for many years, and by that time it will either be good enough or won’t.

There is wdotool, it’s not complete re-implementation yet, but it works.

Which all of them, which cron implementation is simpler and better? Do you even use cron? It’s not a joke, explanation on how to use cron takes > 8 pages. It should be in the hall of fame of the least accessible and hard to learn programs. Lennart cancer is one of the greatest things that happened to linux.

It’s not so bad like the article author describes, there is work being done to address the input issue e.g. libei and wayland protocols. (also N.Graham answer that says that it should be done on wayland level if they require universal solution is right if a bit unkind)

Like 0 full copies? And internet archive itself archived maybe a percent of everything.

Their historical/cultural loss is probably immesurable. Literary, on the other hand - normal distribution applies and significant amount of those 99% were average or worse.

get acquired

Why in passive? Weren’t they actively participating in acquisition?