Why is TypeScript's new compiler being developed in Go?

Go is efficient for creating native executables, making it suitable for the new TypeScript compiler.

What are the concerns about this decision?

Developers are worried about Microsoft's commitment to C# and .NET, given that they chose Go instead.

Who created TypeScript?

TypeScript was invented by Anders Hejlsberg, who also created C#.

Should C# developers learn new languages?

Yes, it's recommended to learn TypeScript and Go to stay updated with industry changes.

What are the implications of using Go for TypeScript's compiler?

It could lead to a shift in the TypeScript and web build tools ecosystem toward Go.

Is C# still relevant?

Yes, but there's uncertainty about its future direction within Microsoft.

How can .NET improve according to developers?

Developers want to see more focus on building tools and projects in .NET.

What was the community's reaction to using Go?

The reaction has been mixed, with frustration over the choice and uncertainty about the future.

Are there alternatives to Go and C# for building TypeScript tools?

Yes, developers have mentioned existing Rust transpilers for TypeScript as alternatives.

Microsoft Abandons C# and .NET !!!1!1

00:07:11

https://www.youtube.com/watch?v=RD421VBgEQk

Zusammenfassung

TLDRA Microsoft fejlesztői hír frissítésben bemutatják a gyorsabb TypeScript fordítót, amelyet Go nyelven fejlesztenek, nem pedig a .NET vagy C# nyelven. Ez a váltás vitát váltott ki a fejlesztői közösségben, különösen a TypeScript C#-hoz való kötődése miatt. A helyzet szélesebb körű aggodalmakat tükröz a Microsoft nyelvválasztásának irányával és a C# és .NET iránti elkötelezettségével kapcsolatban. A fejlesztőket arra bátorítják, hogy alkalmazkodjanak és tanuljanak új nyelveket, például a TypeScript-t és Go-t, miközben kérdőjelezik meg a C# jövőjét a Microsoft ökoszisztémában.

Mitbringsel

🚀 TypeScript's new compiler is being developed in Go for speed improvements.
🤔 The community is surprised by the use of Go instead of C# or .NET.
💡 TypeScript conversion to JavaScript is currently handled by a TypeScript-based compiler (TSC).
🔄 Microsoft aims for a native executable to enhance TypeScript performance.
😟 Concerns arise over Microsoft's commitment to C# and .NET with this direction.
👨‍💻 Developers need to adapt and learn TypeScript and Go.
📉 Mixed messages from Microsoft lead to uncertainty for C# developers.
🛠️ There are existing Rust transpilers for TypeScript to consider.
📅 The TypeScript and web build tools ecosystem may pivot toward Go.
🙏 Developers wish to see more projects developed in the .NET framework.

Zeitleiste

00:00:00 - 00:07:11
A Microsoft ma reggeli hírei között felfedeztük, hogy a TypeScript tízszer gyorsabb lett, mivel a Microsoft egy natív porton dolgozik. A TypeScript Compiler (TSC) jelenleg TypeScript-ben van írva, ami lassú, ezért a cél egy gyorsabb, natív megoldás bevezetése. Mivel a .NET nem volt megfelelő, a Microsoft a Go nyelvet választotta, ami meglepő, tekintve, hogy ők maguk a C#-t fejlesztik. A közösség reagálása vegyes, sokan aggodalmukat fejezik ki amiatt, hogy a cég nem a saját termékeit használja.

Mind Map

Video-Fragen und Antworten

Why is TypeScript's new compiler being developed in Go?
Go is efficient for creating native executables, making it suitable for the new TypeScript compiler.
What are the concerns about this decision?
Developers are worried about Microsoft's commitment to C# and .NET, given that they chose Go instead.
Who created TypeScript?
TypeScript was invented by Anders Hejlsberg, who also created C#.
Should C# developers learn new languages?
Yes, it's recommended to learn TypeScript and Go to stay updated with industry changes.
What are the implications of using Go for TypeScript's compiler?
It could lead to a shift in the TypeScript and web build tools ecosystem toward Go.
Is C# still relevant?
Yes, but there's uncertainty about its future direction within Microsoft.
How can .NET improve according to developers?
Developers want to see more focus on building tools and projects in .NET.
What was the community's reaction to using Go?
The reaction has been mixed, with frustration over the choice and uncertainty about the future.
Are there alternatives to Go and C# for building TypeScript tools?
Yes, developers have mentioned existing Rust transpilers for TypeScript as alternatives.

Weitere Video-Zusammenfassungen anzeigen

Erhalten Sie sofortigen Zugang zu kostenlosen YouTube-Videozusammenfassungen, die von AI unterstützt werden!

Untertitel

Automatisches Blättern:

