It’s essentially just a bunch of pre-made css classes that do a specific thing that you mix and match from.

AFAIK the programmatic part is so your served CSS file will only include the classes you actually use, rather than all available ones. You could always just not do that.

It always seemed to me like one of the least overengineered front end tools.

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.

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

Yeah the tech labor market has really proven that the idea of employment contracts being negotiated between equal parties isn’t true even in the best of circumstances.

Even when companies are desperate for talent, and willing to spend ridiculous amounts of money on salaries and perks, they are not willing to negotiate on anything outside of that. They still have terrifying contracts with non-compete and damages clauses they could use to wreck your life, no workplace democracy, unpaid overtime and whatever other shit is legal.

But hey! You get free snacks and enough money to buy the dinners you don’t time to cook and save up to survive your inevitable burn out!

Unless unions work differently where you live, they are a democracy that will pursue whatever issues its members vote on. If members don’t think pay is a problem, why would they try to change it?

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

No they call it Sequel Server