Earlier quoted context omitted.
I think what the parent meant was that VSC (along with Atom, and to lesser extent SublimeText) is a good example of "the middle way" that is rapidly gaining popularity. First we had console editors, but they weren't powerful enough, especially for newer languages/frameworks. Then we had full IDEs (VS/Eclipse/IntelliJ), but they got to be slow and clunky. Now the trend is toward "enhanced text editors" (VSC/Atom/ST):…
> First we had console editors, [...] Then we had full IDEs [...] Now the trend is toward "enhanced text editors" (VSC/Atom/ST): editors that can have modular plugin functionality and interact with the console so you don't lose any of its versatility. They're usually faster and more lightweight than IDEs but keep most of what you need Emacs has functioned as an "advanced text editor" for at least 20 years and probabl…
Visual Studio Code 1.0
461–470 of 487 posts
Re: Visual Studio Code 1.0
#462VSCode 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…
"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" Sounds like an undeserving environment for a developer. Why not vote with your feet?
Re: Visual Studio Code 1.0
#463Overall, fairly impressed with 30 minutes of play.
Re: Visual Studio Code 1.0
#464Earlier quoted context omitted.
Aside from different tools having different strengths, I enjoy learning to use new software. I think if I used one tool for everything I would get bored with it. That said, learning new keyboard commands is sometimes a real PITA. When I'm tired, I sometimes find myself trying to close Visual Studio or Sublime Text with :q.
How odd. I've used the same text editor for twenty-plus years now (hint: it has yet to be mentioned) and I find that I no longer have to think how to use it---it just happens. Then again, I consider the Unix command line as my IDE [1]. [1] Every few years I'll try an IDE. I've been doing this for over twenty-five years. I've yet to find one that I like. Over time, my bar for "what I like" has fallen to the point wher…
My favorite place to work right now is on OSX. It's Unix so you get all the command line goodies plus it has a very good GUI and great tools in the graphical environment as well (I'm thinking of XCode). Plus, I think Objective-C is pretty neat.
Re: Visual Studio Code 1.0
#465Earlier quoted context omitted.
Have you tried Vim 8? One of the major updates is plugin package management. Can't say much about it, haven't upgraded yet, but the write up on it looks promising.
Have you tried Vim 8? Have you? Or did you read the placeholder document for a version of vim that isn't anywhere near ready for general release? Because if you know where a branch or a build of vim 8 is, I'd appreciate a pointer.
Sorry if I sounded like I was endorsing it. Did you not read my comment?
Can't say much about it, haven't upgraded yet, but the write up on it looks promising.
Re: Visual Studio Code 1.0
#466Earlier quoted context omitted.
> and changing UTF encoding or line endings If you need to do those things often, there are specialized tools, including in the command line, and for batch processing. No need to do it in an editor.
I don't need to do this often but occasionally you'll need to fix inconsistent line endings, change encoding to UTF-8 or remove a BOM [0] (to stop  being prefixed by some old software). [0] https://en.wikipedia.org/wiki/Byte_order_mark
In OS X and Linux (and Windows with Cygwin etc) there are several command line programs such as unix2dos (line ending conversion), iconv (encoding conversions) etc for doing just that, so that you don't need to do it in an editor and can even automate the work.
Re: Visual Studio Code 1.0
#467Earlier quoted context omitted.
I read the comments, have tried it out and concluded it's just an editor :-). Evidently other people came to different conclusions.
I wouldn't call it just an editor, but rather a development tool which is context aware and provides a lot of info about the codebase you're working on, plus helps with the excellent IntelliSense / code completion. You should take a closer look at it's features.
Re: Visual Studio Code 1.0
#468Earlier quoted context omitted.
"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" Sounds like an undeserving environment for a developer. Why not vote with your feet?
I live in Brazil. We have some striving software houses, but they are few and pay a lot less than, say, my employer, Bigtime Consulting. To vote with my feet I'd have to accept an income downgrade of about 30%, higher risk of unemployment, and even then (heck, I'm looking for something like this right now) it's hard to find.
Re: Visual Studio Code 1.0
#469Earlier quoted context omitted.
"a few hours" ??? Come on, let's not pretend that EMACS is going to take "a few hours" to come to terms with and become more productive in than an IDE.
Actually, you can get decently proficient in just few hours. Have you actually tried sitting in front of Emacs or vim for more than 30 minutes, to the clock ? Humans have this funny thing as they grow older - they look at a thing, maybe try it out for few seconds, and then immediately determine it's too difficult and it will take forever. They rarely bother to spend actual five minutes, to the clock. If they did, the…
Not the parent, but I've spent a significant amount of time with pure vim. I use vim bindings in everything from my web browser (vimium, vimperator) to my WM (i3 & kde vim navigation bindings), to my text editors & IDEs (atom, VS, sublime)
Despite all that, I still find using pure vim to be ineffective relative to just using Atom, Sublime, VS or whatever with vim bindings. I may have internalized the most basic navigational concepts, but the more advanced / esoteric shortcuts that are essential to use vim as an exclusive editor are still ones I need to look up - and that's not counting stuff specific to vim packages liked nerdtree.
At the end of the day I'm sure you could always argue that I should have practiced differently / better / more or whatever - but to what end? There are plenty of full featured text editors on all platforms that do everything I need. Why on earth should anyone force themselves through dedicated practice just to learn the intricacies of a 20 year old editor?
Re: Visual Studio Code 1.0
#470Earlier quoted context omitted.
> On the contrary we have mostly consistent ctrl/shift + arrow behavior Are you saying Windows has consistent Control/Shift + arrow behavior? OS X is pretty consistent about this too, though Control+Arrow moves between Desktop Spaces, not related to text, but you can modify a lot of system/app shortcuts from Preferences -> Keyboard -> Shortcuts.
Ctrl arrow in Windows jumps by word. In os x, it's option arrow. I believe it's widespread but not global.
Problem is: until at least 2012 not even Apple was consistent about it.