5 ms·
Whenever I see Go I think of this: https://news.ycombinator.com/item?id=16143918 https://news.ycombinator.com/item?id=16143918
by perth 5y ago
Whenever I see Go I think of this:
https://news.ycombinator.com/item?id=16143918 https://news.ycombinator.com/item?id=16143918
- _3u10 5y agoThis probably explains every google product after Gmail and google search since Go was invented.
- erik_seaberg 5y agoI didn't see Go used much at all within Google as of 2015; backends were pretty much half C++ and half Java with a bit of Python being deprecated over perf concerns. My team was all Java and had no plans for it.
- endymi0n 5y agoA great one, thanks for sharing. What‘s not to like about that approach? And if you think I‘m sarcastic, we might have a different belief system underneath: For me the irreplaceability of an engineer is not measured in the creation of complexity and the mastering of technical acuity in a language that‘s hard to grasp — but much more about the value and delight any piece of code brings to its users through simplicity. A language that is fast, easy and simple by default and doesn‘t get in the way of people trying to build something for the first time is a feature, not a bug.
- _3u10 5y agoGo has more line noise than Java combined with the expressiveness of COBOL
- joelbluminator 5y agolol
- perth 5y agoWhat about Python? It doesn't yell at you for having unused variables which is nice for actually developing the software. My main gripe with Go is it doesn't seem geared toward figuring out new things, or letting people hack and experiment during development.
- konart 5y agoI think you just don't have enough practice, to be honest. I came to Go from Ruby (and Python too, but I mostly used it before 2.7) and soon enough all my hacks and "let's try it this way" projects were in Go. >It doesn't yell at you for having unused variables which is nice for actually developing the software. No it is not. That was my first impression too but after a few weeks you understand that this was just a bad habit. Not a practice.
- perth 5y agoYeah I will admit I only tried Go for a few hours and hated it, so I don't have much experience with it.
- konart 5y agoI'd also like to point out that much depends on what kind of software you are developing. My main job for the past 5-6 years is system integration and I had a chance to compare Ruby and Go in this field. And this is definitely where I'd prefer Go to most other languages. You don't need clever code most of the time, you need really clear and safe code that will run for a decade after deployment.
- joelbluminator 5y agoRuby code can run for a decade after deployment as well...
- konart 5y agoAny code can. The question which language makes it easier to write such code (assuming it still should be readable and maintainable, even by the new employees, even if they are not familiar with all the tech behind it)
- aaronbrethorst 5y agoI’d rather work in a programming language that is easier to read than one that is easier to write.
- drvd 5y agoWhenever I see that quote being used to spurn Go I'm amazed of the seemingly large number of language researchers of a calibre of Wirth, de Moura or Wadler and the few actual used languages on the other hand.
- artursapek 5y agoMost tools we use in life are designed this way.
- brundolf 5y ago> So, the language that we give them has to be easy for them to understand and easy to adopt And what about making it easy for them not to make mistakes?
- pdpi 5y ago“Easy to understand” goes a very long way towards that.