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.

Just because you can perform a job from home, doesn’t mean it’s ideal for performance. With

You’re refuting an assertion made by NO one.

No one said all jobs can be done remotely. When the site consolidated equipment or media somewhere, and there’s no way to manipulate stuff remotely then - of course - it’s not a remote capable job.

We’re ignoring that buses are just big drones and surgery has been performed by servos or volunteers at the direction of a specialist far away. But you make a point, as has been made before, that a lever which cannot yet be pulled by a remote action needs an agile meatbag to do so.

The point that has been made - oh god, thousands of times - is that jobs that can be remote, should be. And that egotistical managers needing to feel better by staring at asses in chairs all day and knowing they were forced there through threat of food insecurity, that’s not really a justification.

Amazon’s demanded its devs come back into the office for no value, despite the personality type of those devs, an objective assessment of the workpace they’re forced into - toxic - and the need to live within commute range to get there, limiting housing options for the workers and severely limiting the talent pool for companies. These are people who can, would, will and did the same work better and happier in an environment of their choosing - be it central office or personal office. Now they have no choice but to bend to the will of their boomer-esque managers who forgot it’s not the 1900s anymore.

For remote-capable jobs, the only reason workers need to take risks and spend more money to physically commute is purely and simply egos of bad managers.

That’s it. The dead weight they need to shed was in the office the whole time.

I also understand IT security is dramatically complicated by user’s working on their private network connection or even private client devices.

As otherwise mentioned, it’s actually straightforward.

I work in the daytime on some pretty well-secured stuff; not “secret squirrel” but “people data” stuff. There’s a LOT of forms to sign, and they want to ensure you’re not working on a shared patio but in a real, dedicated office space that is ergonomically optimal and private, with a few other rules, but the effort that started as a panic on COVID day 1 proved workable and they’re going with it. They sold the offices in the dank ugly building. And this org is actually insanely cautious and works with cautious entities, and even they could work it.

At night I work for a different company on different shipped gear… and a KVM switch to go from one set to the other. They’re all segregated and secure, and the night job I’ve had for 22 years with only two invites to fly down to the office for a visit in that time. Barbecues, actually.

I have a lovely view of the river.

It works. You have to be sensible and secure, and then you’re golden.

I think that’s half the appeal.

Some kids can only write on the walls.

And the last three aren’t even an option in the enterprise unless your CTO is 24.

I use it for Ansible, so not for code, and just to reduce the time my brain is exposed to Ansible.

Good old curl|sh

You can see the non stop complaints in the Google Search Support forums about the issue if you scroll down to that time frame. There is also this massive Reddit thread with complaints

But, strangely, not a complaint was heard.

sike

Bone apple tea!

This is a different take on the VMscare broadcom purchase.

The real losers here are SoHos where it is too pricy to migrate and also too pricy not to. I don’t know whether that’s in your 1% or 99% but:

• devs don’t develop for infrastructure their customers don’t use. It’s as dead as LKC, then.
• big customers have deprecated their VMware infra and are only spending on replacement products, and if they do the same for docker the company will suffer in a year.

If docker doesn’t have the gov/mil revenue, are we prepared for the company shedding projects and people as it shrinks?

Remember: when tech elephants fight, it’s we the grass who suffers.

systemctl is trying to do the right thing

I love how this comment suggests every fucking alternative doesn’t or wouldn’t. That’s just bloody arrogance.

Systemd’s entire existence is against best coding practice. Famously, when called out just on the ability to work with others, the systemd team represented trends ably.

Never have I raged at a machine and demanded it tell me what the flying flaming fuck it was actually doing now than when systemd was trying to do what I’m charitably deciding is the right thing.

Why would be doing the right thing now? It honestly only does a thing through luck and race conditions anyway.

will shutdown now

‘shut down’ is two words, here.

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

Oh. Just on my system?

Remember: GNU/Linux

I stopped there. Enough kowtowing to the toejamophage.

1. I run with a preferred name instead of a Rupert J Farnsworth III name (actually it sounds like another name of a criminal; not as bad as my buddy Chuck Manson’s name, but someone says ‘hyuk hyuk’ a few times a year).
2. I don’t have a phone number that will ring and get me. My personal phone is set up as a tablet and has no usable number and can’t receive calls or text messages.

Guess that and the lack of a good app means I can’t sell anything on the play store.

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.

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?