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

101–110 of 145 posts

Re: Visual Studio Code 1.7.1

#101

Post by mastazi »

erikbye wrote: post #72
elnado wrote: post #55

Earlier quoted context omitted.

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…

Sublime, people still use that over Atom? Do you see more people using VSCode than Atom, or Emacs? What about TextMate 2, no one? Which language do your backend guys use VSCode for?

I have used Atom for about one year and then went back to Sublime. I do mostly back-end web development, in various languages.

I believe Sublime is a superior product in terms of performance and stability.

Reasons for switching back:

1 - Atom has some long-standing bugs that compromise its usability (e.g. there is a bug where you basically can't scale down a window after it was maximised: https://github.com/atom/atom/issues/10720 )

2 - Atom is slower, you may think a fraction of a second when opening a file or doing a search should not make much of a difference but, when you are using an editor every day for many hours, it ends up affecting your productivity.

PS I liked VS Code but it's different enough from the other 2 editors that it would take time for me to become proficient with it. I especially liked VS Code's debugging features.

Re: Visual Studio Code 1.7.1

#102

Post by zumu »

Pigo wrote: post #32
zumu wrote: post #27

Earlier quoted context omitted.

I've been developing on a chrome book for the past year. I can confirm that vs code runs very smooth, while atom is finicky and just flat out dies on opening large folders/files.

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 to lock up for me. I was actually forced to switch from Atom to VSC, because I had a bad habit of accidentally clicking on `node_modules` in the file tree and crashing my session.

Re: Visual Studio Code 1.7.1

#103

Post by zumu »

pryelluw wrote: post #98
zumu wrote: post #27

Earlier quoted context omitted.

I've been developing on a chrome book for the past year. I can confirm that vs code runs very smooth, while atom is finicky and just flat out dies on opening large folders/files.

VSC runs on chromebook? I did not know that. Mind sharing about your experience?

I am actually running galliumOS--an ubuntu-based distro for chromebooks.

Re: Visual Studio Code 1.7.1

#104

Post by johnnyb9 »

blitzd wrote: post #46
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…

> The Microsoft brand has been completely reborn in the eyes of developers over the past few years. The lows of 2007-2010 seem a distant memory. Maybe in the eyes of some developers - for many of us who are still dependent on MS products that haven't been getting much attention (SQL Server and it's related BI tools), the lows are still getting lower. Sure, there's improvements in the overall functionality (with SQL 2…

Reminds me of the 5 year old bug to fix Intellisense completion mode in SSMS, finally fixed in 2016.

Re: Visual Studio Code 1.7.1

#105

Post by mattmanser »

harigov wrote: post #58
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…

I think the lock in using API or platform is no longer necessary. Their well-integrated services in terms of safety, security, ease of use and reliability will sell on their own. The most important computing battle is on the cloud - get developers to build their tools using MS technologies and then provide much better performance and integration on Azure. If open source implementation of .NET CLR is 10% slower than t…

But, speaking from experience and lots of recent discussion recently here, Azure doesn't have performance or ease of use.

The very people using Azure are the people MS are going out to burn with all this focus on the new stuff, the people invested in their stack are getting heavily burnt by churn and the substandard performance of .net core. One of the great things about C#/ASP.Net is that it was improving constantly, they've basically put that on hold for 2-4 years while they try and support linux. And for what? ASP.Net/C# was basically a much faster, better tooled, statically typed Rails.

There was a discussion here of what all the HN startups were using the free azure credits for and the consensus was basically "anything non-critical, log parsing, azure is terrible". One of the GCE guys replied to one of my comments about consistent latency of 3-5ms between website instances and SQL instances on azure with basically "ours is much better, 100ns latency, we're now beta-ing SQL Server". With .net core MS have basically opened up the C# space to be eaten by AWS + GCE.

And the recent terrible re-write of Azure web interface hasn't got anyone's hopes up of improvements any time soon.

Re: Visual Studio Code 1.7.1

#106

Post by will_hughes »

blitzd wrote: post #46
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…

> The Microsoft brand has been completely reborn in the eyes of developers over the past few years. The lows of 2007-2010 seem a distant memory. Maybe in the eyes of some developers - for many of us who are still dependent on MS products that haven't been getting much attention (SQL Server and it's related BI tools), the lows are still getting lower. Sure, there's improvements in the overall functionality (with SQL 2…

The Per-Core licensing cost for SQL Server and now Windows too is really a pain, and getting worse with more and more cores showing up in boxes.

We've got some servers that would be happy to putt along on 2-4 cores, but we're struggling to find anything less than 12 cores with our managed hosting provider - so we have to pay for the extra cores, even though we don't want to use them.

"Consolidate!" - sure, but we can only do that so much. Some stuff we have to deploy regionally for latency reasons, other stuff can't share hardware for PCI compliance reasons. We don't want to have production environments sharing with dev.

Re: Visual Studio Code 1.7.1

#107

Post by skilic »

pavlov wrote: post #19
jagermo wrote: post #2

Can I say that I really like the speed of these updates? The team Microsoft really seems to be invested in this free code editor. And a lot of the features are cool, however I really like: | Help > Keyboard Shortcuts Reference brings up a printable PDF reference sheet of VS Code command keyboard shortcuts. Keep this reference handy and you'll be a VS Code power user in no time.

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 wonder what I'd get from my Surface RT that I paid more than a pretty penny for a few years back. Would be nice to "trade-in" for a decent discount on a Surface Pro 3/4.

Re: Visual Studio Code 1.7.1

#110

Post by qarioz »

timdorr wrote: post #12
Pigo wrote: post #5

Electron is a great framework. I've used the same applications on several OS's, each seemed stable and fully functional.

I'm curious why Atom gets so much crap for being an Electron app, whereas VS Code is generally praised for it's speed. Are they doing something significantly different from each other?

One of the developers explain why it's faster than atom, basically the are using different threads for different things and many optimization on viewbox

https://vimeo.com/174657014

Post reply on HN