Deleted Comment
For me, the reason for a hackintosh is just that I am tired of all the cables and having to swap between the two setups (like having one monitor for working, and one for gaming) while utilizing the performance when working.
I also want to utilize my iCloud Drive symlinking hacks to sync files / dotfiles between systems.
My gaming rig is currently running i4790k with a fairly decent motherboard (Asus Maximus VII) that I bought used for $200 a two years ago. It still performs like butter as long as you have a decent gpu connected to it. I seriously recommend this setup if you want to save some dough (or maybe the new Ryzen CPUs are better now tbh).
A sidenote regarding monitors: These are some exciting times to be working from home combined with having an interest for gaming due to the new monitors coming out, working for both.
I am currently thinking about the LG 38WN95C-W. Really expensive, but if you use it 8 hours a day for 5 years, I think I calculated it to be like 50 cent a day. :)
edit: Oh, and yes, as someone below mentioned, I love macOS and a lot of the things I work on require me to work on it.
What do you on macOS that isn't available on Windows? Really curious.
The compatibility break with the .NET Framework also removed the biggest advantage I saw in C#, which was that any code that I wrote would "just work". Now there's more frameworks, standards, cores, and build flags than I care to learn, and there are all too many scenarios where it's flat impossible to do something that was trivial before.
This is the reason, for example, that PowerShell Core is past version 7 but is still missing many modules, including some key Microsoft ones. If they can't figure this out, what chance do I have? Why would I bother?
Lastly, I got fed up with Microsoft releasing yet another half-baked GUI framework. What's the latest one? MAUI? It's yet another attempt at having one framework to rule them all, which means that it'll inevitably be the lowest common denominator and not good at anything. Microsoft won't actually bother making it good enough to write a flagship application in it, and they won't write any of their own apps with it. It'll be dropped on the floor and replaced by the next incomplete GUI framework within just a few years, mark my words. That's if it's ever finished!
The actual issue is this new Microsoft full of half-done projects and trying to reduce engineering costs. They even try to make others write the documentation for their products... MSDN is gone and now docs are a mess.
Ballmer was a mess, but at least he got the devs-first bit right. Nowadays it is devs-last, cloud-first.
Edit: interesting, someone wrote about this a couple years ago: https://xoofx.com/blog/2018/04/06/porting-unity-to-coreclr
I wonder if there’s movement on this internally at Unity.
When run all it does is return "Hello World!" in plain text - it doesn't even use HTML.
For example, you can see gcc's progression of efficiency for c atomics with https://godbolt.org/z/brsoEr. If you increment the gcc version number, you will see the (very slow) mfence disappear, and xchg show up.
Then there is Clang at O3: If an int falls in the forest, and there is no one around, was it ever incremented? No. The function turns into a bare ret.
For a random example from a few days ago, I wanted to understand how Rust compiles various approaches to doing pairwise addition between a f64 vector and a f32 vector: https://godbolt.org/z/9envsT. Profiling can tell me which is fastest, but godbolt is really helpful for understanding why.
(Fun fact I learned recently, after years of using it: Godbolt is named after its creator, Matt Godbolt [0]).
The thing is that he originally served it from its domain so people use both interchangeably.
I now built the exe and ran:
real 0m0.199s
user 0m0.000s
sys 0m0.014s
So 0.2s for 10k files on the worst possible hardware/software scenario I could find nearby. Edited my original comment. Thanks!It is still a ton of time, about an order of magnitude more than optimal if the real/sys time split is to be believed.