Blitz VS cargo-watch

Blitz is also an open-source project that allows users to access the code and allows to contribute. Their community has generated a lot of impact as well, and has grown rapidly over time since the creation in 2020:

Not yet, I actually just whipped it up quickly last week after I was browsing the Notion subreddit and it reminded me of myspace.

These are the tools I used:

* BlitzJS (https://github.com/blitz-js/blitz)

Maybe you could help/join this project? https://github.com/blitz-js/blitz

Hello, I'm the creator of Blitz.js (first announced 2.5 years ago)

Today the Blitz.js 2.0 pivot to a modular Next.js toolkit reached Beta status [1]

Previously Blitz abstracted Next.js, but Blitz 2.0 is now a modular toolkit that plugs into any new or existing Next.js app. Blitz picks up where Next.js leaves off, providing libraries and conventions for shipping and scaling small to large apps.

When I first created Blitz, my aim was to have an all-in-one fullstack framework for Javascript like Ruby on Rails. But that proved to be too difficult. I've decided that achieving an all-in-one framework for JS like Rails is too difficult unless you have a ton of funding and don't have to make meaningful money.

The difference with JS is that client-side frameworks like React have an incredible amount of complexity. Trying to manage all of that and all the other fullstack framework stuff like API layers, auth, file uploads, etc is too large of scope.

So now Blitz is no longer trying to do it all and is focusing on all the non-frontend functionality you need to ship web apps.

Going forward, we want to be the most trusted technical resource for rapidly building and scaling full-stack TypeScript apps.

[1] https://github.com/blitz-js/blitz/releases/tag/v2.0.0-beta.1

I used cargo-watch here so that every time my source changes, the server will automatically restart and re-serve the updated code.

watch-one-test test_name: # More info on cargo test: https://doc.rust-lang.org/cargo/commands/cargo-test.html # More info on cargo watch: https://github.com/watchexec/cargo-watch cargo watch -x check -x 'test -- --test-threads=1 --nocapture {{test_name}}' -c -q

Rust: RPDS https://docs.rs/rpds/latest/rpds/ and Im https://docs.rs/im/latest/im/

Rust isn’t great for letting you do FP things like other languages, but it does have the best type system imho which makes it the leading functional programming language right now imho. If you’re not using too many specialized python packages then I recommend using Rust instead, even for toy demos, as you can be more confident your code works without needing to run it and wait for a crash like you would in debugging python, and the tests also run faster in rust due to the incremental compilation. Use cargo-watch and you can retest your code every time you save your work.

https://github.com/watchexec/cargo-watch

I usually write a make command to cargo watch and rerun each test file : code file pair independently so then you won’t rerun your tests in other modules when you change the one you work on (faster but might miss stuff if you change API contracts which touch other parts of your codebase)

you can use cargo-watch to real time run tests on save in your attached vs code console session which is about as close to what you're asking as I think exists for rust

Note that cargo, by virtue of being a package manager for a programming language, is primarily going to be dealing with library packages. That's not because it can't manage executables (see cargo-watch for a particularly useful example), it's just that it's less common.

Also check out cargo-watch -- https://crates.io/crates/cargo-watch

Unless there's a new issue, I think this is what was here: https://github.com/watchexec/cargo-watch/issues/249

A feature that I look for whenever possible in my development environment is Hot Reload, with it, every time a file is changed and saved the application restarts, so the cycle of writing-evaluating-refactoring code becomes extremely fast, for Rust, we have cargo watch, I suggest taking a look at the documentation for more details.