Go 2, here we come

Re:Go 2, here we come by jpfed on Thursday November 29, 2018 @11:05PM (#18566575)

>I believe in the future all languages will fork into a simpler novice subset for general use and an expansive language for infrastructure. These will both be valid in the same parser, but the subset will be quarantined at the package management level.

I don't think we'll see this happen much for existing languages, but it could be a very interesting angle for a newly-designed language (or rather pair of languages).

[ Parent | on HN ]

Re:Go 2, here we come by Tarq0n on Friday November 30, 2018 @04:56AM (#18567977)

To some extent this is already happening in languages popular for machine learning. Libraries are written in C/C++ and the users just glue things together with very accessible API's.

[ Parent | on HN ]

Re:Go 2, here we come by erikpukinskis on Friday November 30, 2018 @02:49PM (#18572045)

It’s already happening. For example many people code in a subset of C++.

[ Parent | on HN ]