https://t.me/sad_pup_kit_kid_thing/10774
it's a knife

avery have you gone insane

https://t.me/talconsnudebeach/169
not everyone is an idiot who lashes out at people for not knowing things

You might wanna avoid interacting with people like that

Upsetting

https://t.me/Dproductions/2269
Asking the right questions

So since I know none of you are going to actually play the thing, here's what the entire first level looks like now: https://hyper.is-a.cat/smwhack2.mp4

Interesting read.
I've noticed this as well; things that are old, obsolete and horribly coded are not removed solely for compatibility reasons. They can't fix them, either, because that would break 3rd party applications that rely on this erratic behavior. So they simply pile up features upon features that work well only for a while. Then they inevitably have to extend or fix them and then it turns out that it is impossible.

And then there's the filesystem. Holy heck, bless the people who still understand what is going on in that mess.

The result is that most problems are fixed by a reinstall, rollback, or whatever like that. No one understands where the issues come from because no one cares.

https://t.me/ramblings/207
From the article: "That's literally the explanation for PowerShell. Many of us wanted to improve cmd.exe, but couldn't."

https://t.me/loudbarking/4962
aww

https://t.me/cockypony/2906
_rubber duck squeeze sound_

I always suspected that moving processes between cores as windows does it is kind of inefficient; if you look at the CPU usage graph on windows, you can see that it's kinda messy and over the place even when there's one thread at 100%. Linux would move this thread around processes much slower, making the graph reflect reality a bit more.

https://www.reddit.com/r/linuxmasterrace/comments/60e2u8/the_inferiority_of_windows_cpu_scheduler_vs/df5wcsz/
Here's a pretty brilliant analogy if you don't quite understand what I'm talking about