News for hackers. Stuff that matters.

A comment on Go performance from version 1.2 to 1.18. Parent comment

Re:Go performance from version 1.2 to 1.18 by lamontcg on Friday February 04, 2022 @01:15AM (#30203461)
> almost all users (me/GoAWK included) want performance and don't care nearly as much about simplicity under the hood.

that works up until you're at scale and the complexity of the implementation causes hard to understand edge conditions and just bugs from the complexity being beyond what the developers are able to handle.

[ Parent | on HN ]
Re:Go performance from version 1.2 to 1.18 by epolanski on Friday February 04, 2022 @06:40AM (#30205539)
Exactly, at some point code is such a mess that further optimization and features are harder to get merged. And the smaller the number of contributors the bigger the problem gets, till the main maintainer calls it quits and there's need for a completely new library.
[ Parent | on HN ]
Re:Go performance from version 1.2 to 1.18 by kaba0 on Friday February 04, 2022 @03:47PM (#30212950)
Is it also true when even the essential complexity of the project is quite demanding? Like runtimes, especially with JIT compilers are not easy to begin with.
[ Parent | on HN ]
Re:Go performance from version 1.2 to 1.18 by lamontcg on Friday February 04, 2022 @04:17PM (#30213361)
It is even more important then.
[ Parent | on HN ]