[flagged]
I started watching [3]. I have no stakes in this, but a lot of stuff I should be enraged about... I'm just not? Doesn't look fundamentally different to Debian or Firefox trademark policies. I guess it is an abrupt change in trademark enforcement for Rust.
Rust, RR, Neovim: A perfect debug combination
41–50 of 102 posts
Re: Rust, RR, Neovim: A perfect debug combination
#42Anyone got other useful tools for debugging within (neo)vim? Just seamlessly putting down breakpoints, stepping through code execution, and getting a fully fledged debugging UI experience (a la Visual Studio or Remedy BG)? This is possibly the only thing I miss from developing on Windows, and it's a shame! EDIT: I specified 'within vim' but actually I'd be down for standalone Linux app recommendations too.
I did have a couple of plugins I cant really live without (ZoomWinTab and A.vim) so Im working on porting them to lua with the help of chatgpt. Really like the experience so far. Def worth checking out astronvim / nvchad
Re: Rust, RR, Neovim: A perfect debug combination
#43[flagged]
At least Ferris can be used freely according to that document. That's good news.
Re: Rust, RR, Neovim: A perfect debug combination
#44[flagged]
who is behind this shit
Re: Rust, RR, Neovim: A perfect debug combination
#45Anyone got other useful tools for debugging within (neo)vim? Just seamlessly putting down breakpoints, stepping through code execution, and getting a fully fledged debugging UI experience (a la Visual Studio or Remedy BG)? This is possibly the only thing I miss from developing on Windows, and it's a shame! EDIT: I specified 'within vim' but actually I'd be down for standalone Linux app recommendations too.
VSCode with the CodeLLDB or MS C/C++ extensions both usually work out of the box for debugging most compiled languages (so far I tried C/C++, Rust and Zig), but compared to proper Visual Studio it's very bare bones (especially the variable view panel).
Debugging in proper Visual Studio is by far the most pleasant experience I have ever had. Flame graphs, call graphs, memory and CPU utilisation graphs, straightforward call stacks and variable views... FOSS debugging utilities don't even come close to the debugging productivity on VS 2022.
Re: Rust, RR, Neovim: A perfect debug combination
#46Investing in a good debugging tool and knowing your way around using it well, makes all the difference.
After recently doing some JavaScript work and not knowing how to debug it, any suggestions for a JavaScript debugger? Part of the problem is it's already difficult to get a modern JavaScript stack setup: TypeScript transpiles to JavaScript trasnpiles to different bundles that all get minified and backfilled and next thing you know your debugging a variable named i̷̪̱͆͛w̵̤̹̠͊̇̈x̷̨̻̽̍̄͆ on line 582956, and you ask your…
https://code.visualstudio.com/docs/typescript/typescript-deb...
https://code.visualstudio.com/docs/nodejs/browser-debugging
The JS-to-TS mapping is handled through source map (so you're 'debugging' the TS code, even though it's JS under the hood).
(also, in case you're not aware, browsers have a builtin debugger in their devtool panel, these also have source map support, but this may require some tinkering)
Re: Rust, RR, Neovim: A perfect debug combination
#47[flagged]
Re: Rust, RR, Neovim: A perfect debug combination
#48Earlier quoted context omitted.
I started watching [3]. I have no stakes in this, but a lot of stuff I should be enraged about... I'm just not? Doesn't look fundamentally different to Debian or Firefox trademark policies. I guess it is an abrupt change in trademark enforcement for Rust.
Just ignoring that it is fundamentally gross and pointless, which some people don't understand somehow, consider the practical implications. I can't casually make a youtube video or blog article teaching about Rust without worrying about trademarks if I use the word. Hundreds of rust libraries have Rust in the name and would be in violation of this policy the second it changed, etc.
I wouldn't worry about writing on rust, the language. It certainly sucks that the language, the compiler and the foundation share the same name. But it probably sucks for the foundation as well regarding enforcement.
I don't get why people like to put the name "rust" in crate names, unless they write tools that work with the language (linters, auto-formatters), it just feels redundant.
Re: Rust, RR, Neovim: A perfect debug combination
#49[flagged]
who is behind this shit
It is based on the results of a previous survey: https://old.reddit.com/r/rust/comments/wkv8gv/rust_foundatio.... Looking at where we are now it's safe to assume that not all community feedback was given the same level of care, the (vocal) community is against this, as am I.
Re: Rust, RR, Neovim: A perfect debug combination
#50rr is pure magic! I wish that it is available on macOS.