The Rise of Microsoft Visual Studio Code • Hacker News Board

Re: The Rise of Microsoft Visual Studio Code

#141

Post by jokoon » Thu, Dec 06, 2018, 9:40 PM UTC

Like it was said in this thread, as long as you have an editor that is built on something js-related like electron or node-js, it just cannot beat alternatives that are made in C++.

I've tried VSCode because I wanted to have UI breakpoints with GDB, I admit that vscode seems better than atom, but for performance I have my doubts.

I really don't understand why engineers choose to use JS to made a text editor. I know that js and the dom have enabled the web, but it's because there was nothing better, choosing js to do non-web stuff doesn't only sound silly, IT IS silly.

Re: The Rise of Microsoft Visual Studio Code

#142

Post by bryal » Thu, Dec 06, 2018, 9:40 PM UTC

jamestimmins wrote: post #86

chadash wrote: post #33

Earlier quoted context omitted.

I have a theory on this. For most interview style coding problems (which tend to be algorithmic in nature), scripting languages such as python or ruby: 1) are less verbose 2) don't require worrying about typing 3) have really easy ways to manipulate strings, iterate, etc., which are often found in interview style problems Java and C# have many advantages over python and ruby, but I think that they put you at an inher…

My job involves interviewing many engineering candidates, and I see the issue with typing all the time. A competent Java dev is at a disadvantage compared to a competent Python dev, simply because it's statically typed and more verbose, meaning there are more lines of code which means more small problems that can arise. That matters greatly in a short, time-boxed context.

> A competent Java dev is at a disadvantage compared to a competent Python dev, simply because it's statically typed and more verbose

I don't think that the fact that it's statically typed is the problem. For example, I don't believe a competent Rust, Go, or Haskell dev would be at a disadvantage due to static typing, but rather the opposite.

Re: The Rise of Microsoft Visual Studio Code

#143

Post by kbd » Thu, Dec 06, 2018, 9:40 PM UTC

Drdrdrq wrote: post #134

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…

> don't have to 'git add' and type filenames manually Another option is git add -p , which asks you about each change so you can review them once more and maybe leave some (parts of) them for future commits.

Yep I have a 'git ap' alias set up for that :)

Re: The Rise of Microsoft Visual Studio Code

#144

Post by AsyncAwait » Thu, Dec 06, 2018, 9:43 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…

> It's a good text editor, first and foremost. Compared to netbeans, eclipse, visual studio, even intellj idea

Have to disagree with VSC being better than Intellij. I find Intellij refactoring, debugging and autocomplete far ahead of VSC, especially when it comes to supporting leaser known features, or recently released language changes.

Re: The Rise of Microsoft Visual Studio Code

#145

Post by ksec » Thu, Dec 06, 2018, 9:52 PM UTC

sbilstein wrote: post #5

VSCode is fast, stable, and the plugin ecosystem really beats Sublime Text at this point. I was skeptical because Microsoft but it is hands down my favorite editor.

How can anyone say VSCode is fast, and then compare it to Sublime Text ? They are not even in the same order of magnitude.

VSCode is definitely fast enough for most uses cases, but I still wish it was as fast as Sublime Text, from Scrolling Frame-rate to response time.

Re: The Rise of Microsoft Visual Studio Code

#146

Post by zygotic12 » Thu, Dec 06, 2018, 10:00 PM UTC

I've told you guys before - my 10 year old son scored 'well above average' on their interview process. We live in the UK but they are still trying to recruit him. And no - he cannot write code.

Re: The Rise of Microsoft Visual Studio Code

#147

Post by mawburn » Thu, Dec 06, 2018, 10:03 PM UTC

mrdoops wrote: post #137

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…

Go is a language designed to take CS college graduates to productive engineers at Google with as little fuss as possible. Considering it was designed for an organization in the scope of Google, it's less likely to be the best option for something like a startup, small business, or even a medium size business.

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.

Re: The Rise of Microsoft Visual Studio Code

#148

Post by sonnyblarney » Thu, Dec 06, 2018, 10:06 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.

Java on VS code is still kind of pain, which is too bad.

To me, VS Code and Typescript were made for each other.

Python is just a free bonus.

Re: The Rise of Microsoft Visual Studio Code

#149

Post by School-Cotton » Thu, Dec 06, 2018, 10:06 PM UTC

Drdrdrq wrote: post #140

bassman9000 wrote: post #120

Earlier quoted context omitted.

git has its problems, but it's a consistent, centralized (in the sense of origin/repo), well known set of problems. I use multiple IDEs/editors, and they all handle git differently. It doesn't make sense to learn yet another N sets of quirks.

> git has its problems, but it's a consistent, centralized (in the sense of origin/repo), well known set of problems. Consistent? Ha! Change branch: git checkout my-branch . Reset file to committed version: git checkout -- my-file . Git is many things, but consistent it is not. That said, I still use CLI precisely because I don't trust other software to make sensible abstractions on top of it, given that foundation i…

Consistent in time. Those warts haven't changed much in the 7 or 8 years that I've been using git.

Re: The Rise of Microsoft Visual Studio Code

#150

Post by pmarreck » Thu, Dec 06, 2018, 10:09 PM UTC

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…

> and multiple cursors everywhere is a boon for quick and dirty data munging.

VSCode has this. Hold down Command on Macs (probably Ctrl on Windows/Linux) and click. You can also select "next similar word" with command-D so you can quickly change all instances of a word to another word.