3 ms·
Sure but it's worth noting that they went with the Rust implementation in the end even though it took the longest to write. Their reasons appear to have been t
by IshKebab 7y ago
Sure but it's worth noting that they went with the Rust implementation in the end even though it took the longest to write.
Their reasons appear to have been that Rust code has fewer bugs (who cares if you get your JS code done in an hour if you spend a week fixing trivial runtime bugs?), had better performance, and they didn't like Go's dependency system.
I definitely have noticed when writing Rust code I spend way more time getting it to compile, but I also have that "wait it worked first time? Impossible, I must have done something wrong" feeling waaaay more in Rust than I ever did with C++ or Typescript. I'm even starting to get used to it and think "sure it worked first time, it compiled after all!".
I wonder how their opinions on Go would change though, given that it now has arguably the best designed dependency system of any language.