Show HN: Fastify DX, a full stack framework based on Fastify and Vite

This required quite some clicking to find out WTF fastify is [0]. Luckily I knew about Vite [1] already.<p>[0]: <a href="https:&#x2F;&#x2F;www.fastify.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.fastify.io&#x2F;</a><p>[1]: <a href="https:&#x2F;&#x2F;vitejs.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;vitejs.dev&#x2F;</a>

As usual, I click the link, I try to read the page content but I have no idea what it&#x27;s saying.<p>Buzzword buzzword, buzzword!<p>Just tell me what is it, and if you don&#x27;t want to, that&#x27;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&#x2F;similar tools?<p>Don&#x27;t tell me &quot;it&#x27;s fast and developr friendly&quot;. 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&#x27;t wait to see run out of steam. I&#x27;ve been around enough years to see a lot of things that we thought were GREAT ideas, turn into &quot;what were we thinking?&quot; I believe we&#x27;ll be doing the same with Tailwind in 3 years. &quot;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???&quot; This viewpoint makes me very unpopular obviously. But it&#x27;s a hill I&#x27;ve chosen to die on. It&#x27;s bad DX and it&#x27;s worse for maintenance. I welcome a lot of downvotes... but let&#x27;s revisit this in 3 years and have a candid conversation about it. I&#x27;ll gladly admit it if I was wrong. But I wasn&#x27;t wrong about AngularJS, Bootstrap and a litany of jQuery plugins. And JS developers fiercely defended each of those at one point as &quot;the one true way&quot;.