timanderson

Great video, thanks for the link.

The PaaS section seems odd to me too. AWS 63% followed by Vercel 7.9%. But Vercel runs on AWS I believe. Azure just 4.6% and no showing for GCP at all.

Seems odd that C# does not figure in the top 10 programming languages, yet ASP.Net is the 4th most popular web framework with 10% share?

The React docs point devs toward Next.js if you want to use RSC but here is a simpler option.

What does "tied" mean in this headline? One presumes correlation rather than causation. https://xkcd.com/552

I create workouts in Garmin Connect

Opposite experience here. Went from Apple Watch to Garmin, couldn't be happier. Never had an issue with the charging point chafing, it is recessed and no problem. Buttons to start/stop/pause/resume activity work as expected, so much better than trying to swipe and tap the Apple Watch screen especially in wet conditions. GPS sync never been an issue for me, you can start an activity before it syncs and it figures it out.

A Garmin watch is absolutely designed for wearing all the time, even when sleeping. You might prefer not to for reasons of appearance or because there are features of some other smart watch that you like, but Garmin is fine for what I use it for and does notifications etc. The battery life was a game changer for me (as an Apple Watch switcher) since it's now something I just don't worry about whereas with Apple Watch it was a daily thing and it let me down on several runs too.

https://www.puppet.com/blog/open-source-puppet-updates-2025

It's meant to be an indicator of fitness but agreed it doesn't make any practical difference to how you train

Experience of those race predictions varies! Mine are over-optimistic but not by that much, a friend is the other way round and Garmin continued to predict a slower time even when he actually recorded races in faster times.

I have an Apple Watch 7 and a Garmin Forerunner 265. The Garmin gives me a much higher VO2Max. I have no idea which is right but one factor seems to be the max heart rate, which the Garmin calculates but in Apple Watch seems to be fixed based on age unless you set it manually. Reluctant to set it manually as it will change over time and would neeed re-calculating so the Garmin approach seems better to me.

Atmos is a good thing IMO. Not so much for the technology itself though it seems OK, but rather for the fact that we are getting surround remixes of many albums which is a new way to hear them and a lot of fun; also less prone to "loudness wars" excessive compression in my experience.

Surround is better than stereo but much harder to set up right; I totally get that, but that doesn't make it bad. I have an absolutely compromised surround setup in my study with a soundbar that supports Atmos, sub and rear speakers, and I love it, even if yes, the bouncing sound off the ceiling thing doesn't seem to do much.

On headphones or earbuds it's some and some, really depends if you like the remix.

Agreed that Windows has become rather unpleasant but this:

"So, there is basically little you can do with Windows out of the box but buy subscriptions and log into pre-installed social media apps."

is not true at all. Well, I suppose if you don't install anything. But what you are going to do with Windows "out of the box" is not to buy subscriptions, but to install stuff. LibreOffice, VSCode, Audacity, Paint.Net, VLC, etc. There is so much fantastic productivity software for free. In the end it's just an OS with its share of annoyances. The big advantage of Mac for me is not the OS but Apple Silicon.

I was in a similar position. I use ASP.NET Core, works well, fine on Linux. I don't use Node but I do use TypeScript and getting that working smoothly with ASP.NET Core took some experimentation, I went down the webpack rabbithole but abandoned it as I don't have an SPA. I use Dapper in preference to Entity Framework.

Not tried it, sorry

I have a C# project which I can work with in either VS 2022 or VS Code. I find myself almost always using VS Code. I mean to blog about why, but performance is better and it is nicer for the non-C# parts like TypeScript.

These look like implementation defects to me. I do not know if the problem is in Word 2010, or Word 2007, or both. It is specific to Open XML since if you use the .doc format the problem goes away. It is embarrassing since Open XML is meant to the new and better format, and this is a good reason not to use it.