Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not your parent commenter but:

> You can frame that as an architectural concern...

"Go also offers excellent control of memory layout and allocation (both on an object and field level) without requiring that the entire codebase continually concern itself with memory management."

"The TypeScript compiler's move to Go was influenced by specific technical requirements, such as the need for structural compatibility with the existing JavaScript-based codebase, ease of memory management, and the ability to handle complex graph processing efficiently. "

If memory management and ability to handle complex graph processing efficiently isn't related to architecture to you I don't know what to tell you.

[0] https://github.com/microsoft/typescript-go/discussions/411

> The cult is in your imagination.

CTRL+F "rust" on the Go issue and see how many results you get. 31 for me and that's before expanding spam.





> If memory management and ability to handle complex graph processing efficiently isn't related to architecture to you I don't know what to tell you.

Rust can do complex graph processing, as well as efficient easy memory management, but it's going to do it in a different structure than a GCed lang would. Hence my statement that 1 to 1 translation was the primary factor.

> CTRL+F "rust" on the Go issue and see how many results you get.

Yes and so what? There's 35 for .NET or 74 for C#, yet you don't see people claiming the C# cult was harassing the TS team.


Obviously, C# is one of Microsoft's flagship language along with TypeScript.

So it's expected to be frequently mentioned there.


Sure, and Rust is the most used language for modern TS/JS tooling, outside of TS/JS. There would have been substantial ecosystem benefits had Rust been chosen.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: