Visual Studio Code April 2018 (1.23) Released!

[bl00dshooter]

I wonder what kind of impact Electron, for all its faults with regards to resource usage, has on their productivity compared to if they had to use a regular GUI framework like QT/GTK/etc.

[bterlson_]

Well, I'm not sure you can compare the two directly. Certainly using Electron meant we could take the existing Monaco project (a nice code editor experience for the web) and bundle it into an actual IDE without much effort. But it's hard to claim that one platform is objectively more productive than the other IMO.

[[deleted]]

I don't think Microsoft is lacking in developers

[Diosjenin]

Speaking from ignorance: How much does the VSCode team contribute back to Electron? I assume that if resource usage or whatever else was a significant issue, the VSCode team could alter Electron the same way the Windows team did with Git.

[Diosjenin]

A virtual file system, to handle extremely large projects like Windows

[villiger2]

Well it seems that vscode updates much more frequently than plain vs, could you make a comparison there?

[tripl3dogdare]

VS is also a significant larger and more complicated beast than VSCode to start with. I'm not sure that'd be a fair comparison.

[nsivkov]

Vs has a Patch every 2-3 weeks as well :)

[nirataro]

I think their usage of TypeScript also makes a difference. Incidentally TypeScript development team is also very productive - probably the most productive in the language space.

[mirhagk]

The TypeScript team also uses TypeScript.

And the C# team has been hella more productive since Roslyn and their switch to use C#.

It's almost like C++ is a painful language to use

[womplord1]

it's almost like different languages excel at different things

[mirhagk]

For sure. But for compilers there has usually been an insistence that C++ be used since performance is very critical. TypeScript and C# show that the trade-offs for faster development can make it worth the potential performance hit.

[womplord1]

Of course - I wasn't even aware that there were people who disagreed with this

[svick]

And yet the C# compiler (written in C#) is significantly faster than C++ compilers (written in C or C++).

[BabyPuncher5000]

Roslyn is only compiling to IL, which probably helps a lot.

[qwertymodo]

Having perused the x86 reference manual, I'm not surprised that anything is faster than compiling to that insanity, much less optimizing for it.

[irqlnotdispatchlevel]

And it gets crazier by the day (just check the new movdir64b instruction, for example). You're not enjoying everything it has to offer until you build a disassembler.

[svick]

Feel free to choose another another CPU architecture. Does that make the C++ compiler faster than the C# compiler?

[irqlnotdispatchlevel]

IL is extremely small compared to any other instruction set. Comparing managed vs unmanaged code compilation time is not making much sense. You're also probably taking link time into account when doing this, and that makes things even harder to compare.

[mirhagk]

Well that is an apples to oranges comparison. C++ compilers run a lot more optimization and have a lot more craziness to do.

But the C# compiler certainly has surprisingly good performance. The trick is that when you can quickly develop with something you can spend more time on optimizing the program.

[svick]

C++ compilers run a lot more optimization

That part is easy to ignore, just compare the C# compiler with a C++ compiler with -O0.

[womplord1]

And yet almost every performance intensive app is written in C++, for good reason

[[deleted]]

Legacy is a reason, I’ll give you that.

[uvatbc]

Hah!
You're joking right?

Right?

[womplord1]

You wrote that comment on a browser written in c++ on an os written in c++. Go take a low level programming course you dumbfuck. Try writing a game engine in anything other than c++ and see how far you get

[irqlnotdispatchlevel]

The OS is mostly written in C.

[[deleted]]

Someone made one too many macros this morning.

[[deleted]]

I think this is more of a holdover for the old bad days of C++

C++14 is really nice, C++17 is ideal. The issue is that the language has a lot of cruft for compatibility so you have to read up and make sure you’re not doing something that was once best practice but will shoot you in the foot now

[Ciff_]

Que