As a new Go user I seriously don't get the hype. It feels like C with some (not many) niceties thrown on top, that's not what we expect from high level languages. I am still waiting for the tada moment, hope it comes.
[deleted]
Why I Don't Like Golang (2016)
71–80 of 237 posts
Re: Why I Don't Like Golang (2016)
#72Title needs 2016
[deleted]
Re: Why I Don't Like Golang (2016)
#73> Go doesn’t have exceptions. It uses multiple return values to return errors. It’s far too easy to forget to check errors... Yes, because it is easy and predictable to track exceptions in nested try catches and hidden control flow.
[deleted]
Re: Why I Don't Like Golang (2016)
#742016. Generics have been added.
[deleted]
Re: Why I Don't Like Golang (2016)
#75I'm still baffled by their decision around date formatting. https://www.godateformat.com/
I wrote https://golangti.me because I never remember _any_ of the formatting types (besides Excel (which isn't as extensive)—d, dd, ddd, dddd, m, mm, mmm, mmmm, mmmmm...).
Re: Why I Don't Like Golang (2016)
#76Earlier quoted context omitted.
When developers who usually make 6 figures of money complain about $90/yr IDE price I just cannot help laugh. Actually it's even better... the price elevators down from $90 -> year2 90 - 20% -> year3 90 - 40%. Over three years that's like $150-$200 total and it will save you so many headaches. But that's a steep price? Are you kidding? Why do developers hate tools that cost money when they save them time and allow th…
Pretty simple for me: I like working with Free and Open software much more than proprietary software. I think it's important for society, and I have more fun that way too! Also the payoff for me has been very good, I can learn emacs once and enjoy using it for the rest of my life for all significant written language tasks on a computer. Perhaps I could be a little more efficient if I were using a jetbrains IDE, but t…
Most of JetBrains platform is open source (Apache license). Only the language plugin is proprietary.
It's not perfect but better than your typical closed source software.
Re: Why I Don't Like Golang (2016)
#77Earlier quoted context omitted.
When developers who usually make 6 figures of money complain about $90/yr IDE price I just cannot help laugh. Actually it's even better... the price elevators down from $90 -> year2 90 - 20% -> year3 90 - 40%. Over three years that's like $150-$200 total and it will save you so many headaches. But that's a steep price? Are you kidding? Why do developers hate tools that cost money when they save them time and allow th…
What's even worse is getting companies to pay for this stuff. Getting a company to buy software to help you do your job is like pulling teeth.
any company will let you expense a few hundred dollars for a tool you use literally every day many hours a day. if you’re having trouble they are not good to work for or you’re asking the wrong way
Re: Why I Don't Like Golang (2016)
#78They've fixed the import / modules situation to a point where it's usable and much improved, and generics have been added. However, the issue this brings up about structs / types not explicitly declaring which interfaces they implement is a real and unaddressed problem, especially in large codebases. The only tool that I'm aware of that finds implementations is GoLand, at steep JetBrains prices. Figuring out what typ…
When developers who usually make 6 figures of money complain about $90/yr IDE price I just cannot help laugh. Actually it's even better... the price elevators down from $90 -> year2 90 - 20% -> year3 90 - 40%. Over three years that's like $150-$200 total and it will save you so many headaches. But that's a steep price? Are you kidding? Why do developers hate tools that cost money when they save them time and allow th…
Sorry, no. I have JetBrains and have since stopped using it for go development. It's too slow, too buggy, and lacks the ecosystem that VS code has. I still use it for Java because the rest are even worse
A language that depends too much on IDE integration for usability is a real problem, because now you have tool fragmentation as everyone goes different routes with varying levels of success to fix the deficiencies in your language. In the end you end up rolling your own tools as I have done, which is the absolute WORST of all worlds.
Go was supposed to be simple, but all it succeeded in doing is shifting the complexity elsewhere and calling mission accomplished. When you're designing a language, it's VERY important to understand the difference between the emergent complexity of the domain, and the inherent complexity of your design. The latter can be fixed, the former can only be managed - in ways that are already well researched (or just swept under the rug, as go has done).
Too much magic and too much "clever" re-purposing of existing paradigms (file names, capitalization, implicit contracts, etc) makes for an infuriatingly bad design.
Re: Why I Don't Like Golang (2016)
#79Agreed with the article, though obviously it’s a bit dated (especially around generics and package management). My take is that Go is basically the new Java, with fewer abstractions and faster compilation. Although, the pre-Java 8 Java, before Java started to get a bit functional. Like Java it’s a practical, imperative, statically typed, garbage collected language with very good performance. Also like (pre-Java 8) Ja…
Surprised you compare it to pre-Java 8 considering functions have first class support in go.
First class functions are a lot less interesting without functional data structures, with methods like map, filter, reduce, etc. These were added in Java 8, but Go has always been against them. This may change with generics, people can certainly write their own now, but I’m on the fence about whether they’ll catch on. I think they still won’t be overly nice to use in Go because:
- Go’s lambdas are extremely verbose. “Concise but clear” is a big part of what people live about functional data structures, Go won’t have the concise part
- Go will still have almost no support for immutability, which works beautifully with functional data structures
Code like this is nice to write:
users.map((user) => user.id)
While code like this isn’t:
users.map(func (user User) string { return user.id })
Re: Why I Don't Like Golang (2016)
#80Earlier quoted context omitted.
When developers who usually make 6 figures of money complain about $90/yr IDE price I just cannot help laugh. Actually it's even better... the price elevators down from $90 -> year2 90 - 20% -> year3 90 - 40%. Over three years that's like $150-$200 total and it will save you so many headaches. But that's a steep price? Are you kidding? Why do developers hate tools that cost money when they save them time and allow th…
I'm shocked at how often I see software engineers not paying for Sublime Text. These are people who get paid to write software not paying for software.
The use to pirate stuff all the time. Now it's actually more convenient for me to buy it.
But the philosophy I always had was that as long as there were enough people like you paying for software, I wouldn't have to.