3 ms·
actually at the time i wrote the API, i was still considering how the FE was going to be written, so because i never used remix until this point, i didn't reali
by partly_cloudy 4y ago
actually at the time i wrote the API, i was still considering how the FE was going to be written, so because i never used remix until this point, i didn't realize they offered an all-in-one solution.
honestly i like the seperation of concerns though, so i'm happy with it. might even rewrite the API again to teach myself rust
- Kiro 4y agoSo why even use Remix? Maybe I misunderstand what it is.
- Ralfp 4y agoWith Remix, you run two two servers: - Remix server - API server When user visits your page, their first HTTP request hits the Remix, which pulls data from API server and renders initial HTTP response from your React.js UI. It then sends this response to the client, so you see full site load at one time, even with JavaScript off. If you have JavaScript enabled, the client version of the React.js UI will load and replace the HTML generated on server, making things interactive. This UI will hit Remix API server for Remix features, but you can still hit your API server from individual components if you need.