You can run systemd (or cron) inside a pod for scheduling and call the kubernetes API from there to run jobs and stuff. Not sure if this helps you, but it can be easy to overlook.

May I suggest you spend more effort understanding the situation, and less coming up with wild speculations?

I’m sorry but that is absolutely not “the whole point of open source”.

The point of open source is the ability to read, modify, keep and share the source code of the software you use.

It’s a good thing that no one is beholden to anyone then. Which is the entire point of free software.

2024 is the year of Red Star Linux on the desktop

You might be surprised to learn that Sweden also has sanctions against Russia, together with the rest of the EU, Norway, Switzerland, Japan, Australia, South Korea and a bunch of other countries. Because this is not about the US being an ass, it’s about Russia being an ass.

The massive negative outcry over this fairly uninteresting change certainly seems oddly overblown, almost as if there are parties trying to turn it into a big political issue to paint Russia as a victim. But idk, nerds freak out over stuff all the time completely on their own.

Giving them the benefit of the doubt, I think the Linux Foundation has a hard time being clear on the matter because it just isn’t clear. These are new laws and a global open source cooperation run by a non-profit is likely a corner case that the lawmakers did not think about at all when making them.

Yes, the sanctions against Russia, as mentioned by Linus. The change also said the maintainers “can come back in the future if sufficient documentation is provided”.

My guess is that the Linux Foundation must ensure that none of the people they work with are in any way associated with any organisation, person or activity on the sanctions list. And that they preemptively removed all maintainers that might risk violating the sanctions while they work with them to establish whether they might be covered by the sanctions or not.

Regardless of what you or they think of the sanctions, they are the law, and I don’t think anyone wants the Linux Foundation to have to spend their money on lawyers and fines because they had a maintainer who also worked on a research project funded by a sanctioned entity. (If that is how it works, IANAL)

I use macros to solve most of the same problems. You just on-the-fly record a sequence of regular vim commands that you can then replay as many times as you need. Great for formatting a bunch of data without having to deal with the misery of regex

Really? Not that I’d notice, but I assumed ed was so tiny that there wouldn’t be any reason to not include it. (Ubuntu has it and it’s 59KB)

Asking for vi and getting vim is just a pleasant surprise :)

Just type :!bash (or whatever heathenous shell you prefer) and you never have to leave the warm embrace of vim ever again

For just regular text to be consumed by humans, it’s not that great, you probably want a word processor.

It shines when you do a lot of more structural editing, stuff like “change all quotation marks on this line to be single tick”, “copy everything inside these parentheses and paste it after the equals sign”, “make the first word on the next five lines uppercase”, these are the type of things vim make easy that are not easy in other editors.

So it’s great for code and config files. Markdown is borderline. You can have a setup that lets you live view how the markdown renders while editing in vim, so it can be pretty good, but the advantage might be a bit dubious.

It does have a vim plugin, so it’s a perfectly fine editor

tl;dr: Run vimtutor, learn vim, enjoy life

It’s extremely powerful, for mostly the same reason that it’s incomprehensible to newbies. It’s focused not on directly inputting characters from your keyboard, but on issuing commands to the editor on how to modify the text.

These commands are simple but combine to let you do exactly what you want with just a few keypresses.

For example:

w is a movement command that moves one word forward.

You can put a number in front of any command to repeat it that many times, so 3w moves three words forward.

d is the delete command. You combine it with a movement command that tells it what to delete. So dw deletes one word and d3w deletes the next three words.

f is the find movement command. You press it and then a character to move to the first instance of that character. So f. will move to the end of the current sentence, where the period is.

Now, knowing only this, if you wanted to delete the next two sentences, you could do that by pressing d2f.

Hopefully I gave a taste of how incredibly powerful, flexible, yet simple this system is. You only need to know a handful of commands to use vim more effectively than you ever could most other editors. And there are enough clever features that any time you think “I wish there was a better way to do this” there most certainly is (as well as a nice description of how).

It also comes with a guide to help you get over the initial learning curve, run vimtutor in a console near you to get started on the path to salvation efficient editing.

Unless you wanted to learn to use ed (which you don’t)

vi is part of the POSIX standard, so it’ll be available in some form on almost anything UNIX-flavoured