If people are uncomfortable, they can predict how often they can turn the table over and get another party in there.

If I'm uncomfortable, I can predict how seldom I will be coming back.

I picked three North American trees arbitrarily, and they were all cut down, one by vandals, one by a protester who sounds a bit crazy, and one by a researcher.

I think we've been trained to accept bad software at this point, and a lot of people don't know anything different.

I suspect that a lot of it is caused by shoving Android onto underpowered devices because it is cheap and seems like an easy button. But I don't know for sure, that's just an impression. I have no numbers.

Could there be an opportunity here, for a specialized kiosk OS or something like that?

It's become a defacto forum for a lot of local niche stuff like clubs, schools, non profits, and other special interest groups.

In my area there are groups related to a lot of different outdoor activities , and they share information, trip reports, etc. There might be some other forums for that, but they aren't as widely used or frequently updated.

People have died during fires on the tarmac while trying to evacuate. Every second saved could mean another person lives.

My favorite fiction book I read this year is Berlin, a graphic novel by Jason Lutes.

"Is it time to rewrite sudo in Zig?"

This is rage bait! :-)

This triggers a vague memory of trying to figure out why my assembler (masm?) was outputting a LEA instead of a MOV. I can't remember why. Maybe LEA was more efficient, or MOV didn't really support the addressing mode and the assembler just quietly fixed it for you.

In any case, I felt slightly betrayed by the assembler for silently outputting something I didn't tell it to.

I assumed they're referring to register-register moves?

OK, so:

LEA eax, [ebx]

instead of:

MOV eax, ebx

But of course:

MOV eax, [ebx]

is not the same.

Nice work!

I do want to say, I don't like having to rely on scraping ss output. But that's not a comment on this project - I have done the exact same thing. It just proved to be the most expedient way given the constraints I was under. I suspect there is a lot of devops and CI/CD code out there that relies on the output format of ss. My concern is that parsing text intended for human readability and not machine processing is brittle and prone to failure due to unforeseen circumstances, or a package upgrade that changes the behavior.

it sounds like you want https://github.com/evilsocket/opensnitch

I was going to say the same thing.

I really like the eBPF approach as pointed out to by the other comments. I feel like this is the ideal approach, please correct me if I'm wrong.

A callback based approach as opposed to (constantly) polling the output of some command is ideal.

This was my experience, too. A Skeleton Key To Finnegan's Wake by Joseph Campbell helped me understand the overall themes of the book, and hearing Joyce read it helped me appreciate the language and the rhythm of the words. I found it more approachable once I saw it as a story told in wild poetic dream sequence imagery.