vadersb

That heavily depends on the use case. Game developers that use C# adopt NativeAOT with zero friction, it's just a natural fit

how is OOP dead if tons of code keep being written using OOP these days? From anything corporate in Java/C# to Hyprland C++

It's just futile to to get any kind of sleep working on Windows laptop. An alternative strategy is to just shut it down for long breaks, and keep it working for short breaks ("closing lid does nothing" setting), and that's it. Maybe you will be loosing a few minutes per YEAR waiting for boot, which is nothing compared to hours trying to get sleep working.

It’s OLED in general, because of PWM flickering first of all. I strongly prefer IPS LCD for any screen that’s used for longer than brief periods of time. Btw Apple IPS screens in iPads, MacBooks, etc demonstrate that that tech is capable of producing great image quality

Yeah, going with prev gen iPad Pro would definitely be a valid choice. I was talking about the general state of Apple hardware and software, not only iPad. The fact that base iPhone 15 model has 60hz screen (while obviously having more than enough power to drive 120hz display) is frustrating. Personally I perceive it as a hostile stance towards anyone who considers themselves a tech enthusiast. There are many more examples of that. Like pop up warning about 10% battery left forcibly stops current audio message recording. Inexcusable.

I was a long-time iPad fan for more than a decade, currently using 5 year old iPad Pro 10.5 which works flawlessly but its battery is quite degraded already.

With these new iPads introduced I no longer have a viable upgrade path: iPad pro is a no-go for me because of OLED screen (which I strongly oppose, PWM, irregular subpixels, etc.) and newly introduced iPad Air doesn't have 120Hz display (or ProMotion in Apple terms). So, there are no new iPads with LCD display and ProMotion.

What a sad state both Apple hardware and Apple software are in.

Very nice tutorial on the subject! Probably it's a noob question, but - with such CMake setup, will it be possible to step into dependencies' source code when debugging?