241–250 of 487 posts
This is not nice -- https://github.com/Microsoft/vscode/issues/5275
> This is intentional. The C# plugin is now an additional install instead of bundled with the installer. https://code.visualstudio.com/updates/vFebruary#_languages-c...
Earlier quoted context omitted.
"Vim and Emacs are still superior if you want to put the time in, and both have non-terminal interfaces." I don't need an instruction manual to figure out how to close VSCode.
>> and both have non-terminal interfaces. > I don't need an instruction manual to figure out how to close VSCode. To close GVim, you click the 'x' in the upper right/left corner, like any other window.
I'm your standard unix greybeard, the sort that uses org-mode to outline-structure their emacs config (that's actually what I do, not even a hypothetical), so I approached VSCode with skepticism. I have actually been really impressed. It's fast and responsive, even on Linux, and the TypeScript tooling is fantastic. I think with a bit more UI work (like vi keybindings) it could potentially become my preferred editor.
I'm chuckling (not in a bad way!) at the emacs user that prefers vi keybindings expressing optimism about a Microsoft editor written in a statically typed variant of Javascript. Progress is cool.
One of the things people does not seem to mention is the great debugging support you have in VSCode. The possibility to easy setup debugging with support for breakpoint, step through, inspection and so on. For react-native VSCode is the only IDE I have found which enables this. Previously one had to open Chrome and debug your apps from there, to have it inside the IDE makes it so more convenient. The same goes for No…
VSCode knockouts Atom in a dispute for becoming a developer editor in a corporate computer. Sure, you all have root password in your computer. Unfortunately, I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me. I didn't know about VSCode before this HN post, but I was trying to use a new editor instead of Notepad++. I…
> To quickly test a new general code editor I just want 3 "simple" things: column selection, regexp search and replace, and a python mode. What do you mean by python mode? Just syntax highlighting or something more advanced like an integrated REPL?
There's a few other nice-to-haves, but those are the big ones.
Earlier quoted context omitted.
Just wanted to say I find Notepad++ to be an excellent tabbed editor, especially for XML or SQL. I use it on windows all the time and really miss it on OS X where I find Textmate to be a bit awkward.
I like Notepad++, but I prefer one that works in Windows and in my linux home computer.
I'm your standard unix greybeard, the sort that uses org-mode to outline-structure their emacs config (that's actually what I do, not even a hypothetical), so I approached VSCode with skepticism. I have actually been really impressed. It's fast and responsive, even on Linux, and the TypeScript tooling is fantastic. I think with a bit more UI work (like vi keybindings) it could potentially become my preferred editor.
I've seen the vi keybindings complaint a few times in here, and it's my major complaint as well. There are a few plugins, but they just aren't even close to usable in my opinion.
Having said all that, many of the unimplemented parts in extensions across the board come down to limitations in the VSCode extension APIs. I've been watching the VSCode team, and they're actually pretty sharp and welcoming, too, so most issues should be ironed out, given enough time. (Although it hasn't been prioritized at this point.)
However, the appropriate unit of measurement to describe how long I've been using Vim is "decades", and through observing (but never seriously using) the attempts to emulate it over the years, I've spent a lot of time thinking about what it would actually take for an app to really support Vim keybindings—aside from actually just being Vim. Unfortunately, even if we assume a team with infinite resources intent on achieving perfection, there are several things about Vim that prove to be irreconcilable with the way almost every interested app is implemented. The only way around this will have to come down to Vim users either collectively participating in some "Great Vim Shift", or just ignoring the remaining gaps entirely and continuing to put up with incomplete emulations.
Earlier quoted context omitted.
> To quickly test a new general code editor I just want 3 "simple" things: column selection, regexp search and replace, and a python mode. What do you mean by python mode? Just syntax highlighting or something more advanced like an integrated REPL?
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.
Earlier quoted context omitted.
You're arguing that stating that water is wet is an assumption
If it's so obvious then it should be easy to back up your claim with data.
For example, do productive programmers tend to use Vim or is it the other way around? It's hard to find the causality.
Earlier quoted context omitted.
Try building a large webapp in vi and then comment. These days what you do is more important than what you use to do it, use vi or emacs or some shitty text editor, but eventually you need a real IDE with a GUI, vi is great, I love it, but it isn't the thing to be used for a large web app. >ut why spew uninformed bullshit when any semi-knowledgeable linux/unix dev knows that vim and emacs run laps around vscode, subl…
> Try building a large webapp in vi and then comment. I've built several using mostly vim as the editor. > These days what you do is more important than what you use to do it, use vi or emacs or some shitty text editor I mean that's a cute opinion, but both vim and emacs are much more powerful and flexible than eclipse, intellij, visual studio or other similar crap. > but it isn't the thing to be used for a large web…
Nice claim, now do you have data to back up your claim? Meanwhile let me ask you a few quick questions.
Okay, how do you automatically organise imports in emacs? Can you jump to the declaration of an expression with just pressing one button? How do you extract functions or values quickly without having to fiddle around with copy paste? If you use a language with type inference can you quickly view the inferred type by pressing a single button?