I agree that the name is not worth the confusion.

My first thought on seeing the name was, "Someone is still working on mkLinux?" I think it would be possible to run multiple kernels on the Mach microkernel, but kernel development was never my thing.

> But on the flip side, nobody would still remember how to compile code for it, so maybe not

Oh, I think I might remember or could figure it out rather quickly. I remember developing for KDE on a Performa 6100(?) back in the day and the compile of the entire KDE suite taking 3 days or so. I still have the machine with an out of spec 72MB of RAM sitting in my attic. I haven't touched it in 2 decades, so it's probably dead or needs batteries at least. mkLinux is still on the hard drive since I never wiped it.

Cheers to you, dgatwood, and to nester for your fine work.

The same way that you implement a language that does look like Common Lisp: macros, specifically reader macros.

This is the definition of fascism according to Mussolini:

“Fascism should more appropriately be called Corporatism because it is a merger of state and corporate power."

"Le landsknecht frappe à minuit."

TBH, I mostly only use threads with C++, so I should have reflected that in my previous comment. Thank you for sharing your response, I did know that about threads in Python.

I've mostly only used threads in toy/practice programs in Python. I use the subprocess module a lot.

I suppose I should reread my posts more carefully before hitting submit.

The project I work on uses many non-MT safe modules. Encode being the main one. You simply cannot use threads in Perl with non-MT safe modules.

In C++ or Python, if you have non-MT safe code, you can implement a MT safe wrapper with locks or atomics.

I honestly used to think: "I don't need Python. I have Perl." I started messing around with Python a few years ago, and I found it to be usable despite the white space issues. I use it mostly for small utilities that I might have otherwise written in Perl.

I still probably write more Perl than any other language. I'm paid to work on a large F/OSS project that is mostly written in Perl. Sometimes, I curse the Perl layer because too many people have introduced too many different idioms into the code over the years. There are some things that the architecture of Perl 5 makes very hard to do that are dead easy in Python, threads for instance.

Yeahp. Say is basically pointless. Just type "$\ = '\n';" and you get a newline after every print.

I used to really like Perl, but the more I've used it for complicated things, the less I like it. I've been using other languages, particularly Python and C++, for things that I used to do in Perl.

I doubt that you actually watch Fox News. I'm subjected to it on a routine basis because of family members living in the same house.

Tucker Carlson is NOT all of Fox News. He's the lone loony voice. He's also the most popular because he says what he "thinks" off the cuff.

How 'bout you pay some attention to the vast number of other Fox News hosts. They pretty much always say the following when it comes to vaccines in this order:

1. We're vaccinated.
2. It's an individual's choice if they get vaccinated or not.
3. We recommend you get vaccinated if you can.
4. Consult your physician.

You are wrong about Fox News. Everyone at Fox News is vaccinated. If a Fox News employee refused to get vaccinated, they were fired or asked to resign. The management made it a requirement. NB: I'm only talking about the national Fox News. I don't know about any of the affiliate stations.

Also, every time they discuss the vaccines, they say it is up to individuals to make the choice for themselves, but they always point out that they are vaccinated and they recommend that everyone get vaccinated who does not have a medical reason not to do so.

You should watch the opposition to see what they actually sometimes rather than just relying on what other people say they say.

> tech companies are especially hard

Wiring harnesses from some entity in China I only have email contact with. Steel sheet metal fab across the country that likely needs months to get my order in. Surprise tariffs on my embedded boards due to Trump's trade war on China. Failures on some of these boards that leave the HDMI displaying, but frozen, and even a serial connection stops responding, so I have no way to diagnose it and suddenly a bunch of support incidents where the box needs to be shipped back.

The tech piece of this is by far the easiest bit of the operation. I guess what I'm asking is, "hard, compared to what?"

You know that all of the safety and efficacy data comes directly from the drug manufacturer, right? You know that Pfizer was fined $4.3 billion US dollars for lying about the safety and efficacy of their drugs for decades? You know that there was no management shake up, no one fired, no changes made at Pfizer after the fine was levied?

They lied before. I assume that they are still lying. Which is the biggest reason that I have not and will never get the shot. It's a scam, like just about everything else in the USA.

Big surprise.