Makes sense to substitute Express for Fastify?

[rustworthy]

Hi there!

This is an awesome stack and a lot of efforts and time invested for the community benefit.

I'd like to suggest something. How about switching onto fastify, which is a new generation framework and
could fit the epic stack nature ideally. Here is short summary from Nest.js documentation on the underlying framework, which is of interest I believe.

There's a community maintained remix-fastify adapter and one missing piece - the wrapper over the wrapper 😅 in Sentry - I hope will be covered soon. As for the middleware used in the epic stack's Express server app - a quick walk-through shows they are all available in Fastify ecosystem.

It goes without saying, there should be a proof of concept first, which I'd love to implement and tag accordingly 😄

What's your opinion on this change suggestion in general?

[fredericrous]

my humble opinion, epic stack should wait for fastify to become a remix official adapter. switching to a community driven adapter doesn't seem wise for a broad usage for the number 1 template for remix. But that shouldn't stop you from forking the template and creating a PR to add it to https://github.com/epicweb-dev/epic-stack/blob/main/docs/examples.md

[kiliman]

My understanding is that the Remix team is not interested in creating more official adapters. They want to offload that responsibility to the platform owners or community.

[kentcdodds]

An example would definitely be welcome.

I'm not very interested in changing the built-in server until Remix finishes the work they're doing on solving "the middleware problem." Because when they do then we'll ditch the built-in server in favor of using Remix for everything anyway.

Express is good enough to get us to that point.

Here's an old discussion about this. Feel free to move further discussion here: #511