Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I Don't Like Golang (2016)

teamten.com

Post reply on HN
Print view View original

61–70 of 237 posts

Re: Why I Don't Like Golang (2016)

#61

Post by fomine3 »

smeagull wrote: post #35
sriram_malhar wrote: post #18

Earlier quoted context omitted.

Musicians and carpenters make far less than programmers, but they still buy their tools. Software people are too entitled. Even if you are not professional, you can still afford 54c a day ($200 a year). Even a programmer in India can.

I'm not paying that much for an editor that runs counter to my muscle memory, just so I can use a different programming language. If a language requires some IDE to make it usable, then I put it in the same camp as Java: Hope the competition are using it.

That's why I buy JetBrains all products pack. It supports many languages.

Re: Why I Don't Like Golang (2016)

#62

Post by makeitdouble »

sriram_malhar wrote: post #18
xigoi wrote: post #9

Earlier quoted context omitted.

Professional developers in the USA usually make 6 figures.

Musicians and carpenters make far less than programmers, but they still buy their tools. Software people are too entitled. Even if you are not professional, you can still afford 54c a day ($200 a year). Even a programmer in India can.

This is an undue attack. We buy our computers and screens and keyboards, most of us are on commercial OS, we pay for SaaS at a non trivial price, and most of us also use additional personal apps that aren't free (including password managers, mail clients etc.). Those are actual tools for the trade.

Arguing we should also buy every Jetbrains product is like arguing carpenters should buy line drawing AR goggles. Perhaps some will see the value in it, but it's far from an noncontroversial POV. If you feel a tool as as much downsides than upsides in your workflow, you don't use it, whatever its price is.

Re: Why I Don't Like Golang (2016)

#63

Post by srer »

voidfunc wrote: post #7
implying wrote: post #5

They'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…

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 then I wouldn't like what I was doing as much. Enjoying what I do, even if it may look slightly contrived to others, is important in me achieving results at work.

Re: Why I Don't Like Golang (2016)

#64

Post by fomine3 »

zenlot wrote: post #38
bmitc wrote: post #25

Earlier quoted context omitted.

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.

In most cases you cannot use personal licence on a company hardware. JetBrains also have separation between individual licences and organization licences.

JetBrains allows users to use personal license for work, but declines company to buy cheap personal license. I think this is good pricing. I agree that make company to buy license is annoying.

Re: Why I Don't Like Golang (2016)

#65

Post by digianarchist »

yashap wrote: post #55

Agreed 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.

Re: Why I Don't Like Golang (2016)

#67

Post by Barrin92 »

weatherlite wrote: post #29

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.

I don't think there is a tada moment but for me that's ironically enough what made the language deserve some hype. I like C, I never liked sophisticated languages that impose too strong of a style on the developer, a garbage collected, nice C with good performance and practical choices is pretty much what I wanted for a really long time.

Re: Why I Don't Like Golang (2016)

#68

Post by [deleted] »

yashap wrote: post #55

Agreed 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…

[deleted]

Re: Why I Don't Like Golang (2016)

#69

Post by [deleted] »

ngalaiko wrote: post #53

another person who can’t get over his java stockholm syndrome in three (!) years one particular thing that tells that is the attitude to interfaces: while in java (and most languages) interfaces are used to tell which contracts a class implements, in go it’s reversed. you must declare interfaces to _require_ certain contracts, for arguments in your functions for example: type interface Operator { Operate(int, int) in…

[deleted]
Post reply on HN