Can you share any info on how you set this up? I also have more faith in Apple's privacy policies than I do in Google / Amazon, so this could be an interesting option. Any idea if it works on an apple watch?
This is freakin EPIC. A hat that captures audio and then decides whether or not to relay it to the physical Alexa / Google / etc speaker. I struggle to believe it'd be super reliable, but the concept is ultra cool!
According to this[1] post, that might not always be the case. I also have this assumption about alexa devices, and I haven't seen any other evidence to say that voice recognition can happen locally. Personally, I find the claim in the thread a bit hard to believe, but...
AFAIK, the thing that sets Gatsby apart is the integration of the built static site and React to do pre-fetching. The output from Gatsby is not just HTML, it's HTML + React javascript, with data loaded from JSON files. That means that once the site has loaded, Gatsby can pre-emptively fetch all the linked pages, both React components and data, to give instantaneous second click page loads. That's a pretty impressive feature in the wild, the second click is neck snappingly fast. I'm not sure if this is an option in other things like nuxtjs or not.
But, you're right that Gatsby requires a lot of code. To get a simple static site setup, it's a lot of work. Plus it changes very fast. We stopped paying attention for a few months, and things broke on the next upgrade.
But, if web performance is the goal, Gatsby is hard to beat. In addition to pre-fetching, it also inlines every resource, images, CSS, the whole thing. So a single HTML fetch should be enough for a full first paint. That's a lot faster than a usual static site, which in turn loads all the additional resources before it can show the site to the user.