5 ms·

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

47 points by jgalvez 4y ago

Semaphor 4y ago
This required quite some clicking to find out WTF fastify is [0]. Luckily I knew about Vite [1] already. [0]: https://www.fastify.io/ https://www.fastify.io/ [1]: https://vitejs.dev/ https://vitejs.dev/
chatmasta 4y ago
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. :) 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. 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?
- jgalvez 4y ago
  Thank you! There's a low-level library it builds upon: https://github.com/fastify/fastify-vite https://github.com/fastify/fastify-vite
hsn915 4y ago
As usual, I click the link, I try to read the page content but I have no idea what it's saying. Buzzword buzzword, buzzword! 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? - What general category of tools is it? - What makes it different from other/similar tools? 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?
- brailsafe 4y ago
  Ya, sometimes I think people with this opinion didn't read the home page, but this is beyond me. Seems like a junior programmer's side project or something based on one of the deeply nested descriptions. I guess at some point they were a contributor on another esoteric stack layer and decided it was too much, so they announced rebuilding it on an even more alpha and esoteric bit
- string 4y ago
  I can only assume you're not a web developer? Because just the title of the post makes it clear to pretty much any web dev what this is. The package introduction sections accessible in one click are also very clear and concise.
  - pdimitar 4y ago
    I'm a web developer for most of my 20 years of career and that page tells me absolutely nothing except that the software is apparently a full-stack framework, which operationally and concretely can mean hundreds of things. I don't think you understood the criticism of the parent poster. I too got exactly nothing concrete from that cryptic generic README.
  - yuppiepuppie 4y ago
    You shouldnt have to be a <whatever> to understand a tool and what it does. I think Richard Feynman had a technique around this.
  - hsn915 4y ago
    No, I'm a web developer (unfortunately?). Maybe you don't realize there's a hundred ways to develop websites and just because you know a certain stack does not mean everyone else knows it (or cares about it).
    - string 4y ago
      I too don't use half the things mentioned in the project's documentation but I know what they all are, the ecosystem isn't that big. I'd be really interested to hear what stack you use to develop websites.
nobleach 4y ago
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".
- deleted 4y ago
  [deleted]
- jgalvez 4y ago
  Tailwind is not part of Fastify DX. It's just part of the starter template, through unocss. unocss goes beyond what Tailwind does. it's general CSS processing engine and provides quick access to some rather essential goodies, like an icon set. I think it's a worthy addition to the starter template, but easy to remove. Literally remove one import and a vite.config.js plugin entry.
- mgrandl 4y ago
  I have been a frontend dev for 10+ years and tailwind is absolutely amazing DX for me personally, but to each their own.
  - nobleach 4y ago
    Hey yeah, that's entirely your call. If you and your team agree on it, I'm very happy to hear it increases your quality of life. Where I start to drift is when I see it included on any project because "everyone's using it" I do not ever want to use it. I tried to see what all the fuss was about. I read the book and. No thank you. I promise I'll add it to projects on my own if I come across new info. Remix takes the right approach. They recommend it in their docs... but stop short of making it a product dependency. (If it's included in one of their stacks, I'm not sure)

47 points by jgalvez 4y ago

This required quite some clicking to find out WTF fastify is [0]. Luckily I knew about Vite [1] already. [0]: https://www.fastify.io/ https://www.fastify.io/ [1]: https://vitejs.dev/ https://vitejs.dev/

chatmasta 4y ago

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. :) 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. 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?

jgalvez 4y ago
Thank you! There's a low-level library it builds upon: https://github.com/fastify/fastify-vite https://github.com/fastify/fastify-vite

hsn915 4y ago

As usual, I click the link, I try to read the page content but I have no idea what it's saying. Buzzword buzzword, buzzword! 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? - What general category of tools is it? - What makes it different from other/similar tools? 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?

brailsafe 4y ago
Ya, sometimes I think people with this opinion didn't read the home page, but this is beyond me. Seems like a junior programmer's side project or something based on one of the deeply nested descriptions. I guess at some point they were a contributor on another esoteric stack layer and decided it was too much, so they announced rebuilding it on an even more alpha and esoteric bit
string 4y ago
I can only assume you're not a web developer? Because just the title of the post makes it clear to pretty much any web dev what this is. The package introduction sections accessible in one click are also very clear and concise.
- pdimitar 4y ago
  I'm a web developer for most of my 20 years of career and that page tells me absolutely nothing except that the software is apparently a full-stack framework, which operationally and concretely can mean hundreds of things. I don't think you understood the criticism of the parent poster. I too got exactly nothing concrete from that cryptic generic README.
- yuppiepuppie 4y ago
  You shouldnt have to be a <whatever> to understand a tool and what it does. I think Richard Feynman had a technique around this.
- hsn915 4y ago
  No, I'm a web developer (unfortunately?). Maybe you don't realize there's a hundred ways to develop websites and just because you know a certain stack does not mean everyone else knows it (or cares about it).
  - string 4y ago
    I too don't use half the things mentioned in the project's documentation but I know what they all are, the ecosystem isn't that big. I'd be really interested to hear what stack you use to develop websites.

nobleach 4y ago

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".

deleted 4y ago
[deleted]
jgalvez 4y ago
Tailwind is not part of Fastify DX. It's just part of the starter template, through unocss. unocss goes beyond what Tailwind does. it's general CSS processing engine and provides quick access to some rather essential goodies, like an icon set. I think it's a worthy addition to the starter template, but easy to remove. Literally remove one import and a vite.config.js plugin entry.
mgrandl 4y ago
I have been a frontend dev for 10+ years and tailwind is absolutely amazing DX for me personally, but to each their own.
- nobleach 4y ago
  Hey yeah, that's entirely your call. If you and your team agree on it, I'm very happy to hear it increases your quality of life. Where I start to drift is when I see it included on any project because "everyone's using it" I do not ever want to use it. I tried to see what all the fuss was about. I read the book and. No thank you. I promise I'll add it to projects on my own if I come across new info. Remix takes the right approach. They recommend it in their docs... but stop short of making it a product dependency. (If it's included in one of their stacks, I'm not sure)