Go over Rust(hdost and DanielRosenwasser didn't respond to my comment but wrote boilerplate answer from previous discussion) #553
Replies: 2 comments
-
This was already discussed #411 i doubt this will get much further. |
Beta Was this translation helpful? Give feedback.
-
As @hdost has mentioned, we've discussed it quite a bit in that other thread. We provided our rationale and we feel we picked the language that would allow us to port most-effectively for this task. The TypeScript compilers (both the current stable one written in TypeScript, and this repository's written in Go) are both open source. If one feels very strongly about writing a TypeScript compiler in a different language, they are free to do so. We took ourselves up on that offer and have made a lot of progress. 😄 |
Beta Was this translation helpful? Give feedback.
-
I believe you should have written a less obfuscated formulation of the reason for picking Go that should have
looked something like..
Hey guys, we are picking Go not because of any technical reason but because we need to think less when porting and it is easier to write than Rust.
Which is a valid reason but you tried to make it seem like there is some technical justification.
Rust is simply a better language. It produces better software with less bugs that runs faster and it is easier to fix bugs and maintain because of the stronger type system. The only places where Go beats Rust are non technical.
If you know Rust well, there isn't a single reason to use Go.
I had to write this because i saw too many comments in that discussion which i couldn't reply to.
I feel like i am entitled to have this conversation because your discussion was sent to my by email by
golangweekly
.If you don't want to have this discussion then don't advertise it to people. If i have to read your stuff, i feel like i should be able to respond to it.
Beta Was this translation helpful? Give feedback.
All reactions