This is always one of the first things I setup on a project and teach or encourage my teams to do… I’m always surprised how many devs would rather use print statements all the time (not just in Rust, but especially JS/TS) when it only takes like 5 minutes to configure the debugger. Maybe 10 minutes if you need to search how to open the debugging port in Chrome/FF.
Unfortunately a shockingly large number of people don’t get this… including my old boss who was running an AI-based startup 💀
The worst is when you're not expecting it and get ambushed with a whiteboard...
Is it actually ready to use? I don’t see much information about how to use it. I know there’s been work on integrating cosmic-text, but I notice this issue is still open: https://github.com/iced-rs/iced/issues/320
The main issue I've come across experimenting with Rust UI frameworks is that none of them seem to have a decent multiline / rich text field story. Iced and the like are nice for simple apps but if you need to e.g. input Markdown and render it nicely all in one field you're out in the wilderness.
Alright, time to update my team's linters and formatters...
Yup, I've already been really frustrated by this... Google's search results are so useless, full of advertisements, blogspam, astroturfing, etc, the only way to read about genuine reviews and experiences about stuff is to add " reddit" to the end of my search queries.
I wouldn't say "martial law", but if they're gearing up for their IPO then I wouldn't be surprised if they take "harsh" measures to kick out uncooperative mods and force subs to reopen.
Cool, done and done
In addition to the others mentioned, I highly recommend trying out AstroNvim! It's got a great set of defaults, based on lazy.nvim, and it's easy to modify and extend.
I also do recommend taking the time to write your own config from scratch... even if you end up scrapping it just to use one of the pre-made configs, it's worth it to learn how vim works. And you'll quickly discover you have a new hobby in life... configuring your text editor.
I never went through it "end to end". I think it's important to cover the essentials up to ownership, lifetimes, generics, etc, but most of the topics after chapter 10 you can pick and choose as you come across them in real life. The most important is to just start any kind of project and see what questions you come across as you build.
Like another commenter I’m also running Proxmox. I have a couple VMs to ensure certain services have total segregation, and otherwise usually configure systemd services from my nix flake.