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

71–80 of 145 posts

Re: Visual Studio Code 1.7.1

#71

Post by WorldMaker »

Noseshine wrote: post #63
RyanCavanaugh wrote: post #44

Earlier quoted context omitted.

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

Right, most of the code changes Typescript performs are the equivalent of babel plugins: the closer you write to the target output version of the language the fewer changes there between the input/output. The further back compatible you try to target the more "polyfills" and reconfiguring Typescript needs to do to support the older versions of JS.

Most of Typescript's output changes when you are writing for the same version of JS that you are outputting are simply just removing the type hints from the final output.

That said, with allowJS "mixed" mode of Typescript now you can also try for a hybrid approach of JS and TS files in the same project and that hybrid approach gets more powerful and capable with each release. I think with some effort you can even get somewhat close enough to the point that you can have some Flow-like behavior by using JS for most files and .d.ts and .ts files for only the really type-dependent stuff.

Re: Visual Studio Code 1.7.1

#72

Post by erikbye »

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…

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?

Re: Visual Studio Code 1.7.1

#73

Post by erikbye »

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…

VSCode was not supposed to be a "website". VSCode is based on Monaco, the editor for Visual Studio Online.

https://github.com/Microsoft/monaco-editor

Re: Visual Studio Code 1.7.1

#74

Post by Noseshine »

WorldMaker wrote: post #71
Noseshine wrote: post #63

Earlier quoted context omitted.

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

Right, most of the code changes Typescript performs are the equivalent of babel plugins: the closer you write to the target output version of the language the fewer changes there between the input/output. The further back compatible you try to target the more "polyfills" and reconfiguring Typescript needs to do to support the older versions of JS. Most of Typescript's output changes when you are writing for the same…

I hope that is going to be a major use case for TS (i.e. directly intended and supported by the makers), i.e. (guaranteed) "just types".

Re: Visual Studio Code 1.7.1

#75

Post by erikbye »

satysin wrote: post #47

I enjoy working in C and C++ (on Windows) using Sublime Text however I am thinking of giving VSCode a proper try. I know many people use VSCode for web related development but MS seem quite serious about improving its support for C and C++. My question is does anyone here use VSCode for C and C++? What is your setup? task files, etc?

Why use VSCode over Visual Studio for C/C++ when your environment is Windows?

If you were on Linux or Mac I would recommend CLion or Qt Creator if you wanted a proper IDE. Or a heavily customized Emacs. But on Windows, I would recommend Visual Studio.

Re: Visual Studio Code 1.7.1

#76

Post by dvlsg »

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?

Not op, but I definitely preferred sublime to atom. I have since swapped entirely over to vscode, though, and I have been using it to write / compile / debug Node.js and c# / f# dotnetcore backend applications without many complaints.

Re: Visual Studio Code 1.7.1

#77

Post by ksubedi »

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?

VSCode actually uses natively compiled C# codebase for all the processing and only uses Electron for the "View" part. Atom does everything in javascript.

Re: Visual Studio Code 1.7.1

#78

Post by joaomoreno »

ksubedi wrote: post #77
timdorr wrote: 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?

VSCode actually uses natively compiled C# codebase for all the processing and only uses Electron for the "View" part. Atom does everything in javascript.

No.

TypeScript 73.9% JavaScript 21.6% CSS 3.4% Inno Setup 0.8% HTML 0.2% Shell 0.1%

Re: Visual Studio Code 1.7.1

#79

Post by oblio »

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…

IMO the long term strategy is Enterprise Javascript on one hand and Azure on the other one.

Azure is the obvious one.

Enterprise Javascript is basically:

1. Javascript is probably the most popular programming language at the moment (or at least top 3).

2. Since the creation of Node Javascript has entered the realm of back end services applications.

3. There's a lot of Javascript being written these days, and those lines of code will have to be maintained.

4. A large enterprise will need good tools from a solid, respected vendor, preferably one that has a great image in the developer community.

5. These tools, Open Source but beefed up with enterprise extensions, will cost $$$.

Microsoft was losing the back end completely, on the long term. It has already lost the frond end: web, Android, iOS. Now it's clawing its way back with its back end stacks or at least with tools meant for Open Source stacks.

Mark my words, after this huge flurry of development to mark Visual Studio Code as the leading cross platform "light IDE" (ahead of Sublime, Atom and maybe even ahead of some "heavy IDEs" such as Eclipse or Netbeans), Microsoft will release proprietary extensions, especially things targeting big enterprises.

In my eyes, this is a win-win situation. Microsoft still makes money, developers don't get EEEd like in the bad old 90s, etc.

Re: Visual Studio Code 1.7.1

#80

Post by wvenable »

Noseshine wrote: post #63
RyanCavanaugh wrote: post #44

Earlier quoted context omitted.

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

Also you could just add types to your JavaScript code with TypeScript and nothing else; the result of running through the TS compiler is just the same code with the types removed.
Post reply on HN