To apply for this position you require 12 years of Senior Experience in Go and Cobol.
Go: Ten years and climbing
141–150 of 193 posts
Re: Go: Ten years and climbing
#142Earlier quoted context omitted.
> an army of "toddler" developers can overthrow a single hero in terms of productivity Depends on what you mean by toddler. Golang devs imo are not toddlers. The point seemed to be that golang devs could just learn to write C, which is valid. So could Rust developers. But if that was the goal, you'd think both groups would only be using C. When I think of "toddler" developers, I think of interns being hired into a co…
And that disaster situation is going to happen regardless of what language they happen to be working in.
For sure. The problems happen when insufficient experience, knowledge, and leadership is combined with anything.
With enough fuel, fire, and gained wisdom, anything is achievable.
But, 10 kids playing with building blocks can't easily build an automobile, whereas one smart, dedicated engineer with a lot of metal, some tires, and better tools could pull it off. So, tools and resources matter, too.
Re: Go: Ten years and climbing
#143No other social or professional setting tolerates this kind of brazen self importance and posturing seen here without mockery.
This site doesn't allow satire but looks the other way when snarky claims are made without evidence. Blanket assertions must be backed up. At least show the problem you were trying to solve and the new solution in your favoured language/tool/framework so it can be judged.
This is how bad ideas and complexity gain traction without scrutiny and push back. People become vested in Ruby and run down php, people become vested in Rust and run down Go, people become vested in React and run down jquery. How comes tools people were using happily just yesterday are suddenly 'completely unacceptable'?
No one who befitted from these tools and languages is going to run them down publicly because they found something better. This is self serving ecosystem marketing at work that HN seems to ignore. It's as if every self congratulatory commentator often seen here was born an expert and short circuited the process of learning, and can use this platform to run down everyone else and their choices.
Re: Go: Ten years and climbing
#144I appreciate the ruthless design choices behind Go. Crafting a language so there are as few ways as possible, and preferably one, to solve a problem must be beautiful at a large scale organization. In my experience java codebases in big companies are nightmare factories because of the freedom you get from more similar languages. The Go dream of having a single decent solution to a problem instead of 20 that range fro…
>because of the freedom you get from more similar languages. Is this lack of freedom a good thing?
Naturality (i.e., the absence of either artificial constraints or artificial degrees of freedom) is a good thing.
Re: Go: Ten years and climbing
#145Maybe I'm spoiled, but I've had a hard time dipping my toes into Go due to the lack of batteries included frameworks (like Rails or Laravel). Can anyone recommend some resources to give it another shot?
Take a look at Buffalo, it's very much inspired by Rails.
Re: Go: Ten years and climbing
#146Earlier quoted context omitted.
And that's an intentional misreading of the Go devs. Read the Go Programming Language or any number of discussions by the guys behind Go and it's obvious that they care about their craft and care about writing real, working applications, while at the same time having a better understanding of what your application is doing. In their view the way to do that is through simplicity, but it's not a design decision intende…
> Do people really believe that individuals such as Rob Pike, Ken Thompson, and Brian Kernighan are just trying to propagate Blub, the language, so that all devs are lowest common denominator morons? It was Pike himself that stated that as a goal for Go at one of the early Goconfs, because new Googlers aren't skilled enough to pick up C++, Java or Python. If you wish I can track it down for you.
His quote was:
> "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. So, the language that we give them has to be easy for them to understand and easy to adopt."
It seems opposite of what you mentioned regarding C++/Java/Python.
Re: Go: Ten years and climbing
#147Not a Go programmer myself but I am very grateful for Go. Some of the best software I use everyday uses Go - rclone, gitlab, gogs, gosu, docker to name a few.
> gitlab
is written in Ruby.
Re: Go: Ten years and climbing
#148One of Larry Wall's slogans for Perl is "Easy things should be easy, and hard things should be possible." In its own way, that's what has made Go the kind of success that Perl once was. Perl was the glue language of the web and Go is the production language of the cloud. I'm actually a bit scared to imagine a world in which Go was not created, given how much success I've personally had with it. Thanks to the entire G…
This is a bad comparison.
Core philosophy of Perl is to empower programmers with more than one way to do it.
Core philosophy of Go is your coworkers are too stupid to be allowed to have nice things.
Re: Go: Ten years and climbing
#149Earlier quoted context omitted.
Which language released in the last 10 years is more popular then ? Golang is arguably niche and does not offer the huge flexibility and ecosystem of say Python, so i am pretty sure it will never come close to that, but there are a good number of usescases where it arguably is the best choice.
Scala, with 164 jobs in London and 225 nationwide, has been around for about the same time as a production-quality release. I raised the point because I think Golang's coverage on HN is disproportionate to its significance in the job market.
Scala is 13 years old. Golang was first publicly released 7 years ago
Re: Go: Ten years and climbing
#150Earlier quoted context omitted.
> Do people really believe that individuals such as Rob Pike, Ken Thompson, and Brian Kernighan are just trying to propagate Blub, the language, so that all devs are lowest common denominator morons? It was Pike himself that stated that as a goal for Go at one of the early Goconfs, because new Googlers aren't skilled enough to pick up C++, Java or Python. If you wish I can track it down for you.
His quote was: > "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. So, the language that we give them has to be easy for them to understand and easy to adopt."…
Not really, because in spite of "probably learned Java, maybe learned C or C++, probably learned Python", Go thin set of features makes a good developer in any of those languages feel like elite.