This required quite some clicking to find out WTF fastify is [0]. Luckily I knew about Vite [1] already.<p>[0]: <a href="https://www.fastify.io/" rel="nofollow">https://www.fastify.io/</a><p>[1]: <a href="https://vitejs.dev/" rel="nofollow">https://vitejs.dev/</a>
As usual, I click the link, I try to read the page content but I have no idea what it's saying.<p>Buzzword buzzword, buzzword!<p>Just tell me what is it, and if you don't want to, that's your right, but then why are you sharing the link?<p>- What general category of tools is it?<p>- What makes it different from other/similar tools?<p>Don't tell me "it's fast and developr friendly". Tell me what makes it that? What makes it better than the other tools? What do these other tools lack that you are providing?
Very cool! I’m a big fan of Fastify. In fact I’m working on a SQL-over-HTTP bridge right now, published first as a fastify plug-in. And I’m using Vite, so this repository will be nice to study. :)<p>I originally chose Fastify over express ~2 years ago, due to benchmarks and newness, and it’s been running stable in production since then. It’s great software. If you’re coming from express there is a bit of a learning curve. Fastify felt a bit more rigid at first - for example with defining schemas for request body or not logging with console.log - but it was totally worth it.<p>From that perspective, I think this dx framework you’re making here is a great idea! Might I (selfishly) recommend a variant for library authors?
The primitives on which this is built are cool. Fastify and Vite are two projects I love. The moment I see TailwindCSS added as an opinionated default, I nope right out. Tailwind is one hype-train I can't wait to see run out of steam. I've been around enough years to see a lot of things that we thought were GREAT ideas, turn into "what were we thinking?" I believe we'll be doing the same with Tailwind in 3 years. "Why oh why did we think annotating all of our HTML elements with a bunch of class names - some which represent rule-value pairs, was a _good_ idea???" This viewpoint makes me very unpopular obviously. But it's a hill I've chosen to die on. It's bad DX and it's worse for maintenance. I welcome a lot of downvotes... but let's revisit this in 3 years and have a candid conversation about it. I'll gladly admit it if I was wrong. But I wasn't wrong about AngularJS, Bootstrap and a litany of jQuery plugins. And JS developers fiercely defended each of those at one point as "the one true way".