Live data from Hacker News

Visual Studio Code 1.7.1

code.visualstudio.com

61–70 of 145 posts

Re: Visual Studio Code 1.7.1

#61
post #59
post #46

Earlier quoted context omitted.

> 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…

What exactly open source technologies will give you feature parity and better support than microsoft's BI stack?

Would love an answer on this one. I implemented the MSFT BI stack into a product for no other reason than we were already using MSFT. However, each time I look at OSS BI stacks I feel like I'm losing out on something.

Re: Visual Studio Code 1.7.1

#62

I wish they left a flag for the people running their own npm mirror. Other than that, it's hard not to be impressed by how quickly they made another release. Congratulations!

It looks like setting an environment variable CH_ATA_ENABLE will turn it back on:

https://github.com/Microsoft/vscode/commit/b3c10273d7ba34086...

Re: Visual Studio Code 1.7.1

#63

Earlier quoted context omitted.

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…

> I don't want to use a language that changes my code to something else TypeScript doesn't change your code. If you're writing ES2015 code and targeting ES2015 emit, the output code is always exactly what you put in. There isn't any difference.

I guess I'll have to look into that again then.

Re: Visual Studio Code 1.7.1

#66
post #12
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?

Because Microsoft pays people to shill for them on media sources like Hackernews.

Re: Visual Studio Code 1.7.1

#67
post #12
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?

The text editor component (i.e. the part people are most likely referring to when discussing performance) is completely different between Atom and VS Code. No relation at all between the two codebases. VS Code's derives from Visual Studio Online.

Re: Visual Studio Code 1.7.1

#68
post #59
post #46

Earlier quoted context omitted.

> 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…

What exactly open source technologies will give you feature parity and better support than microsoft's BI stack?

There's nothing that's really comparable at the moment, so far as I know. It's not one of the pieces we've been able to replace.

Re: Visual Studio Code 1.7.1

#69
post #12

Earlier quoted context omitted.

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?

This comes up every time there's an Atom or VSCode post, but I've yet to see a good explanation of the architectural differences that contribute to the performance differences. Does anyone have the scoop?

All I know is that the typescript code used in VS code looks almost like C#. Interfaces etc. I had a good look at the github.

I can only assume that leads to a very low leakyness and low memory usage.

Re: Visual Studio Code 1.7.1

#70

I wish they left a flag for the people running their own npm mirror. Other than that, it's hard not to be impressed by how quickly they made another release. Congratulations!

If you are interested in getting the latest features, try VSCode Insider version[0].

[0]: https://code.visualstudio.com/insiders

Post reply on HN