The Rise of Microsoft Visual Studio Code • Hacker News Board

Re: The Rise of Microsoft Visual Studio Code

#161

Post by gknoy » Thu, Dec 06, 2018, 10:41 PM UTC

emerongi wrote: post #100

bassman9000 wrote: post #30

Earlier quoted context omitted.

amen people look at me like I'm an old crazy dude because I don't use a git UI or eclipse, or intellij, or from sublime. Git already has plenty of quirks, adding another layer of unknown on top of it is a no-go

I've started using VSCode for git push/pull/branch and staging. This is what I use git for 99% of the time anyways and since they are simple commands, triggering them from VSCode is faster than falling back to CLI. Staging/diffing is especially convenient with VSCode. `git add -p` used to be my most-used command, but VSCode just makes the process easier.

If you stage things often enough, `git add -u` might be enough. It's pretty much what I use all the time, aside from the few times I do `git add -up`.

Re: The Rise of Microsoft Visual Studio Code

#162

Post by aaaaaaaaaab » Thu, Dec 06, 2018, 10:48 PM UTC

kbd wrote: post #37

hprotagonist wrote: post #11

There are some warts, but it seems nice from afar. The biggest wart is/was the "FUCK FUCK FUCK" git clean vs git reset UX error: https://github.com/microsoft/vscode/issues/32405 . This is a fantastic demonstration of why i exclusively use git from a command prompt -- i know what will happen and nobody's going to reinvent terms to put on buttons that just confuse me. In my life: - I'm committed to emacs for org-mode a…

> This is a fantastic demonstration of why i exclusively use git from a command prompt... Thanks for this. I've always felt the same way but haven't been able to put my finger on why. As more things get integrated into my editor (I use VSCode) I feel like I should use the shiny features, but for source control I think I'm going to only use the commandline forever. (Edit: though plugins such as GitLens that give you s…

Hint:

    git add -i

Re: The Rise of Microsoft Visual Studio Code

#163

Post by d_burfoot » Thu, Dec 06, 2018, 10:50 PM UTC

It's interesting to me that Go does so well. I have a buddy who convinced his shop to switch over to Go for the following reason: he knew that they were not going to be able to consistently hire good programmers, and he thought Go was a way to mitigate the problems arising from this situation. In other words, Go is a language where newbie programmers can still do okay. He also claimed that Google developed Go for this reason, referencing the infamous Ron Pike quote ("They're not capable of understanding a brilliant language, but we want to use them to build good software").

Re: The Rise of Microsoft Visual Studio Code

#164

Post by feketegy » Thu, Dec 06, 2018, 10:51 PM UTC

Nimitz14 wrote: post #159

mawburn wrote: post #147

Earlier quoted context omitted.

I feel like you should spend some time with Go. If I were building a startup, I would probably choose Go for core infra for being able to move quickly as a developer and write incredibly performant code with about as much mental overhead as most dynamically typed languages. Anecdotally, I've seen it replace Java in quite a few small and medium sized established companies.

> I would probably choose Go for core infra for being able to move quickly as a developer At the company I used to work at it took nearly a 1000 lines to replace an 80 line bash script. So I can't help but laugh at this statement.

Since when LoC is a meaningful metric?

Re: The Rise of Microsoft Visual Studio Code

#165

Post by vrazj » Thu, Dec 06, 2018, 10:52 PM UTC

Nimitz14 wrote: post #159

mawburn wrote: post #147

Earlier quoted context omitted.

I feel like you should spend some time with Go. If I were building a startup, I would probably choose Go for core infra for being able to move quickly as a developer and write incredibly performant code with about as much mental overhead as most dynamically typed languages. Anecdotally, I've seen it replace Java in quite a few small and medium sized established companies.

> I would probably choose Go for core infra for being able to move quickly as a developer At the company I used to work at it took nearly a 1000 lines to replace an 80 line bash script. So I can't help but laugh at this statement.

