Live data from Hacker News

The Rise of Microsoft Visual Studio Code

triplebyte.com

221–230 of 327 posts

Re: The Rise of Microsoft Visual Studio Code

#221

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.

expect for a feature that keeps a lot of people on other editors (recordable macros) https://github.com/Microsoft/vscode/issues/4490

I don’t use macros but it looks like I should tbh

Re: The Rise of Microsoft Visual Studio Code

#222

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…

> fantastic demonstration of why i exclusively use git from a command prompt

What's described in that github issue happened to me as well the first time I used git via Visual Studio. I normally don't do that, but something told me to make a zip of everything before using git in VS. So that saved me big time.

Why in the world are the deletions not pointed to the Recycle Bin??? That's what it's there for.

Re: The Rise of Microsoft Visual Studio Code

#223

Earlier quoted context omitted.

Which is weird because with all of its inconsistencies, git must have been designed with the idea that someone would build a sensible shell over top of it. I can't imagine Linus expected people to interact directly with git when he built it.

this is precisely the case: http://www.gelato.unsw.edu.au/archives/git/0504/0873.html

OT: that's a blast from the past - http://www.gelato.unsw.edu.au/

Re: The Rise of Microsoft Visual Studio Code

#224

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…

I do command line git as well because I am bouncing between IDEs and dont want to learn the differences in little features of each IDEs source control ui.

Re: The Rise of Microsoft Visual Studio Code

#225
post #88

Earlier quoted context omitted.

Not sure why you're downvoted. This is a concern. In my company, I downloaded VS Code to use it with F# for a toy project. But when I saw you cannot disable all data collection, I pretty much uninstalled it. Most likely there is no IP risk, but I did not want to go through the trouble of finding out precisely what data is collected, and/or cross check with our legal department. Plenty of people at the company do use…

I work on VS Code. You can disable VS Code telemetry and even disable all built-in online services if you like. This is documented on the website [1] However VS Code cannot block the extensions that you install from collecting their own telemetry. Even if use a version of VS Code built from source, an extension that you install could still collect telemetry of its own. Same applies to most software that allows third…

It would be nicer if they made it clearer when they inform you during the installation. All I saw was that they collect, and I can turn the setting off, but it wouldn't turn off all collections.

Anyway, thanks for the info.

Re: The Rise of Microsoft Visual Studio Code

#226
post #26

Earlier quoted context omitted.

There’s a jetbrains (IntelliJ) flavored ide for basically everything - even c#! I prefer Rider for doing c# in Unity3D over VS or VSCode because it seems muc more performant and the vim plug-in is way better

VS Code has something that JetBrains IDEs cannot match: Price. For startups in developing countries $200 per seat is a lot of money... VS Code or Atom look amazing in comparison for $0

You should talk to Jetbrains if you are a startup. They have discounts and such.

Having good tools in a fast paced environment is the key to Keep things focused on the product. I’d argue it’s more critical in a startup than else where for that reason

Re: The Rise of Microsoft Visual Studio Code

#227

Earlier quoted context omitted.

Has anybody written a Notepad++ to VS Code command translation guide? I use Notepad++ for all sorts of text related things (cutting, sorting, making 100s of julennne phrases) but not as an editor. If there was a cheat sheet of VS shortcuts I could ditch Notepad++ completely.

VS Code has a printable cheatsheet of keyboard shortcuts that it prompts you to view when you first open the editor.

Also available here:

https://code.visualstudio.com/docs/getstarted/tips-and-trick...

I, too, am making the Notepad++ -> vscode move.

Re: The Rise of Microsoft Visual Studio Code

#228
post #131

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…

P.S. VSCode has multi-cursor as well: https://code.visualstudio.com/docs/getstarted/tips-and-trick...

and emacs of course. https://youtu.be/jNa3axo40qM

Re: The Rise of Microsoft Visual Studio Code

#230
"Do Emacs and Vim users have some other characteristic that makes them more likely to succeed during interviews? Perhaps they tend to be more willing to invest time and effort customizing a complex editor in the short-term in order to get returns from a more powerful tool in the long-term?"

One thing I noticed on Lobste.rs is that a lot of them like the old school editors. That's normal. What was more interesting was that they were constantly sharing and discussing their customizations that made them more productive. Kept making me want to have another go at those editors. I didn't since I came from Windows with big, full-featured editors that could do everything (or Notepad++ or Notepad). Still, I keep reading those comments since there's always new and interesting things people are coming up with.

In other words, I think the author is onto something worth further investigation and comparisons. Especially comparing VS Code programming to experienced folks using highly-customized, full-featured setups in the other stuff. I bet the results would be more interesting than a random person tried using Emacs or whatever.

Post reply on HN