MicroEmacs

In testing, to settle a bet by a rabid cult-of-vi peer, I opened a given set of files in each editor, each a day apart because I couldn’t be arsed to clear caches. This guy, otherwise a prince, was railing about emacs, but otherwise suffered days of waiting.

10/10 the memory usage by his precious vi was same-or-more than emacs.

There’s so many shared libs pulled in by the shell that all the fuddy doomsaying about bloat is now just noise.

I avoid vi because even in 1992 it was crusty and wrong-headed. 30 years on the hard-headed cult and the app haven’t changed.

I don’t see how microEmacs can improve on what we have by default, and I worry that the more niche the product is the harder it will be to find answers online. But I’m willing to be swayed if anyone can pitch its virtues.

vi versus emacs

You write “vi versus the world” funny.

The existing maintainers won’t live forever, having Rust in the Kernel is a bet on the future.

You’re drastically reducing your talent base by requiring membership in two groups of experts. Well done.

The comma splice gives it away, but you’re new at organizing groups and practicing set theory, aren’t you?

yum history undo last

There’s a colossal amount of work that goes into making that command usable and reliable, and I’m glad to say the yum-adjacent distros are still putting in the effort. That may change, but so far it’s been there to save my bacon when I need it.

deleted by creator

a […] infrastructure

The uncountable becomes countable.

Ever? That’s a lot.

That’s a terrible sword to live by. How do you expect to get blood, then? If you’re unconscious you can’t take it by force.

ZFS. It’s come so far, and it has so far to go. but it’s a good concept for sure.

Firefly.

Breathe, son.

Nah, not ALL the pedestrians. That’s not how natural selection works.

Source: am pedestrian, have lived.

Remind them that the use the same beds for people injured when they have the right of way as when they don’t, and that while their feet are on black stuff they are in danger.

Gen-x was a long time ago, so it’s been a long time since parents - and teachers; remember? - taught kids about not jumping out into traffic. In the latter case, they had traumatic injury clips!

Oh, that’s a great suggestion.

Please tell me someone didn’t buy software with ‘atleast’ spelled like that in there. Please, tell me someone tested the web app and had the brains God gave a douglas fir and knew that wasn’t a word; that it was never a word; that the writer’s spell check should have picked that up; that it’s not been over-ruled by stupid so much that it just takes it.

We all know it sucks. I have no idea why people use it instead of anything else. My workday is jammed with fucking ansible which, while also being so ghetto that we were easily doing more with less in 2002, uses So.much.fucking.yaml . Just when you think ansible couldn’t get more clunky and useless and slow, it also is configured in yaml.

When you run git-bash from an install of the git suite, that’s a valid pathname.

Oh. Just on my system?

My old employer used to have people on staff just for technical writing. Some of that writing became the man pages you know, and some of it was ‘just’ documentation for commercial products - ID management and the like.

Then we sued IBM for breach of contract, and if you ask anyone about it they’ll parrot the IBM PR themes exactly, as their PR work was brutal. People in Usenet and Forums were very mean, and the company decided to stop offering much of the stuff that it was for free. It was very ‘f this’.

If man pages needed a volunteer to maintain, I know why ours tapered off.

assume that productivity is a feature of an individual and not a feature of a team. That’s a wrong assumption. The fairest way to pay is same salary for the whole team.

So much of what we do produces nothing, but prevents a lot. There is definitely a reason to pay for experience and seniority: it’s not so much about creating widgets faster but more about not making short-sighted decisions. And in dev work, we have a high chance of making bad decisions as we’re second-generation lost-boys.

Having said that, those individuals are out there for whom compensation starts competitive and ends just short of their value. It’s eye-opening to meet and talk with these people and, once you do, it will change your life having them in it.

If I need systemd for a specific use, like testing systemd services

So you’re hoping to test systemd in this theoretical test environment, but your prod isn’t built like this? Tell us why you’re ignoring the first rule of testing and deploying internal software?