Explore >> Select a destination
|
You are here 
|
blog.yossarian.net | ||
| | | | |
leblancfg.com
|
|
| | | | | Documenting my first steps with Rust, from installation to running a simple script. | |
| | | | |
rust-unofficial.github.io
|
|
| | | | | Learning Rust With Entirely Too Many Linked Lists | |
| | | | |
matklad.github.io
|
|
| | | | | I've learned a thing I wish I didn't know. As a revenge, I am going to write it down so that you, my dear reader, also learn about this. You probably want to skip this post unless you are interested and somewhat experienced in all of Rust, NixOS, and dynamic linking. | |
| | | | |
nguyenhuythanh.com
|
|
| | | In web development and deployment, most software engineers are familiar with either: Separating the built SPA and the backend (Client-Side Rendering), or Return HTML directly from the backend (Server-Side Rendering) I recently (re)discovered 1 that there is a third way: embedding the built SPA into the backend's binary file, and serving it directly. I think this is an elegant approach, as the pros are: Simpler deployment as we only have one binary file in the end Simpler code where we don't have to take into account CORS and the backend endpoint since the frontend and backend are served from the same origin 2 The cons are quite clear: | ||
