Hacker News Reader

Comment by JoshTriplett | Hacker News Reader

> Among editors, vim remains king, though we see healthy growth in VSCode adoption at 34.1% (up from last year’s 3.8%). This growth no doubt has been helped by VSCode being one of the first platforms to get support for the Rust Language Server.

This suggests that it would help to have better getting-started guides for vim, and for using it with RLS in particular.

> 10% responded that tools aren’t use mature enough.

I've seen more than one person mention that the fact that RLS doesn't work on stable Rust is a sign of immaturity.

Also, in the context of people who had stopped using Rust:

> The rest of users mentioned [...] were turned away by Rust’s syntax, [...] or had a bad interaction with the Rust community.

Is anyone systematically looking over each of the responses that said either of these, in detail, in order to address them as well as possible?

View on HN

What I personally did not like is: I'm very minimal vim user, I don't use plugins or plugin managers, I just setup some basic options like syntax highlighting and auto indentation. All I wanted from Rust plugin is to enable syntax highlighting and some reasonable indentation. But it turns out that I must install some kind of plugin manager just for rust plugin and I would receive lots of bells and whistles that I'm not interested, at least while I'm learning.

Actually I think it's the same problem with golang. Last time I used it, I had to browse VCS history of go project, they shipped vim plugin long time ago but then deleted it, I had to recover it from there and install it into ~/.vim/.

You don't have to use a plugin manager, that's just how many people use plugins.

Furthermore, earlier in the year I upstreamed rust.vim https://github.com/vim/vim/pull/1356/ So if you're using a new enough vim, you shouldn't even need the plugin.

And thank you for that, because it works out of the box for me.

Thanks, didn't know about that.

> But it turns out that I must install some kind of plugin manager just for rust plugin

It's not well documented, but there's a much simpler way, which I used until recently (newer versions of vim already come with syntax highlighting for Rust out of the box):

Checkout https://github.com/rust-lang/rust.vim and copy everything there except the README/LICENSE/.gitignore to your ~/.vim directory, keeping the exact same directory structure.

> This suggests that it would help to have better getting-started guides for vim, and for using it with RLS in particular.

Yeah I'm not sure that there's classic Vim support, langserver.org has two things that are both for NeoVim.

> Is anyone systematically looking over each of the responses

Someone (jntrnr) did read every single response, that's part of why this post took so long to produce. I just asked him about it, basically, he's going to be giving feedback to each of the teams about the stuff that was in their area, and they can act on it that way; so that'd be the language and community teams in these two cases.

>This suggests that it would help to have better getting-started guides for vim, and for using it with RLS in particular.

https://www.reddit.com/r/rust/comments/6rx634/async_autocomp...

> This suggests that it would help to have better getting-started guides for vim, and for using it with RLS in particular.

Not really. VSCode only one of few IDEs which have integrated debugger for Rust.

> This suggests that it would help to have better getting-started guides for vim, and for using it with RLS in particular.

Oh man yeah I'm using vim to play around with Rust, would like to see a tutorial in term of usage of the plugins. Like a tutorial with vim and the guess number example would be nice while using the vim plugins. Idea whatever and VScode is meh. VScode is on the cloud iirc meeeeh.

VScode is on the cloud iirc meeeeh

It's based on Electron/Chromium and uses JS for extensions, but it's a local program in every other way. It's also fairly snappy, maybe much more so than the usual Electron app.

It does have the usual broken font rendering on Windows, as does everything that is derived from Chrome. But that's no an issue on Linux or macOS.

Broken font rendering? I've never had that happen in VSCode or any Electron application.

What does it look like? Maybe I've just missed it.

Every Chrome derived application, including everything Electron, has substantially degraded font rendering compared to native apps on Windows. Just load the same text with the same fonts and look side by side. Best way to describe it would be that the fonts are fuzzier and have less well defined outlines. Must be some kind of hinting + subpixel-AA issue, or Chrome not respecting the system ClearType settings, or whatever. The bug has been there for ages. I wouldn't care if Chrome was the only thing suffering from it, since you can use another browser, but the appearance of good Electron apps like VSCode has made it very painful.

Maybe someday Microsoft will port VSCode to Chakra.

Chakra is only the JS runtime of the Edge browser IIRC. So they'd have to open-source all of Edge in order to port VS Code to it instead (if they wanted to keep everything open source).

Someone somewhere just told me that rust sucked .. because of its community. I don't think I talked to them so I wonder what happened

Reply on news.ycombinator.com