Explore >> Select a destination
|
You are here 
|
maud.lambda.xyz | ||
| | | | |
tuckersiemens.com
|
|
| | | | | Dynamically generating PNGs with your IP address in them. | |
| | | | |
tokio.rs
|
|
| | | | | Tokio is a runtime for writing reliable asynchronous applications with Rust. It provides async I/O, networking, scheduling, timers, and more. | |
| | | | |
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: | |
| | | | |
purde.net
|
|
| | | [AI summary] The post discusses topics related to startups and marketing, focusing on referral timing and Pipelo. | ||
