Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code 1.7.1

code.visualstudio.com

Post reply on HN
Print view View original

131–140 of 145 posts

Re: Visual Studio Code 1.7.1

#131

Post by petre »

erikbye wrote: post #130
petre wrote: post #124

Earlier quoted context omitted.

Yup, Sublime Text rules. I still use 2.0.1 at work (on a Mac) mainly for Perl and JavaScript. It always works, it's fast, doesn't ever crash. I didn't like VSCode that much (mainly have a problem with the toolbar on the right and don't want to learn new key bindings/menus etc). Also I don't use debuggers that much, so it's a useless addition to VSCode for me. Atom is a lot like Sublime in terms of usage, but it's pai…

Have you used TextMate 2? Possibly the editor with the best integration UI-wise, also, easily the most performant.

No, but if it's not open source and multi-platform (at least Linux and Mac) then I see no reason to switch. That's why I probably ignored it, in fact; also why I keep checking Atom out.

Re: Visual Studio Code 1.7.1

#132

Post by jhasse »

erikbye wrote: post #129
jhasse wrote: post #128

Earlier quoted context omitted.

> Not sure exactly how the Git integration is better? I can directly see which lines have changed in VS Code on the left site of a file. > VS also has multi-cursor support, if we are thinking of the same thing... editing more than one line simultaneously? You can add multiple cursors by Alt + Left mouse button in VS Code. This allows to even modify multiple words in one line simultaneously. > Besides, these two featu…

> I can directly see which lines have changed in VS Code on the left site of a file. VS has this too. Except, by default, it is on the right side of the editor. Uncommitted is in yellow. The white "marker" or hyphen, moves with the line number your cursor is on. Just like in VS Code. You can also see commits on each function and class, by author and date. You can right click each commit and view details for that comm…

> VS has this too. Except, by default, it is on the right side of the editor. Uncommitted is in yellow. The white "marker" or hyphen, moves with the line number your cursor is on. Just like in VS Code. > > You can also see commits on each function and class, by author and date.

Both not working for me. Are you sure that this also works with C++ code?

Re: Visual Studio Code 1.7.1

#133

Post by Pigo »

zumu wrote: post #102
Pigo wrote: post #32

Earlier quoted context omitted.

Kudos to another chromebook dev! Are you running Ubuntu in a Crouton, or another setup? I'm doing that and I run Atom without any complaints. It might just be the way I'm using it however.

I removed the write protection screw, upgraded my ssd, flashed on a new bios from https://mrchromebox.tech/ , and installed galliumOS--originally I used chrubuntu, then straight ubunutu. Everything works great. Even installed display link drivers, so I can dock to 2 monitors at work. Can you open arbitrarily large text files/directories in atom these days? Whenever, I open anything over a few thousand LOC atom seems…

I had someone on here mention the write protection screw removal method to me before, I just couldn't bring myself to do it on my Pixel 2. But I should try it, I'm glad to hear someone say it worked out great for them. I definitely want to still be able to boot into the normal Chrome OS because it's preferable to me when I'm not working.

I think I see what you're saying. Maybe it's because the pixel is actually a beast, I don't notice it as much. I have VS Code installed, maybe I should give it another shot. I'm probably just used to Atom, and the only time I really used VSC I was trying to work on one of our really large .NET solutions and it just started throwing hundreds of errors at me. I should try one of my MEAN apps in it.

Re: Visual Studio Code 1.7.1

#134

Post by erikbye »

jhasse wrote: post #132
erikbye wrote: post #129

Earlier quoted context omitted.

> I can directly see which lines have changed in VS Code on the left site of a file. VS has this too. Except, by default, it is on the right side of the editor. Uncommitted is in yellow. The white "marker" or hyphen, moves with the line number your cursor is on. Just like in VS Code. You can also see commits on each function and class, by author and date. You can right click each commit and view details for that comm…

> VS has this too. Except, by default, it is on the right side of the editor. Uncommitted is in yellow. The white "marker" or hyphen, moves with the line number your cursor is on. Just like in VS Code. > > You can also see commits on each function and class, by author and date. Both not working for me. Are you sure that this also works with C++ code?

Ok, so I tried it out.

You have the same Git stuff (color markers) on the sides of the editor for C++. I tried both the Community edition (2015) of VS and Enterprise (15, preview 5). But, the number of references, authors, etc, above functions and classes, seems limited to C#.

Re: Visual Studio Code 1.7.1

#135

Post by jhasse »

erikbye wrote: post #134
jhasse wrote: post #132

Earlier quoted context omitted.

> VS has this too. Except, by default, it is on the right side of the editor. Uncommitted is in yellow. The white "marker" or hyphen, moves with the line number your cursor is on. Just like in VS Code. > > You can also see commits on each function and class, by author and date. Both not working for me. Are you sure that this also works with C++ code?

Ok, so I tried it out. You have the same Git stuff (color markers) on the sides of the editor for C++. I tried both the Community edition (2015) of VS and Enterprise (15, preview 5). But, the number of references, authors, etc, above functions and classes, seems limited to C#.

Thanks :) Git markers are still not working here, don't know why. (Tried VS 2013 Community and 2015 Community)

Re: Visual Studio Code 1.7.1

#136

Post by at-fates-hands »

