Go 2, here we come

Re:Go 2, here we come by johncolanduoni on Friday November 30, 2018 @12:19AM (#18566908)

To be fair, all of the aspects of the language itself you mentioned apply to JavaScript (save perhaps differences in how literally it takes `int`, etc. being objects vs. JavaScript's unboxed `number`, etc.). I suspect most of the difference is that one has had three of the largest corporations in the country competing to have the fastest implementation, in some cases for decades, and the other hasn't.

[ Parent | on HN ]

Re:Go 2, here we come by zbentley on Friday November 30, 2018 @08:23AM (#18568853)

I think a bigger reason is that Python prioritizes simplicity of internal implementation.

To be sure, the internal implementation of CPython (the only one I'm familiar with) is complicated as hell. But it's a whole lot simpler than any fast JavaScript runtime I've ever used. I think that's the result of a conscious choice by the maintainers/BDFL/community in Python, not a side effect of it having less funding (assuming that's the case).

[ Parent | on HN ]

Re:Go 2, here we come by gameswithgo on Friday November 30, 2018 @12:50PM (#18570862)

The primary difference is Javascript has serious JIT's as the normal case of running Javascript while Python is normally interpreted.

[ Parent | on HN ]