|
You are here |
lists.swift.org | ||
| | | | |
nora.codes
|
|
| | | | | ||
| | | | |
pointersgonewild.com
|
|
| | | | | Static vs Dynamic: Why not Both? | |
| | | | |
weblog.raganwald.com
|
|
| | | | | [AI summary] The post discusses the debate between dynamic and static typing in programming languages, explaining how Ruby's dynamic meta-programming makes static type inference difficult and arguing that this feature outweighs the overhead of explicit types. | |
| | | | |
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: | ||