3 ms·
And the "I now have to evaluate thousands of libraries instead of 10 well established framework" tax? I've seen plenty of bad go libraries. For example their a
by LtWorf 2y ago
And the "I now have to evaluate thousands of libraries instead of 10 well established framework" tax?
I've seen plenty of bad go libraries. For example their authors will be unaware of isatty() so they will output control codes when piped.
If you factor in the time to find a competently written library (and quite possibly write one yourself) it starts to be less convenient.