Earlier quoted context omitted.
Well, what they hiring for, their questions in a specific language, how and who is evaluating the answers, the fact that a person is looking to work for them vs other companies are all biases. Nobody should try to extrapolate their results to the whole population of software engineers. That said, Visual Studio is really on the rise. I used to think VSCode was late and could have never catch up with the Sublime's and…
VSCode is only on the rise because alternatives are really bad. Meanwhile, it offers good defaults, and decent latency on modern hardware but for me it is just a glorified syntax highlighter. VSCode becoming so popular should not tell us it is a great product, but that most modern alternatives suck.
The Rise of Microsoft Visual Studio Code
321–327 of 327 posts
Re: The Rise of Microsoft Visual Studio Code
#322There 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…
Re: The Rise of Microsoft Visual Studio Code
#323Like 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 t…
Re: The Rise of Microsoft Visual Studio Code
#324Earlier quoted context omitted.
> 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.
Ctrl+Shift+L will select all instances of the highlighted term in one shot. Ctrl+D , as you mentioned, is useful for progressively selecting the highlighted phrase within the file.
Re: The Rise of Microsoft Visual Studio Code
#325Earlier quoted context omitted.
I also very much related to this, the two exceptions I find awkward from the command line are: * Doing partial adds with `git add -p`. I see the hunk it presents see what I want from it, but then sometimes have to go through several iterations of splitting, skipping etc.. A visual tool (even like the tool in vim-fugitive) is a huge improvement. At the end of the day I'm still looking at the staged diff before committ…
There's a somewhat hidden gem in vanilla git which can be sometimes useful: git gui You can right-click on some line in the file and select "Stage Hunk for commit", etc. instead of `git add -p`. It can be also helpful for browsing history, esp. "blame digging".
Re: The Rise of Microsoft Visual Studio Code
#326Because of the popularity of VS Code on HN, I decided to give it a try. It's good. Much better than Electron or Atom for my workflow. And much faster IME. The one thing that keeps me from switching from my current IDE is the lack of Whitesmiths brace formatting. I'd pay up to $15 for a Whitesmiths plugin. Until then, I can't change. But I'll keep checking.
In which codebases is Whitesmiths formatting used? It looks so wrong if you're used to any of the other styles.