Everyone's a pro ninja 10x whatever until you ask them to create multi-core optimized code

My last job our code base scaled linearly to 48+ physical cores... I doubled its throughput. Beg to differ!!!

@atheist your a real 48x engineer

Laughs in haskell

@atheist a 10x unicorn ninja rockstar from space worthy of the name

this is actually a huge problem. At my school there was only one class that taught multi threaded programming, and it was NOT mandatory. So i can definitely see why this is the case a lot of the time. it's unfortunate.

Python developers can cry in corner

It becomes even more fun when you throw in thread priorities. I mean real time priorities, not the Linux style.

Laughs in .Net Parallel Class :

https://docs.microsoft.com/en-us/...

Well, at school I was the king of performance & multithreaded C (perfect 100% cpu utilisation on 20 cores 🤤)

My real magic trick was to not use any kind of mutex (or atomics) 😆

I only started using them because Rust forces me to 😆

@oraro or you know, an sde at Amazon, close enough? My point was more some of us have actually had to do that kind of high performance multi-threading.

@NoToJavaScript
Laughs in custom logic.

@MagicSowap
Teach me master.

@Gregozor2121 I guess there are cases where you need to do it manually. But I would argue 80% of the time it is better to use something what already exists

@chowdercake 😭😭😭

HA
fork()
HA HA
fork()
HA HA HA HA

With Go there are quite some constructs that help with that. Not mucking with treads but just focus on parallelization and either using mutexes or channels to do it safely. No more idle core.