My thoughts on Building Go-Gin: Simple over Easy: Building Go-Gin: Simple over Easy
Commentary
- Manu Martínez-Almeida Blog: Building Go-Gin: Simple over Easy
- Ok this is really good adivce. Building things which are simple over easy. There is a subtle difference between simple and easy. Something is simple to understand like http semantics, working with apis on postman feels easy, and python is easy to learn, but golang is a simple language to understand. There is a difference, yet very fine line is blurred for most of us.
- When I say easy, I mean the effort required to do something. Python looks easy on the outside, but when dealing with intricate dict mutation and internals, the easiness is no longer the ground. Its no longer simple, it was never simple, it made it look easy. Not saying Python is a bad language, but its not something you want if you are looking for lower abstraction.
- When I say simple, it means its requires very little or almost no cognition or effort to understand something or do it. When I look at a Golang codebase, it is not easy to understand it, there is a lot of code, but its simple. There is a difference. The size of things matter yes, but when everything is dead simple, it sometimes or most often is verbose. More verbosity doesn’t necessarily mean simple. Java is another example when I hear the word verbose. But what I am saying it simple is intuitive. Easy is a effort thing.