00:00:00
Oh, yes! Let's look at some Microsoft developer news this morning. What have we got? A
00:00:05
TypeScript that's ten times faster, woohoo! Let's see how they've achieved it. Oh, yes,
00:00:11
okay. They've been working on a native port of TypeScript. Yes, let's go. Oh, yes, a new TSC. Oh,
00:00:17
you can build and run the Go code? No, no, no, no, this is incorrect. This should be .NET, not Go.
00:00:38
In all seriousness, let's actually take a look at what is happening.
00:00:41
We're going to delve into it. We have TypeScript files, TS files,
00:00:45
yes, but the browser uses JavaScript files, we know this. TypeScript itself, however,
00:00:54
is a project that doesn't just contain this beautiful language written by Microsoft's finest,
00:01:01
but also has what they call a compiler, known as the TypeScript Compiler, or TSC. Now,
00:01:09
I wouldn't call it a compiler, it's a transpiler because it converts TypeScript to JavaScript.
00:01:15
Currently, within the TypeScript project, this compiler is actually written in TypeScript itself,
00:01:25
which makes it quite slow. We all complain about how long it takes
00:01:30
for these projects to work. It's compiled by itself, it's a circular process. The
00:01:36
JavaScript runs on Node.js to actually turn your TypeScript files into JavaScript.
00:01:43
The goal is to upgrade this to something faster, native,
00:01:48
and not written in TypeScript or JavaScript itself, and certainly not running on Node.js.
00:01:55
Microsoft has an amazing programming language, you might have heard of it,
00:01:58
it's called C#. They also have a great runtime, it's called .NET. It compiles to native code as
00:02:03
well. But instead of C# and .NET, which would have been cool, they've just decided to use Go.
00:02:16
The response has been shocking, as usual. Here's the repo,
00:02:22
Microsoft TypeScript Go. Go being a Google programming language, obviously. Why not?
00:02:30
In typical fashion, we have a pivotal GitHub issue. We're going to give the community 500
00:02:41
words to justify a decision. Language choice is always a hot topic, says Ryan.
00:02:48
Basically, they need a native executable to be used as a compiler, and Go is very good
00:02:54
at this. .NET is not quite there yet. The AOT stuff isn't perfect. Bring back native .NET,
00:03:01
that was cool. .NET Native from UWP days, that was quality.
00:03:06
So, the choice of Go is quite surprising, given that Microsoft makes C#. This is
00:03:13
carnage. Neon Sunset says reflection is fully supported on Native OT. This is not helping
00:03:22
the allegations that Microsoft doesn't use their own products. This is carnage.
00:03:31
Who's going to refactor the code in a week? I haven't thrown my hat in the ring yet,
00:03:36
but I might. The agony that's going on here is justified, I think. Nick here goes,
00:03:50
"I won't be making C# videos any longer." Very funny. But why are people so upset about this?
00:03:56
Well, last year, Microsoft decided to put some job ads out to work on some
00:04:00
core stuff for Microsoft 365. Instead of looking for C# and .NET developers,
00:04:07
they decided to look for Rust developers. This caused a big stink.
00:04:13
But this is just Microsoft 365, so developers don't particularly care about it. This is just
00:04:19
a sub-team. However, TypeScript was invented by the guy who invented C#,
00:04:31
Anders. If this guy, who invented C#, is not going to invest time in making C# and .NET
00:04:42
good enough to be used as a scripting language transpiler, which is what TSC is, is it all over?
00:04:56
The somewhat good news is that the C# and .NET guys are not the only ones
00:05:00
annoyed by this, so are the Rust guys. There are already Rust transpilers for TypeScript if
00:05:23
we needed something to speed up web compilation. If they wanted to use Zig, this exists as well.
00:05:47
The optics need serious improving. With all this mixed messaging, what should a C# developer
00:05:53
do? You should stick with C#, yes, and I keep talking about this on this channel,
00:06:03
but you should also learn TypeScript. For the love of God, please don't fall into
00:06:10
this belief that C# does everything on planet Earth. It can do many things, it can do desktop,
00:06:15
it can do mobile apps, it can do SPAs with Blazor, but give it a rest. Learn TypeScript.
00:06:23
You should also be dabbling in Go. If you're doing web services, Kubernetes is all written
00:06:29
in Go. The TypeScript compiler is about to be written in Go,
00:06:32
which means the entire ecosystem of TypeScript and web build tools will
00:06:37
end up in Go. If you're a low-level guy, you might want to have a look at Rust as well.
00:06:45
Is C# still going to be a thing going forward? The mixed messages from Microsoft really worry
00:06:52
me. Microsoft guys, I know some of you watch this channel. Please, we need a win here.
00:06:59
.NET needs a win. Build something in .NET for a change, please. I'm begging you.
00:07:05
It's all I ask. People are struggling out here. Alright, thanks for watching.