3 ms·

There are some absolutism in there which are not correct > Because of this, Go developers lean on the standard library more than many other communities and gen

by oaiey 4y ago

There are some absolutism in there which are not correct > Because of this, Go developers lean on the standard library more than many other communities and generally hold it in high regard. As a .NET developer I can just laugh here. Compared to JS and C/C++ this is accurate, but .NET, Java, PHP, Python this is the normal case. I would say the majority of platforms for application writing nowadays come like that. Which supports your argument, just that it is the norm already for a long time. To your generalized argument: i do not follow that. Yes, modern languages have the benefit of knowledge, but the old stacks are massively catching up. Package manager and libraries is a solved problem (except for C++). The most interesting aspect this should focus about are modern compilers. The ones like C# or TypeScript which expose their services (AST, type checking, etc) as language servers. Here old platforms (PHP, C++, Java, ...) have massive pains because rewriting the compiler is the opposite of fun and new languages could start like that (e.g. TypeScript).

idoubtit 4y ago
>> Because of this, Go developers lean on the standard library more than many other communities and generally hold it in high regard. > [...] Compared to JS and C/C++ this is accurate, but .NET, Java, PHP, Python this is the normal case. This is not my experience with Python, and even less for PHP. There are too many dark corners in the standard libraries of these languages to hold them in high respect. The standard library of PHP is an inconsistent mess, with many documentation holes. For instance, there are several ways to send HTTP queries using the PHP STL. Apart from very basic needs, the usual way is through the libCURL integrated into the STL. Unfortunately this library is just a port from C, far from a native syntax and barely documented. For any advanced usage, the developer has to read the C documentation, or switch to a non-standard library.

by oaiey 4y ago

idoubtit 4y ago

>> Because of this, Go developers lean on the standard library more than many other communities and generally hold it in high regard. > [...] Compared to JS and C/C++ this is accurate, but .NET, Java, PHP, Python this is the normal case. This is not my experience with Python, and even less for PHP. There are too many dark corners in the standard libraries of these languages to hold them in high respect. The standard library of PHP is an inconsistent mess, with many documentation holes. For instance, there are several ways to send HTTP queries using the PHP STL. Apart from very basic needs, the usual way is through the libCURL integrated into the STL. Unfortunately this library is just a port from C, far from a native syntax and barely documented. For any advanced usage, the developer has to read the C documentation, or switch to a non-standard library.