3 ms·
Yeah, this guy only had a superficial understanding of JS and Python--he had no idea how they worked under the hood, had no low level experience, no CS backgrou
by throwaway894345 5y ago
Yeah, this guy only had a superficial understanding of JS and Python--he had no idea how they worked under the hood, had no low level experience, no CS background, etc. We already sunk so much effort into the Python implementation that he couldn't get behind a rewrite in another language, and moreover I suspect he was intimidated by a "lower level" language (relative to Python) and figured it would take weeks or months to be productive.
In his defense, if you work in Python and JavaScript a lot, you get pretty jaded on tools and techniques that promise to be silver bullets and the idea that you could have a language that is orders of magnitude faster than Python, easy to learn, better package management and other tooling, and at least as maintainable just wasn't believable. Frankly, I think it would have been an easier sell if I lied and said that Go was only slightly better than Python.
- zozbot234 5y agoI guess this is the perfect use case for Nim. Same surface syntax as Python, so your senior dev would've had no issue surveying the code at least, even though contributing to it would've been more of a challenge (Nim compiles straight to C; it's not nearly as high level as either Go or Rust).
- throwaway894345 5y agoProbably, although I suspect Nim wouldn't have been a good choice because we were deploying on Lambda and we were using a lot of libraries for which there probably aren't good Nim alternatives (e.g., various cloud databases).