Jump to page: 1 2
Thread overview
TypeScript is being ported to Go | interview with Anders Hejlsberg
Mar 12
Sergey
Mar 15
monkyyy
Mar 15
Sergey
Mar 15
Sergey
March 12

Interesting and a surprising technical interview.

https://www.youtube.com/watch?v=10qowKUW82U

Especially the part from here https://youtu.be/10qowKUW82U?t=2691 is interesting, at least for me.

Just thinking out loud, maybe somebody with connections to MS should try to get him to be a keynote speaker at dconf, and have him rant for an hour.

March 12

On Wednesday, 12 March 2025 at 13:01:59 UTC, Robert Schadek wrote:

>

Interesting and a surprising technical interview.

Already discussed ono Discord:
Interesting - D fits everywhere except "We need concurrency and we need shared memory concurrency" - I mean in Go it is better..
https://www.youtube.com/watch?v=10qowKUW82U&t=990s

Oh and "we also need a great tooling" maybe not the best for D.. idk how good is support of vscode for Go but I assume it should be good

March 14

On Wednesday, 12 March 2025 at 13:05:05 UTC, Sergey wrote:

>

Oh and "we also need a great tooling" maybe not the best for D.. idk how good is support of vscode for Go but I assume it should be good

My interest was not so much about them using go instead of D, but more about
them moving into a compiler server architecture. Aka. not recompiling their std.stdio on every compile.

March 14

On Friday, 14 March 2025 at 15:04:15 UTC, Robert Schadek wrote:

>

On Wednesday, 12 March 2025 at 13:05:05 UTC, Sergey wrote:

>

Oh and "we also need a great tooling" maybe not the best for D.. idk how good is support of vscode for Go but I assume it should be good

My interest was not so much about them using go instead of D, but more about
them moving into a compiler server architecture. Aka. not recompiling their std.stdio on every compile.

What I found interesting was the semi-machine translation; and that if one looks at the github ticket with the discussion, the post-port code looks so similar to the pre-port code. So vindicating the choice of Go as the target.

Also the shear degree of whining on the ticket from folks who wanted it ported to C# instead, "because"...

March 15

On Wednesday, 12 March 2025 at 13:05:05 UTC, Sergey wrote:

>

On Wednesday, 12 March 2025 at 13:01:59 UTC, Robert Schadek wrote:

>

Interesting and a surprising technical interview.

Already discussed ono Discord:
Interesting - D fits everywhere except "We need concurrency and we need shared memory concurrency" - I mean in Go it is better..
https://www.youtube.com/watch?v=10qowKUW82U&t=990s

Oh and "we also need a great tooling" maybe not the best for D.. idk how good is support of vscode for Go but I assume it should be good

VSCode support for Go is first class, because it was started by Microsoft themselves, and later given to the Go team at Google.

https://code.visualstudio.com/blogs/2020/06/09/go-extension

Microsoft also has their own Go distribution, and developer support team,

https://devblogs.microsoft.com/go/

March 15

On Friday, 14 March 2025 at 16:47:35 UTC, Derek Fawcus wrote:

>

On Friday, 14 March 2025 at 15:04:15 UTC, Robert Schadek wrote:

>

On Wednesday, 12 March 2025 at 13:05:05 UTC, Sergey wrote:

>

Oh and "we also need a great tooling" maybe not the best for D.. idk how good is support of vscode for Go but I assume it should be good

My interest was not so much about them using go instead of D, but more about
them moving into a compiler server architecture. Aka. not recompiling their std.stdio on every compile.

What I found interesting was the semi-machine translation; and that if one looks at the github ticket with the discussion, the post-port code looks so similar to the pre-port code. So vindicating the choice of Go as the target.

Also the shear degree of whining on the ticket from folks who wanted it ported to C# instead, "because"...

As one of those whining folks, imagine having Walter after all these years, suggesting that his next side project is going to be in Zig/Rust instead of D.

That is why those of us that like C#, and experience the adoption hurdles outside Windows still being a big problem, see having the C# original architect suggesting something else, that also happens to contradict .NET team marketing efforts.

Having such a key figure in the programming world adopting Go, for what is one of the most used frontend toolchains, will only solidity even further Go's relevance in the industry, beyond Docker and Kubernetes ecosystem.

Thus making .NET team developer advocacy efforts even harder.

March 15

On Saturday, 15 March 2025 at 08:22:38 UTC, Paulo Pinto wrote:

>

As one of those whining folks, imagine having Walter after all these years, suggesting that his next side project is going to be in Zig/Rust instead of D.

contradict .NET team marketing efforts.

Thus making .NET team developer advocacy efforts even harder.

Marketers being dishonest makes their jobs harder not the honest people being honest.

Walter should make a project in zig

March 15

On Saturday, 15 March 2025 at 08:22:38 UTC, Paulo Pinto wrote:

>

On Friday, 14 March 2025 at 16:47:35 UTC, Derek Fawcus wrote:
Thus making .NET team developer advocacy efforts even harder.

I think some of his points were relevant.. that their initial code was not really OOP and that syntax of TS is closer to Go, than to C#

Moreover Microsoft internally and officially is using plenty of languages.. a lot of repos are in C/C++/C#/Go/Java/TS/JS/PHP/Rust/R .. based on their official Github

And I don't know why this should be different for other core (closed sourced) projects.
It is a business with hundreds of thousands engineers and they are choosing the best tools to solve their tasks.

March 15

On Saturday, 15 March 2025 at 10:03:09 UTC, Sergey wrote:

>

On Saturday, 15 March 2025 at 08:22:38 UTC, Paulo Pinto wrote:

>

On Friday, 14 March 2025 at 16:47:35 UTC, Derek Fawcus wrote:
Thus making .NET team developer advocacy efforts even harder.

I think some of his points were relevant.. that their initial code was not really OOP and that syntax of TS is closer to Go, than to C#

Moreover Microsoft internally and officially is using plenty of languages.. a lot of repos are in C/C++/C#/Go/Java/TS/JS/PHP/Rust/R .. based on their official Github

And I don't know why this should be different for other core (closed sourced) projects.
It is a business with hundreds of thousands engineers and they are choosing the best tools to solve their tasks.

The difference is that this is not a random set of Microsoft employees, without a compiler well known industry background in one of their key assets.

However this is my last reply on the matter, we don't need to pollute D forums with this discussion any further, I was clarifying where the whinnying comes from.

March 15

On Saturday, 15 March 2025 at 10:31:07 UTC, Paulo Pinto wrote:

>

However this is my last reply on the matter, we don't need to pollute D forums with this discussion any further, I was clarifying where the whinnying comes from.

I agree

And wanted to say that I think that Robert’s idea to invite him to Dconf is amazing

I just afraid it will be a bit hard to do

« First   ‹ Prev
1 2