Live data from Hacker News

Visual Studio Code 1.0

code.visualstudio.com

251–260 of 487 posts

Re: Visual Studio Code 1.0

#252

Earlier quoted context omitted.

The only bad part about Jetbrains is that no matter how much i've tried i can't use a text editor without feeling crippled. A big factor is probably that I started programming using Jetbrains tools (except some c++ in codeblocks before that). It's so awesome everything else just sucks. The problem is when i want to try some language that is not well supported by IntelliJ. No matter how cool the language is i get frus…

I know what you mean, I started programming back in the 80's as a kid so I spent about a decade without anything that looks like a modern IDE and since then I've used nothing but IDE's, I can live without an IDE but I seldom want to, it just suits my programming style.

Most importantly I always miss "Go to definition" that usually doesn't work (well?) in editors. Also in javascript. The exploratory power that comes with that is also incredible. I don't need to read your damn docs (unless the module is heavyweight and needs studying), I just want to be sure I called your mehod with the arguments in the correct order ffs!!

Re: Visual Studio Code 1.0

#253
I don't know why people are asking for a text-only mode in 2016.

HOWEVER, it'd sure be nice to open a VTE panel so that I could actually run my code.

I usually just stick with Gedit, and that way I can edit my code, and just re-run it in the terminal and see the output there, without having to change windows.

Re: Visual Studio Code 1.0

#254
post #38
post #23

Earlier quoted context omitted.

But you shouldn't need high end hardware to run a text editor.

It's interesting how people seem to have very different experiences with lag on vscode. I wonder if it's actually much more laggy on some system configurations. What are your running it on?

Not surprising since most people have their own pool of extensions that they'll install but fail to mention any time the topic comes up. This is the "Firefox is beastly" strain of criticism all over again.

Re: Visual Studio Code 1.0

#255
post #214

Earlier quoted context omitted.

I like Notepad++, but I prefer one that works in Windows and in my linux home computer.

Notepad++ does work on Linux and also Mac's using WINE.

Seriously try gvim. Not vim where you need a long ass cheat sheet just to create a new tab or move between splits. But gvim where you can be productive and use the mouse and menus when necessary.

Re: Visual Studio Code 1.0

#256
post #248

Earlier quoted context omitted.

To me (not OP), Python mode means syntax highlighting, code linting, code completion, and unit test integration from within the editor. There's a few other nice-to-haves, but those are the big ones.

In a simple text editor? My requirement would just be that copy/paste does intelligent things with indents.

For me, it's a robust extension API, because then I can have any feature I want given enough time. Atom definitely has an edge there imo. Performance is also a plus (I have no complaints there with Atom). VSCode looks promising, though.

Re: Visual Studio Code 1.0

#258

VSCode has done the thing that nobody expected MS to do, change the way code was written on Unix/Linux. I love linux/unix, but the problem always was with the lack of an awesome text editor cum IDE, yep there is eclipse but it is too clunky, I do not like sublime as it isn't FOSS (call me crazy), gedit took way too much memory, geany is fast and mean but the UI sucks plus functionality isn't that great. Enter VSCode,…

Please, elaborate how VSCode changed the way we write code on Unix? I mean, repeat your statement out loud and ask yourself how big statement you just said. No way in hell how VSCode change the way we write code as much as you stated, no way even Atom did that. Like it or not TextMate came first, and soon after that Sublime Text took over. Yeah, like it or hate it, ST with it’s very well known default monokai theme c…

At work I write Scala and the IntelliJ Scala support is simply unbeatable. It's refactoring engine etc. is fully Scalafied -- when you paste Java code, there's even a "translate to Scala" function offered. I use a "vim mode" plugin that allows me to hope around with 25j and such.

For my personal project (which is in Rust) I use Atom, which is new for me, but I find to be really impressive. Both its plugin system (which allow for all the extensibility and in my case Rust support) is fantastic, and I don't know where the complaints about speed come from (it's far lighter than IntelliJ, obviously).

I've really been enjoying Atom when I do use it, and don't see why I'd switch to VSCode unless it had better support for Rust. But perhaps I'm missing something.

Re: Visual Studio Code 1.0

#259
post #119

As much as I love trying VSCode, the lacking of tabs prevents me from keeping it open longer than 1 minute. I'm just not used to not having tabs.

I use "Working Files" as my pseudo-tabs. It's not quite the same but more or less can be used for the same purposes.
Post reply on HN