incubator-retired-wave VS cargo-watch

FWIW, they donated the project to the Apache Foundation, so it's open source (albeit unmaintained).

https://en.wikipedia.org/wiki/Google_Wave

https://github.com/apache/incubator-retired-wave

FWIW iirc it was continued for some time by apache (https://incubator.apache.org/projects/wave.html) but is also discontinued now. (I hope thats the correct project, but I'm pretty sure).

Also here: https://github.com/apache/incubator-retired-wave

to sobie postaw lokalnie

> Setters and getters are only popular in Java EE/Spring based environments (and it can be easily useful).

I'd love to see stats on how common this stuff is amongst java programmers. I agree that modern java has lots of modern tools to write reasonable code - like closures and functional primitives. But its very normal amongst a lot of java programmers to never use that stuff. I believe you if you tell me your team uses a modern, nice subset of java. But believe me when I say lots of people out there don't.

I worked as a professional interviewer for a year or so recently and interviewed 400+ programming candidates. One of the tasks was a 30 minute coding challenge - using the candidate's own computer and preferred language. A huge percentage of the java programmers, even under explicit time pressure, wasted time adding needless junk (like getters and setters or extraneous, pointless classes) to their code. I think I only saw 1 or 2 java candidates use any of java's functional programming primitives (like map) to keep their code terse and clean.

Is that the fault of java, the language? I don't know. As I said in another comment I think the problem is cultural. I don't really have a problem with java-the-language. But a large part of java-the-community seems blissfully content with mediocrity. I took java off my resume years ago because I don't want that kind of coworker.

> How do you write code, are you copying something by typing?

I don't copy+paste because in the languages I use I don't need to. Thats what the compiler is for.

> I’m sorry to assume it, but I think you only know about java development from third-hand infos and it has nothing to do with reality.

Nope. Eg:

https://github.com/apache/incubator-retired-wave/search?q=ge...

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.