traskjd wrote: post #93
at-fates-hands wrote: post #84

Earlier quoted context omitted.

>> There's a lot of Javascript being written these days, and those lines of code will have to be maintained. Maintained and supported. How many JS libraries have developers jumped on, only to see them die a few years later? Backbone JS is the first that comes to mind. Everybody was using it, but since then, it's pretty much fallen by the wayside and there is still a ton of Backbone code out there that needs maintaini…

Is it dead? Last GH commit shows as 7 days ago? (genuine Q, wondering if I missed something). It may be less flavour of the month, but that seems par for the course with JS frameworks.

The last few commits appear more about cleaning up some of the documentation.

I guess on Jeremy Ashkenas twitter feed he called Backbone "finished" in terms of API and feature set after the 1.0 version. When you look at the contributions graph, its practically non-existent: https://github.com/jashkenas/backbone/graphs/contributors

Add in the Google trends graph compared to Angular and React: https://www.google.com/trends/explore?q=backbone%20js,angula...

Then when you look at the other libraries in the ecosystem, its like a ghost town.

backbone.forms - Open Issues: 172, Issues closed in 2016: 14, Last Release: Jan 21, 2016

backbone.localstorage - Open Issues: 45, Issues closed in 2016: 1, Last Release: Jan 22 2015

backbone.paginator - Open Issues: 20, Issues closed in 2016: 7+, Last Release: Feb 3 2016

backbone.validation -Open Issues: 79, Issues closed in 2016: 1, Last Release: May 8 2015

So not only is interest waning, the creator has called the library "finished" with not much more in terms of features coming and the ecosystem surrounding Backbone has all but dried up. I would be hard pressed to say it still has a bright future.

Re: Visual Studio Code 1.7.1

#137

Post by beagle3 »

wlk wrote: post #16

Is there a Debian/Ubuntu repository somewhere? They provide deb packages but I couldn't find the repo anywhere.

Ubuntu has 'umake ide' that installs or upgrades it directly from the MS download; no .deb yet AFAIK, though.

Re: Visual Studio Code 1.7.1

#138

Post by svieira »

Noseshine wrote: post #29
svieira wrote: post #26

Earlier quoted context omitted.

Typescript can actually use the types you provide in JSDoc[1] so you will see benefits simply by using VS Code in most cases. [1]: https://github.com/Microsoft/TypeScript/wiki/JSDoc-support-i...

That is interesting, I did not know that. Still, I don't want to use TypeScript for the reasons I wrote. I'm as minimalist as possible, and I don't want to use a language that changes my code to something else without any gain for me since I can write exactly what I want in ES 2015+ already. So it's just those types, and I could get them from "Flow" too and in that case keep my ES 2015+ code. Yes I know TypeScript is…

For what it's worth, that is slightly out of date - I have a code base that uses `@typedef` and TypeScript seems to pick it up without trouble.

Re: Visual Studio Code 1.7.1

#139

Post by dethswatch »

mattmanser wrote: post #42
pavlov wrote: post #19

Earlier quoted context omitted.

The team Microsoft really seems to be invested in this free code editor. It's great strategic marketing. Making Visual Studio Code costs a fraction of what Microsoft spent on the Surface RT marketing campaign (as an example), and the benefits to their image are much more powerful and long-lasting. The Microsoft brand has been completely reborn in the eyes of developers over the past few years. The lows of 2007-2010 s…

I don't get the end game though, what is the strategy? Ultimately, if you end up using Linux .net core + typescript, they seem to be killing off visual studio, IIS, Windows Server, etc. For what? Azure, glorified hosting that might end up a race to the bottom vs AWS & GCE? Selling SQL server licences? I just don't get the strategy. I'm genuinely asking, where is this actually taking them apart from burning a bunch of…

>Linux .net core + typescript, they seem to be killing off visual studio, IIS, Windows Server, etc.

Yup.

Kill it all- transition it to linux, put linux on azure, or build systems on azure profit / rent-seeking.

vsCode only exists because vstudio isn't multiplatform and never will be but they need multiplatform in order to make their slice of the cloud revenue larger.

Re: Visual Studio Code 1.7.1

#140

Post by dethswatch »

elnado wrote: post #55
mattmanser wrote: post #42

Earlier quoted context omitted.

I don't get the end game though, what is the strategy? Ultimately, if you end up using Linux .net core + typescript, they seem to be killing off visual studio, IIS, Windows Server, etc. For what? Azure, glorified hosting that might end up a race to the bottom vs AWS & GCE? Selling SQL server licences? I just don't get the strategy. I'm genuinely asking, where is this actually taking them apart from burning a bunch of…

In 2012ish as a freshman intern at Microsoft, I asked Will Kennedy (then CVP in Office) how did he feel about people pirating Office apps. He said that they would rather permit people to use illegal versions of Office than have them use their competitor's tools. Essentially he was saying Microsoft would rather people use their products free of charge rather than using other products as it promotes Microsoft image and…

> VSCode vs Visual studio are not competing efforts

Yet. Little by little, rather than invest in windows-only vstudio, they'll enhance code until it's building all the same stuff as studio and then they'll announce how amazing code is and stop talking about studio alltogether.

When MS ghosts a product, you know what its future is.

Post reply on HN