Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Era of Visual Studio Code

blog.robenkleene.com

Post reply on HN
Print view View original

191–200 of 698 posts

Re: The Era of Visual Studio Code

#191

Post by jopsen »

laqq3 wrote: post #114
stu2b50 wrote: post #35

Earlier quoted context omitted.

See, I don't think that's possible. VSCode only has 10 or so employees full time. I don't think they could make a good text editor with this kind of dev speed on 3 different platforms natively. Sublime is great but it updates once every other blue moon for a reason.

> Sublime is great but it updates once every other blue moon for a reason. I like both editors (VSCode and Sublime) and just want to point out that Sublime Text 4 is in semi-public alpha. It is "semi-public" in the sense that the download link is given in the Discord channel, but anybody could join it. For nine months or so, there has been a new release of ST4 every 2-3 weeks. Development is definitely ongoing (thoug…

I was a huge sublime fan, but it seems like the plugin eco-system moved on.

At the end of the day, I go where the plugins are.

Re: The Era of Visual Studio Code

#192

Post by JMTQp8lwXL »

jcrben wrote: post #116
andrewstuart wrote: post #111

Earlier quoted context omitted.

I'd be more interested in VSCode if Microsoft's strategy was to relentlessly implement the most popular plugins into VSCode natively such that the most commonly used and needed functions were built in and did not require plugins. The problem with systems that are really just frameworks for other to build on is they become reluctant to build stuff that plugins exist for. The philosophy becomes to depend on the plugins…

No way, it sucks when you've got a monolith full of unnecessary gadgetry. Right now VSCode is already getting pretty bloated w/ builtins

I could not understand why anyone would be happy if VSCode came with 50 core un-installable plugins and none of them were useful to you, since everyone has slightly different projects they're working on. It would be inefficient and it wouldn't cater to a larger user base.

Re: The Era of Visual Studio Code

#193

Post by ampdepolymerase »

jyriand wrote: post #108
barkingcat wrote: post #91

Earlier quoted context omitted.

You don't need all the plugins. You just need a curated set. And some of the plugins are fantastically high quality. The Microsoft Python one is excellent, as is the Remote development one. I'm a fan of VS Code because in spite of it having a plug in system, there are great plug ins there. And that one single great plugin is all that is needed (for that specific purpose)

Does VSCode have something similar to emacs’s spacemacs, doom or prelude?

They do have extensions that install multiple other extensions.

Re: The Era of Visual Studio Code

#194

Post by int_19h »

drdaeman wrote: post #173
andrewstuart wrote: post #21

I'm not a fan of VS Code because everything is a plugin. And plugins are inconsistent, buggy, inconsistently documented, hard to use and find and update and goodness knows who developed them. Plugins can be duplicated, outdated, abandoned and incompatible. But worst of all, a big pile of plugins isn't a consistent integrated product vision. I gave VSCode a solid go, and I had to keep installing plugin after plugin, b…

I think it's the core product values for me. JetBrains IDEs are development environments, meant for editing code, in specific primary language. They really try their best to understand code that user works on (which is a hard problem, because code is frequently invalid while it's being actively edited), and make it as convenient as possible. VSCode is - in my understanding - essentially, a step over older glorified e…

PyCharm is also a common IDE core with a bunch of Python-specific extensions on top. It just so happens that JetBrains ships those extensions pre-packaged under different names for various target audiences, and they - especially the Java ones - have a lot of features, and decades of polish.

Re: The Era of Visual Studio Code

#195

Post by xfer »

jhoechtl wrote: post #56
bad_user wrote: post #48

Earlier quoted context omitted.

It has the rendering engine of a browser and that also has some advantages in rendering capabilities. Browsers are really good at rendering rich text, it's what they were designed for, and a native editor can't beat that. There's the occasional big text file that I have to open, in which case Vim would do a better job. But usually VS Code has no performance issues for me.

Me as a Vim fan I thibk its save to say that even vim doesn't handle large files well and is especially bad with files containing long lines.

Same with Emacs, long lines for even a small file is problematic.

Re: The Era of Visual Studio Code

