Hacker News Reader

Comment by golergka | Hacker News Reader

I think it's a matter of different goals. What you describe is pains of a very senior developer who has worked on a lot of very subtle bugs and never questioned their desire to deliver the best software possible.

Parent comment, however, talks about a situation where you have to hire dozens (if not hundreds) of $10/hour developers to ship software that is just good enough. I mean folks who may be great people and deserving overall respect, but who can't actually solve FizzBuzz. For such a situation, this:

> You may be pushing the problem onto ops people, other devs, or your customers

is quite alright and much more preferable than paying the market rate for developers who are actually capable of learning Rust.

View on HN

I'm not fond of this framing, which suggests that go is for bad programmers and rust is for good programmers. If Go makes it easier for bad programmers to write decent code, it also makes it easier for good programmers.

Good programmers aren't good because they're insanely clever and whip up brilliant combinations of abstractions. They're good because they write maintainable, understandable, simple, and effective code.

Or: they write code that understands the problem and solves it, not code that is stylish.

Go helps good devs do this.

> I'm not fond of this framing, which suggests that go is for bad programmers and rust is for good programmers.

Right, go is for inexperienced programmers.

> The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software.

Or so Rob Pike thinks. However, as I get more and more experienced, the shortcomings of go become too much to bear.

> go is for inexperienced programmers.

I am an extraordinarily experienced programmer, and I vastly prefer Go to Rust.

That doesn’t really have anything to do with a statement about Rob Pike’s design intent.

Before rust started being used in crypto, rust salaries weren't great - probably targeting people happy to get less money to use their favourite language

Reply on news.ycombinator.com