I had an experience similar to their Lambda one not that long ago. Needed somewhere to host a static Hugo site, went with Netlify, who marketed some vaguely specified special support and functionality for Hugo, and "sync-to-git-repo" functionality. Ended up spending several hours digging through their docs and scattered code until it became clear to me that the hugo-stuff was just out-of-date and poorly stitched toge…
I like to play with microcontrollers. Nearly everyone uses the terms IoT (internet of things), despite the fact that the vast majority of microcontrollers don't have internet connectivity out of the box. AI is picking up some buzz at the moment, and I even saw the term AIoT being used. Gotta get those buzzwords in.
What I find astonishing is that these are all things directed at technically-competent programmers who are supposed to appraise things objectively rather than being given a lot of marketing guff. Could you ever imagine trying to sell a product to a chemist, engineer or physicist in this way?
I do have one app that's connected to the internet, but that uses a Raspberry Pi. I have had other projects that used Wifi. I've come to the conclusion that it is way better to avoid anything internet if at all possible. It makes devices much more unreliable.
And that's what grinds my gears.