3 ms·
> Software has increased complexity due to Go's Simplicity. Which way are you meaning this. The way I read it was that because GO was simple, we were able to b
by mbrumlow 7y ago
> Software has increased complexity due to Go's Simplicity.
Which way are you meaning this. The way I read it was that because GO was simple, we were able to build more complex systems. But you seemed to indicate that was a bad thing?
Yes making complex that can be made simple is the way you want to do things, but some things simply are not simple, and thus require complex software.
- pjmlp 7y agoFor example check Kubernetes talk from FOSDEM.
- ikiris 7y agoNo, that the simplicity of the language forces complexity in the code written in it.
- mbrumlow 7y agoI have thought about this for about a day, and I can't agree with you. Every time I have seen complex GO code and investigated how it got that way it was simply the result of one of the following. 1) Writing GO code before fully understanding the language. 2) Trying to write GO code like it was some other language. I have seen some crazy complex GO in my days, and after spending hours and hours of trying to figure out what the code was doing -- I have always been able to simplify the program to a nice concise bit of code -- and I can assure you there are much better programmers out there than me. Often the complexity is people trying to implement generics in some crazy round about way, or have prioritized dependency injection, or code coverage test to a extreme. My favorite example of this is https://github.com/rdadbhawala/dutdip https://github.com/rdadbhawala/dutdip -- and here is a good talk on it https://www.youtube.com/watch?v=HBLJV0cPRBM https://www.youtube.com/watch?v=HBLJV0cPRBM The code base that implemented this in production is an amazing mess, I can assure you of that.