Live data from Hacker News

Why I Don't Like Golang (2016)

teamten.com

151–160 of 237 posts

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

#151

Earlier quoted context omitted.

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. Perhap…

“I’ll pay $1000’s to get all setup and running with everything I need, including a bunch of stuff I don’t need, but not the last $90 for some productive software to make more money” Yeah ok.

[deleted]

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

#152

Earlier quoted context omitted.

“I’ll pay $1000’s to get all setup and running with everything I need, including a bunch of stuff I don’t need, but not the last $90 for some productive software to make more money” Yeah ok.

Some people really like these tools, and that is OK. But not everyone has the same workflow. I personally get a JetBrains license from the project I work on - but I refuse to use it, as I find their tools pedantic, slow, and eating my computer's resources. Ymmv.

Oh absolutely, if someone perfers emacs or vim, VS, VSCode, some JetBrains IDE. Punch cards.

Whatever makes them happy and productive, that's great. I've seen people use Vim and its crazy how productive some people are with it.

My point is complaining about the price of some software like it's blocking them from doing anything. They spend all this money on all this hardware and software, but when it comes to development, oh it costs too much I don't want to pay $90 for something to earn money...

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

#153

Earlier quoted context omitted.

Crud APIs...

What did you write CRUD APIs in before Go?

Rails. A bit of Django and Node. All 3 were better in my eyes but as I said in another comment I care very little about performance and concurrency so maybe I'm not Go's target audience.

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

#154

Earlier quoted context omitted.

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. Perhap…

“I’ll pay $1000’s to get all setup and running with everything I need, including a bunch of stuff I don’t need, but not the last $90 for some productive software to make more money” Yeah ok.

Is this a JetBrains commercial account ? Am I at fault for not liking their product that much, and thus not paying them their apparently deserved yearly subscription ?

This feels pretty weird to be faulted for using other companies' products. And no, switching to Jetbrains' doesn't make me more money. Could be the reverse from my past trials.

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

#155

Earlier quoted context omitted.

For comparison, in Go it would be: foo := func() string { if bar { return "this" } return "that" }()

Bit of an odd use of an anonymous function IMO. Normally I'd write that as: foo := "that" if bar { foo = "that" } Unless the assignment of "foo" is expensive, then you'd assign it in an else. If you really want to, you can do it in a single line too: foo := map[bool]string{true: "this", false: "that"}[bar]

These are rather nasty workarounds, to be honest. Instantiating a map out of the blue is clever, but not very readable (not to mention potential performance concerns eg. if it's code executing in a large loop), and something I'd definitely call out in code review. Note that computing "this" and "that" could by itself be costly, and one of these values is guaranteeed to get discarded.

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

#156
post #145
post #139

Earlier quoted context omitted.

I wonder how Turbo Pascal IDE managed to fit into 640 KB....

Because it wasn't based on bloatware liks Electron. And I guess the developers actually cared about performance because at that time they couldn't just assume that everyone has a powerful machine.

Electron !== IDE.

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

#157
post #138

Earlier quoted context omitted.

Sure, some people enjoy being stuck with workflows born out of phosphor terminals.

So why don't you program in VR then? Why not generate CI jobs from an ML model?

Graphical IDEs are good enough.

Xerox PARC already showed how.

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

#158

Why isn't Go good for large projects? Kubernetes is an example of a huge project built in Go

This is stock example. Anything else?

Excluding any lines that aren't Go code, and from projects that I can recall off the top of my head: Kubernetes = 3.87 million, Go = 1.75 million, CockroachDB = 1.65 million, TiDB = 725k, Consul = 375k, Nomad = 375k, InfluxDB = 375k, Mattermost = 370k, Vault = 345k, rkt = 320k, Terraform = 275k, Grafana = 265k, Ethereum = 245k, Gitea = 225k, Dgraph = 205k, MinIO = 200k, Rclone = 200k, etcd = 185k, Hugo = 120k, Prometheus = 120k, Syncthing = 110k, Traefik = 110k, Juju = 105k, Perkeep = 100k.

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

#159

Earlier quoted context omitted.

Some people really like these tools, and that is OK. But not everyone has the same workflow. I personally get a JetBrains license from the project I work on - but I refuse to use it, as I find their tools pedantic, slow, and eating my computer's resources. Ymmv.

Oh absolutely, if someone perfers emacs or vim, VS, VSCode, some JetBrains IDE. Punch cards. Whatever makes them happy and productive, that's great. I've seen people use Vim and its crazy how productive some people are with it. My point is complaining about the price of some software like it's blocking them from doing anything. They spend all this money on all this hardware and software, but when it comes to developm…

The initial [0] only mentioned the steep price in passing, and primarily lamented the inefficiency of the design. I'm not even sure from that phrasing that implying isn't a paying user, even if they seem to care about people who wouldn't fork the money for the editor.

[0] https://news.ycombinator.com/item?id=31734755

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

#160
post #146
post #138

Earlier quoted context omitted.

Sure, some people enjoy being stuck with workflows born out of phosphor terminals.

Do you have any other workflow that allows so much programmability and composability while being lightweight and cross-platform?

You mean the "cross platform" as long it is UNIX?
Post reply on HN