281–290 of 487 posts
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.
Earlier quoted context omitted.
Why spend a few hours over the course of 60000+ working hours to learn how to use more effective tools?
"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.
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, they might actually have learned something.
25 minutes of deliberate practice - a single Pomodoro - is enough to become acquainted with several of Emacs features - like, navigation by semantic units and incremental search and autocompletion. You won't get proficient in that time, but it's enough to rewire yourself to actually start using it when writing code. Which will then lead to you becoming proficient while doing your regular, billable work.
Seriously, set up a Pomodoro timer, sit in front of Vim or Emacs, and try to practice a few things. You'll be surprised how fast you can learn.
(And yes, I did that, so I'm not talking out of my ass. I actually almost doubled my Emacs productivity once in 5 pomodoros - in 2.5 hours - two of which I spent watching Emacs Rocks videos, two on rewriting s-expressions with Paredit, and one on multiple-cursors.)
Earlier quoted context omitted.
Why spend a few hours over the course of 60000+ working hours to learn how to use more effective tools?
You're making the assumption that vim/emacs are more effective tools.
Nerdvana.
Still no CLI mode for editing text. Vim has had this for years. How am I supposed to integrate this behemoth into my work flow if I can't even run it in a terminal? It's just too clunky for my taste. It's also hilarious that Atom gets shat on for data collection when no one cares that VS does it too. Microsoft can do no wrong, only OSS projects have standards to live up to.
> Still no CLI mode for editing text Normally I'd be the first jumping on Microsoft products and criticize them but this is a strange statement. Most of what you can find in VSCode runs on nodejs so if you want a specific features in a CLI you don't need VSCode, just install whatever nodejs lib you need and use it from the CLI.
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…
Sounds like an undeserving environment for a developer. Why not vote with your feet?
Earlier quoted context omitted.
Well, okay, let's talk about that. Is having source control in your text editor enough of a benefit to one's daily routine as to be a step change of productivity or quality of life? It may be for you and I'm not saying you're wrong for that, I'm asking because it isn't for me; I have an alt and a tab key. Bear in mind that the claim wasn't that it's better in some ways , but that it's sweepingly better than the stuff…
Having the git diff in your editor gives you syntax highlighting and let's you edit it (the right side) like you're used to. I guess the killer feature of VS Code is multiple cursors (Ctrl+D). I only know of Sublime Text and Atom who also have this feature on Linux, not sure about Kate. Sublime Text is closed source and not gratis, Atom is slow and buggy.
Earlier quoted context omitted.
You're making the assumption that vim/emacs are more effective tools.
The best possible programming environment is comprised of emacs coupled with a "lispy" language such as Common Lisp, Scheme, Racket or Clojure and the REPL to go along with it. Nerdvana.
Earlier quoted context omitted.
Ummm, no. VS Code is a decent editor, nothing more. It certainly doesn't transform the way code is written on Unix/Linux. Vim and Emacs are still superior if you want to put the time in, and both have non-terminal interfaces. They can also be both customized to be whatever you want them to be, there's not really a limit to their functionality except what plugins are already written. Ditto for Atom, though of course,…
"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.
Earlier quoted context omitted.
I didn't downvote, but you can easily answer your question about what's interesting/exciting about it by simply reading the other comments here. It's pretty clear this scratches the itches of more than a few devs.
I read the comments, have tried it out and concluded it's just an editor :-). Evidently other people came to different conclusions.
Does anybody else use several editors all the time? I use Emacs, Vim, Eclipse, Atom, and Intellij. I don't stick to one. I wish I could stick to one editor but there is always some editor that does a way better job at a particular task. Each editor has its killer feature. I have tried turning emulation of emacs/vim on many editors to provide consistency and its never been really good. Thus I have several "default" ke…
(I actually keep both open; Java files I edit in Eclipse, but pretty much anything else goes to Emacs. I also have Emacs keybindings and Emacs+ plugin installed in Eclipse.)