#196

Post by bigDinosaur »

Zenbit_UX wrote: post #163

Anyone else think it's weird they used the term "text editor" ~100x in that article but what they're actually just comparing IDEs. It's weird to read an article comparing the most popular "text editors" of all time and not have one mention Microsoft Word... I'd expect notepad, open office docs and pages to get honerable mentions on such a list.

It's just a disparaging term for people who think that good software comes only from a full IDE. To be fair though, MS Word is a lot more than a text editor, e.g. you don't save its documents as text documents but as bundles of style/layout/text/fonts.

Re: The Era of Visual Studio Code

#197

Post by jhasse »

bsder wrote: post #181
alexmcc81 wrote: post #50

Earlier quoted context omitted.

You're right - it is a trojan horse and people are eating up the 'MS heart Open Source' PR. It's obvious when you look at what they're doing with language servers. They've replaced the open source Python language server with a closed source one. The C/C++ was always closed. Their remote feature and collaboration tools are also closed. They're slowly making people depend on MS services without even realising it. They…

> They've replaced the open source Python language server with a closed source one. The C/C++ was always closed. Their remote feature and collaboration tools are also closed. They're slowly making people depend on MS services without even realising it. So, what you're saying is that the absolutely enormous number of Python and C/C++ people can't produce a decent open-source plugin while tiny communities like the Rust…

Multiple open source C++ language server for VS Code already exist.

Re: The Era of Visual Studio Code

#198

Post by willbw »

I find this post along with the comments in "A Picture of Java in 2020" https://news.ycombinator.com/item?id=24551390 to be incongruous with my experience as a professional developer.

My first couple of years writing software I used Vim, then VSCode, then worked in a Java shop and was forced to use IntelliJ. I didn't like it at first, but now after a couple of years I cannot see how I lived without it.

The idea that VSCode is the future doesn't seem right to me. JetBrains products allow you to do so much out of the box, without installing a million plugins that may or may not work. In IntelliJ I can write a half baked statement like `new Foo()`, and then Alt + Enter my way to it being `foo = new Foo();` as a private member variable of the class in no time. If you take time to set up configuration it becomes even more powerful. Even these basics are more difficult in VSCode.

To me the future is IntelliJ for Java and all other languages should seek to have such a nicely integrated experience with an IDE.

I am not even sure I could write Java from scratch in Vim - its really that I'm using IntelliJ, not writing Java. Is this bad? In some pure sense, sure, you are further from the language. But I don't care because I can write and edit code some multiple faster than if I was in VSCode.

Re: The Era of Visual Studio Code

#199

Post by lima »

frankjr wrote: post #52

I completely switched to VS Code once I discovered the remote development feature [0]. It allows you to run VS Code locally but work on a project in a different environment (via SSH, Docker, WSL). The integration is seamless - search, debugger, terminal, extensions - everything looks and behaves as if it was running locally but is delegated to the configured remote. You can even have different remotes opened at the s…

> I use this setup primarily to have at least some sort of a barrier between my system and the gigabytes of NPM packages that get downloaded as dependencies.

You can do something similar with IntelliJ by running npm inside a Docker container with your working directory mounted into it. IntelliJ will happily index the resulting node_modules folder without executing any code on the host.

Re: The Era of Visual Studio Code

#200

Post by cutler »

zeroxfe wrote: post #165
macinjosh wrote: post #156

If you want a text editor with longevity try vim or emacs. They aren't dependent on the benevolence of a greedy corporation. Over time VSCode _will_ be raided by the bean counters at MS and it will begin to track you, give you ads about MS products, and lock you in to their ecosystem. I'll never understand why a professional developer would give so much influence over their work to the likes of MS, JetBrains, etc. Su…

Two decades of vim here, and I switched to VS Code. As a "professional developer", it's just nicer to use, and makes me feel way more productive than ever. I definitely wouldn't call it a toy.

It's not like you have to give up Vim anyway considering the good-enough VSVim plugin gives you most of the Vim basics. Personally I have found JetBrains' Vim plugin to be the best.
Post reply on HN