3 ms·
The controversy may have died down, but the impact on code written would have been permanent. There's a lot of value to there being "one way to do things", eve
by gridlockd 7y ago
The controversy may have died down, but the impact on code written would have been permanent.
There's a lot of value to there being "one way to do things", even when it's not the best way from any particular point of view.
Go holds this principle higher than most other languages and I think that should be either embraced, or one should look elsewhere - and I'm saying that as someone who "looked elsewhere".
- bmurphy1976 7y agoI think you make a reasonable point that is worthy of discussion. Unfortunately there's a group of people on this thread that are downvoting comments such as yours instead of discussing them. I'd like to see reasoned responses to your comment, i.e. tell us why you are wrong instead of the downvote brigading.
- didibus 7y agoAgreed, no one is forced to use Go. I think it is refreshing to see a language like Go. You don't want all languages to asymptotically approach each other in features. We need diversity in our languages, that way you have flavors to choose from.
- erik_seaberg 7y ago> no one is forced to use Go. I suspect some people are. Languages have network effects, which get stronger when FFI is uncommon. My team and codebase mostly keep me on Java even though I find Kotlin clearer in every way and I'd love to get better with Scala and Haskell. If for some reason my team switched to something like Go or VB I'd have to find another job or else put up with it.
- pjmlp 7y agoJust wait until management comes around with idea to write Docker or K8s plugins. Using a programming language is not always an option.
- ngrilly 7y agoWhere did you look?