Explore >> Select a destination
|
You are here 
|
www.shuttle.rs | ||
| | | | |
andreabergia.com
|
|
| | | | | This post is part of the Languages Opinion series. Languages opinion - part one - JVM Languages opinion - part two - Rust ??thispost Languages opinion - part three - Javascript and Typescript Welcome back to my mini-series about programming languages. In this post, we will talk about one of the most interesting programming languages that I have seen in a long while: Rust. | |
| | | | |
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: | |
| | | | |
www.shuttle.dev
|
|
| | | | | This guide is a deep-dive on Axum, a Rust web backend framework. We look at using Axum to write a competent web service with middleware, routing, static files and more. | |
| | | | |
www.khronos.org
|
|
| | | KTX (Khronos Texture) Library and Tools. Contribute to KhronosGroup/KTX-Software development by creating an account on GitHub. | ||
