livingcoder

Every so often rust-analyzer in VS Code doesn't use the latest code after a cargo update and the only way I've found to fix it is a cargo clean. This means that I have to wait 5 minutes for the next build, painful. Just because of one project update. I would LOVE a faster build.

Extra info: the updates come from my dependencies that utilize my private repositories via a git = "[path]". The rust-analyzer is pulling from a cache or older version for some reason and I don't know where it is or why.

I would agree. Only if the performance is extremely similar but the readability (for some reason) is significantly better for the recursive solution would I choose that.

Rust, easily.

I love any reduction in build times. This is great news.

I'm hoping we don't have to, but the only example I saw utilizes unsafe code.

Must we write unsafe code to use Rust in NGINX?

Cursorless. It's a spoken-language programming interface that allows the programmer (of basically any language) to use specific words to target existing text, move the underlying cursor/selection relative to that target, and then run a specific modification. Think of VIM but for voice. It runs in VSCode atm as a couple extensions along with an install of the audio tool Talon. https://www.cursorless.org/

My current favorite is mostly Rust-based with the tide crate, tide-jsx crate, vanilla JS, postgres crate, and Postgres in Docker. Super easy, super fast (to develop and run), but I haven't made any large web projects with this stack yet, just small stuff.

I was thinking the same thing when I was trying to use the new base64 code instead of the deprecated version: it's unnecessarily complicated. I remember thinking "why is this so hard, so convoluted?".

As someone who learned a lot from C++ and that now loves Rust, this annoys me.

hook to Insomnia plays

And now I'm making a game. You got me.