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

211–220 of 698 posts

Re: The Era of Visual Studio Code

#211

Post by Constellarise »

sdevonoes wrote: post #55
TYPE_FASTER wrote: post #38

I pay for a personal subscription to the JetBrains suite, use IntelliJ and PyCharm all day, and have also used Visual Studio all day in the recent past. The combination of modern IDEs with modern hardware is pretty awesome. My use of Emacs fluctuates depending on the job, language, environment, etc. but I've mostly used it for Org mode and a scratch pad since I signed up for JetBrains. That said, I tried Nova from Pa…

I use JetBrains suite as well. If only they could offer ONE IDE that is configurable to be used on many programming languages. Having many different binaries is a pita.

IntelliJ Ultimate with the plugins does this but it's not quite as smooth as the individual IDEs.

Re: The Era of Visual Studio Code

#212

Post by zanny »

nickjj wrote: post #139

The thing that bugs me about VSCode is it's labeled as open source but a lot of pretty critical and interesting components are closed source so you have no idea what's going on under the hood. Normally that's not too big of a deal (I use plenty of closed source apps), but when it's Microsoft it's hard to trust what they are doing with that data. That and I feel that this promotes vendor lock-in at multiple levels. Ov…

Like the Chrome and Chromium relationship a lot of distros package VS Code as just Code for a version built by your distro without the proprietary extras.

Re: The Era of Visual Studio Code

#213

Post by spongechameleon »

VSCode looks great and has a nice debugger but going through plugin management again is too much for me.

I’ve already invested the time and effort to setup neovim with coc as my general go-to editor and have very few complaints. If I ever need a true IDE for something I’ll just open something batteries-included like Jetbrains or Pycharm.

Re: The Era of Visual Studio Code

#214

Post by catern »

As far as I know, there are no serious email clients for Visual Studio Code. So the kind of obsessive users, the ones that want to do everything with it, the presence of which indicates a really good piece of software, don't use Visual Studio Code. I consider that a fatal indictment of Visual Studio Code.

Re: The Era of Visual Studio Code

#215

Post by xfer »

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…

Open-source C/C++ LSP server exists, clangd exists and ccls(https://github.com/MaskRay/ccls) is build on libclang which works very well for a few of my projects. I am not sure about python since i don't use it much.

Re: The Era of Visual Studio Code

#216

Post by int_19h »

ImaCake wrote: post #113
redisman wrote: post #72

Kind of a weird set of text editors in the article. I think the preferred tools depend highly on your language and environment. I'm guessing this is for the JS-frontend specialization mainly. If you did Java, C* etc. then the ubiquitous text editors/IDEs were not these ones. I have converted to VSCode because it just works and I don't have to mess with PATH or whatever. I run it on Windows, Linux and MacOS and it wor…

>I have converted to VSCode because it just works and I don't have to mess with PATH or whatever. While I love VSCode and use it every day (mostly for markdown), I have definitely needed to play around with PATHs to get VSCode working nicely with my conda installs on both windows and mac (i.e. it never seems to actually point to the right python interpreter). No idea who is at fault here, but it seems to be a consist…

The problems with Conda usually have to do with its activation. If you manually activate whatever environment you want before starting VSCode, it should pick it up fine. But if you don't, and then later you pick a conda environment, it'll try to auto-activate it in the terminal for you - and this part is brittle, because anything else using the terminal can interfere with it (and vice versa).

Re: The Era of Visual Studio Code

#217

Post by DigitalSea »

I used to be such a huge WebStorm proponent, but when Visual Studio Code reached the point where it could handle all facets of front (and back-end) development, the rich ecosystem and fast pace of updates, I cancelled my Webstorm subscription and never looked back. Admittedly, it took me a while to ditch Webstorm, because I loved that editor. The remote development session feature is amazing in itself. I thought it was a gimmick at first, but since the pandemic hit, remote development has been a staple for our company. Being able to pair with juniors and seniors alike to collaboratively debug and code, it's game changing. There is nothing like it and the stability of the sessions is impressive.

What you get out-of-the-box without needing to install a single plugin is more than some. If you're working with TypeScript you get everything you need, including an in-built TypeScript compiler. All that being said, I still lean on Sublime Text Editor 3 when working with large files, which VSCode is still not perfect at dealing with. It's easy to forget that VSCode is an Electron app.

Re: The Era of Visual Studio Code

#218

Post by izgzhen »

With more years into writing code, I think VSCode/Vim/IntelliJ etc. are just tools to be used for problems that they are good at, depending on your background, and to maximize your productivity. It’s a very personal thing, and any single tool shouldn’t be expected to be versatile.

Re: The Era of Visual Studio Code

#219

Post by paxys »

willbw wrote: post #198

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…

While editors like IntelliJ are definitely more polished out of the box, something that may not be apparent is that internally they are all standardizing on tooling and protocols put in place by VS Code in the last few years.

Language toolchains are now expected to provide IDE-specific features on their own (by implementing a language server), and so IDEs themselves don't need to focus on making the language better. So the biggest sell of IntelliJ, reSharper etc. won't be relevant for too much longer, since every editor can (or will be able to) e.g. understand Java and provide basic fixes and refactorings.

Re: The Era of Visual Studio Code

#220

Post by g5becks »

As much as I like vscode. I’ve yet to find a mainstream programming language that it provides support for better than a Jetbrains based IDE. Which is really sad, because if it did, I’d switch in a heartbeat.
Post reply on HN