Remix clone Hacker News

Genuinely curious, how did Microsoft "shoved it down everybody's throats"? And weren't Jetbrains, Eclipse, Vim, Emacs dominant enough(especially Jetbrains) to have done so before Microsoft?

▲

bsder 9 hours ago | parent [-]

VSCode garnered such a significant market share that supporting VSCode almost immediately becomes your #1 editor (see Rust surveys: 2016-3%, 2017-30%, 2018-45%, 2020-54%, 2023-62%--note: VSCode was only released in 2016!).

Since the LSP was the only effective way that you could support syntax highlighting in VSCode, languages had to create an LSP or they didn't exist to VSCode users. Once the language supports VSCode, anyone not already steeped in the editor wars switched.

At that point, the editors had to support the LSP or get left behind.

With JetBrains, the issue is that they would have almost certainly considered an LSP as a competitive advantage. It would have taken some amazing foresight to release something like that as OSS and not be afraid of losing market share if you get vim/neovim to adopt it (you can ignore emacs market share--the editor wars are all but over and emacs lost badly).

	▲	mdaniel 2 hours ago \| parent [-]
		> With JetBrains, the issue is that they would have almost certainly considered an LSP as a competitive advantage As a point of comparison, the value that I get from JetBrains products is about 35% UX niceties[1] and 1500000% code intelligence, which no LSP that I have ever seen even strives to do that. They all appear to be focused on "jump to declaration", "what can I type here", and some of them ferry "linter" results back to the user but that is just using LSP as a conduit not that the LSP itself is doing anything intelligent That's why I throw up in my mouth when someone claims their vim+lsp is a python powerhouse because, sure, it's better than nothing but even PyCharm open source blows the doors off of any LSP 1: and even that has been under constant attack over the past few years from their gravely misguided product management team, culminating in the "you are committing code wrong" https://news.ycombinator.com/item?id=43710699