I can replace those 1000 lines with a bash script of 1 line that just calls the Go program ^_^

Re: The Rise of Microsoft Visual Studio Code

#166

Post by kbd » Thu, Dec 06, 2018, 10:53 PM UTC

aaaaaaaaaab wrote: post #162

kbd wrote: post #37

Earlier quoted context omitted.

> This is a fantastic demonstration of why i exclusively use git from a command prompt... Thanks for this. I've always felt the same way but haven't been able to put my finger on why. As more things get integrated into my editor (I use VSCode) I feel like I should use the shiny features, but for source control I think I'm going to only use the commandline forever. (Edit: though plugins such as GitLens that give you s…

Hint: git add -i

That is not close to the same thing.

Re: The Rise of Microsoft Visual Studio Code

#167

Post by pippy » Thu, Dec 06, 2018, 10:57 PM UTC

interesthrow2 wrote: post #89

It's a good text editor, first and foremost. Compared to netbeans, eclipse, visual studio, even intellj idea in my opinion. The same thing that made textmate, then sublime text successful made VSC successful. I takes a few seconds to launch, even on my celeron machine with 2Gigs of RAM, it's relatively minimal and unlike intellj it doesn't appear to be analyzing my whole hard drive for hours for no reason... the iron…

I still use Netbeans as my daily driver, but it's been in a death spiral. Now it's the Apache graveyard and will never get modern features like SASS.

Of all the IDEs I've been dabbling with for a replacement, I'm still deciding on Visual Studio Code or PHPStorm.

Re: The Rise of Microsoft Visual Studio Code

#168

Post by woolvalley » Thu, Dec 06, 2018, 11:00 PM UTC

brokenwren wrote: post #4

VS Code solves different problems then IntelliJ, PyCharm and Atom. I'm not sure this is a fair comparison. For example, I wouldn't ever code a full Java stack in VS Code. I'd go straight to IntelliJ.

IntelliJ has a huge head start in targeting Java. Right now it's my python & golang editor of choice.

Re: The Rise of Microsoft Visual Studio Code

#169

Post by Apocryphon » Thu, Dec 06, 2018, 11:03 PM UTC

johngalt wrote: post #130

> Engineers who use Go are also especially strong. If you know why, please let me know. Because there is almost no reason to learn Go. Most shops want JS/Java/Python/C# etc... The primary reason to learn a language like Go is because you want to for it's own sake. It's not that you must learn Go in order to be good, or that knowing Go makes you better. Rather it's difficult to be bad and still have the desire/interes…

Does this hold true for Dart, one wonders.

Re: The Rise of Microsoft Visual Studio Code

#170

Post by thatsaguy » Thu, Dec 06, 2018, 11:03 PM UTC

emacsuserrrr wrote: post #19

NotANaN wrote: post #10

"Do Emacs and Vim users have some other characteristic that makes them more likely to succeed during interviews?" I think the Interview Pass Rates chart makes it clear that the answer is a statistical "Yes", at least for Emacs.

Maybe it’s because the editor was taught to students at places like MIT, Berkeley, etc?

More probably because editors with a steep learning curve (emacs/vi) tend to select for people more willing to invest effort in learning.

The same can be said for Go when Go was relatively new. You learnt [Go^H^Hnew thing] because you thought it was interesting or wanted to play, not because you had to.

As a secondary effect, editors in the likes of emacs/vi require a different mindset compared to an IDE when programming on large projects. There's no question that all IDEs in general have an huge advantage for "all things discoverability" (from project layout to built-in doc).

I personally rely much more on documentation and memorization than autocomplete, despite autocomplete-like extensions being available to both emacs/vi for quite a while. There's a steep hill to climb when approaching large, new codebases when working this way, and it definitely doesn't pay off for quick fixes.

That being said, I used anything from IntelliJ, NetBeans to VSCode and when thinking about "good editor" the first thing that comes to mind is: zero latency. If your computer is slower than you, there's a problem somewhere.