WtAF?!? So many questions, starting with WtF makes this "feminine?"

It definitely didn't come off as particularly masculine.

As much as that doesn't sound very efficient, I admit having a single core would prevent so many multithreading related bugs or crashes. Sounds nice.

A single core can still run multiple threads ...

As soon as I saw no networking, I knew TempleOS was coming

Why would it? Everything still processes one at a time anyways...

The act itself is not feminine but when felt by a sufficiently feminine person the urge to do so, is.

So multiple things can effectively run at once. Otherwise, every piece of software has to be fully aware of every other piece's timing and resource requirements, which obviously can spiral out of control very quickly, and effectively locks out any possibility of an unplanned-for application running on the system.

I feel like even without multithreading the services share processing power effectively. There might be some jitters and hangs, but doing things within specification won't produce any noticeable lag.

It's kind of like the difference of if one process ran for 3ms or if it ran for 0.3ms 10 times.

But we're getting off topic, now, yes multithreading is apparently (a very stupid) thing on single cores and therefor the bugs and crashes can still occur.

Gender ALL THE THINGS!

Well, I guess it's a good thing you're not a software engineer.

Developers aren't engineers as far as I'm concerned.