This is so awesome. Well done! I played a little with Pico/RP2040 (as a hobby), and it is so much fun. I wish educational content and institutions would embrace it more quickly.
This is so counterproductive. I hope the Rust Foundation and the Rust Project change their minds and take a more reasonable route.
Protecting against misrepresentation is completely understandable, but forbidding any common and reasonable use just because of it is so counterproductive.
There is a learning tax at the beginning, for sure, but this is a fixed cost. We experience that once this first hump is passed, the code and output quality is higher, and the cloud resource cost decreases significantly.
Now the challenge is to hire new developers that are not familiar with Rust; it would take a month or so for them to be productive (assuming robust internal code practice). But, well worthwhile in our opinion, as least for greenfield application/services.
We have been building relatively big enterprise cloud applications with a high level of compliance over the last decade and a half, and our next blueprint is all Rust on the backend (web server, web services, and job/micro services). For our approach, Rust is a transformative language for those parts of our systems.
Agree, for our approach, sqlx has the right level of abstraction. Not too high, not too low, and close enough of a sql builder pattern to be very useful. (We are not using the compile time type validation though).
I have rewritten a relatively small but critical 2k CLI from nodejs/ts to Rust, and this was the best decision ever. Cold start and runtime performance got a big boost, but also the code design got much better, and the code is much simpler to maintain and evolve. The single binary install was also a big boost, which I assume is similar to Go.
Since then, we have written all our CLI in Rust, regardless of size.
Tip: for small personal CLI, "cargo watch -x 'install --path .'" can make the whole dev experience script-like.
