I rather like the Anbernic RG35XXSP for the form factor. It is missing analog sticks, which does cut down on playable games a little but it's cute and tiny and is decently powerful for the price and has good community support. The rest of the RGYYXX line(where YY is the screen size) uses the same hardware but have different form factors so you can pick what you like best.
Having never touched rust before, this seems like a good launching point.
Curious though - why did Microsoft create this? Presumably they would be more interested in a C#/.NET guide for Rust developers.
Microsoft employs a number of people writing Rust code, with more on the way. I don’t have specific context as to why this guide was created, but it’s not like .NET languages are the only languages used at Microsoft.
With any solution, you’ll need to have some awareness around SQL injection, CSRF, XSS, etc. Some frameworks have sensible defaults to help you avoid common mistakes, but there’s no 100% fool-proof solution.
Performance and dev experience yes. Simplicity-wise I guess one could argue that Django takes the crown as long as you're okay with the compromises you have to make. I not sure what you mean by value, if it's cost of hosting the service then I'd say yes again because it requires less resources than all the other alternatives.
I've been going thru Astro tutorials and playing around with it. Haven't done anything with Drizzle yet, but I like it a lot, thanks again for the suggestion.
For getting a job? Express is probably less common in enterprise, but since the whole stack is JS/TS you'll have no problem porting your knowledge from that to any of the newer server-side frameworks. React is to my knowledge still the most widely used framework in modern front-end development.
Regarding self-hosting, make sure you look into isolating the RPi you use to serve your app from the rest of your home network as much as possible, and change the default password.
Rust can compile to both easily, and I use a single FFI function that pass JSON between the UI/Rust logic. There I model a Request/response that is similar to HTTP, and the rest is pure Compose/SwiftUI stuff.
