That's still the default state of Google Hardware. Just look at their out-of-warranty Pixel Watch repairs.
And if you're not in North America (or EU), chances are very high that any repair to Pixels is going to be either not possible or will cost you dearly. I personally had a terrible experience of this with Pixel 7 Pro that was in warranty and had a water-related damage, since then, I've stayed away from any device made by Google.
The thriving ecosystem of dynamic libraries that you could just link and create a Windows Vista-esque UI (AKA Aero) in an IDE built in 1998, thanks to Win32 API.
I wish Google would launch Mac Mini-like devices running their consumer-grade TPUs for local inference. I get that they don't want it to eat into their GCP margins, but it would still get them into consumer desktops that Pixel Books could never penetrate (Chromebooks don't count and may likely become obsolete soon due to MacBook Neo).
This looks interesting and I might give it a try. I did look at FSEvents in the past but due to my needs in macOS app, I took a very niche (and not so fast) approach of running find | ls -lT | shasum spawned in a separate process to reliably tell if a folder has changed.
Been working on Petrichor - native macOS music player [1]
This has been my side project for nearly a year, and I also shared it here in HN when it was in alpha [2] and received a ton of feedback (and stars on GitHub).
The project has evolved quite a bit since then, like having additional file format support, lyrics, Last.fm scrobbling, and more!
And if you're not in North America (or EU), chances are very high that any repair to Pixels is going to be either not possible or will cost you dearly. I personally had a terrible experience of this with Pixel 7 Pro that was in warranty and had a water-related damage, since then, I've stayed away from any device made by Google.