<rant>Go programming language</rant>

[Jackolantern]

OK, so I had some interest in at least looking at the Go programming language. I have heard it has a pretty novel way of handling concurrency.

So I hit up Monster.com, just to get a general feel of the job market for it. I can't find anything, because it returned 1000's of programming jobs that all simply used the word "go" in them. OK, that is fine. I read a bit on the homepage. Then I wonder if anyone has made a game server with it. I tried "go game server", and ended up getting a ton of projects working on online game servers for the Asian game of Go. Hmm...how about "go language game server". Now a ton of forum posts about people trying to set up different localizations of their Go servers, and people in Europe wondering whether they should go for an English or native server on popular MMORPGs. "go language mmorpg server" also returned crap where people were simply talking about MMO servers and used the word "go".

Why did they name it "Go"?!? Searching for anything related to this language ranges from a gigantic pain to impossible!! They gave their language a name that is an extremely common piece of speech. How about I call a new language "And"? Or how about "To"? Yes, there are other languages that have fairly poor names when it comes to searching, but they are older before the modern era of web searching, so they can be forgiven. Go was made in 2007.....by Google!! It seems like if anyone would have had a bit of forethought about the impact such a common name would have, it would have been Google!!

OK, sorry about that. I just had to get this frustration off my chest. It also completely made me lose interest in checking it out.

[Verahta]

https://www.google.com/webhp?sourceid=c ... e&safe=off

[Jackolantern]

I was able to find the language itself very easily. But when you start trying to add in other things is when things start falling apart. And the problem on Monster still persists (adding the word "Google" gets into a whole different world). But even to find the language itself, that is 4 words just to make the reference because it has such a poor name! If it had a unique name, like Globble, Geeboo, Gipro, Gigo, etc., it would be a one word search, and you could easily add any other word to it and every search engine would know what you meant.

And to top it all off, there was already a programming language called "go!"

[Verahta]

That figures lol. I never even heard of it until now

[Jackolantern]

Honestly, I had never heard about it before, either, until Google's Go was created and the creator of go! started complaining that it would cause confusion.

Of course, everyone (including Google) politely told him it would not cause any confusion because Google's Go has Google behind it and no one has ever heard of go! before.

But it doesn't change the fact that if you take out the exclamation point, there are two languages with the exact same name lol.

[kaos78414]

Haha, I had this problem too, turns out people have solved it by referring to it as golang, for the most part that will return more relevant search results

I actually enjoyed my experience with it for the most part, not least of which was ease of setup. But I think I would get more out of it if I had already understood C

[Verahta]

Oh my, I didn't know there was TWO languages with Go... until just now

[a_bertrand]

Honestly, I find all those language a pure pain. Why? Sure we should evolve and maybe bring new bright ideas to the table, but I don't know you, I know personally that I may need actually 5 years to really start to master a language. Mastering it means I fully understand how the documentation works, I have a good grab on the environment. Make code that I can show without being scared even a couple years later, and do quickly what I need using what the language / framework offers. Yes 5 years! Sure I can make a code in a couple of days or hours in a new language but that's not what I call mastering.

Now if every 6 month a new language come (yes I point at you Apple, Microsoft and Google), I don't even have the time to think about what it could bring.

Another issue is that there is so many new languages that actually people don't jump on it, and may never jump on it due to the fact it's too new, to scarcely used, and then the language die.

A language needs DECADES before it really reach maturity, where you are sure you will not need to trash your code on the next release, and offers what you would want from it. Even then, check out PHP which have more and more backward compatibilities issues.

No sorry, I don't want to jump on any new language without being 100% sure it will bring me a lot. F# ? No thanks. Ruby ? Why ? Typescript? Stay away from me! Dartlang? Yea sure...

Here was my rant

[Jackolantern]

It is a fact that most new languages die a lonely, obscure death. We just don't need new programming languages every day, where each dev has to start over at square 1 and build up a reliable class library that has already been built over and over again in existing languages. Most new languages talk about having some "killer feature". If it really is a killer feature, existing and popular platforms will simply implement it themselves.

It was just a fleeting interest I had in looking at Go that was completely destroyed by the ridiculous situation I experienced trying to find things relating to it.

Even with the concept of using "golang" to search, I still find it unacceptable that the community has had to come to an unofficial understanding on just how they will perform searches with this unwieldy language name.

[kaos78414]

It was just a fleeting interest I had in looking at Go

Was it that you read that the guy who created Express decided to move to Go (https://medium.com/code-adventures/fare ... a9e7f3e52b)? I read that and decided to give it a try. But it's so young that there's really not a whole lot of resources on it thus far. I was able to create an HTTP server pretty quickly in it, but after a while of fidgeting with it I decided I'm far too invested in Node to learn a whole other platform just because a prominent member of the community has moved on.

I do like that they've gone the package management route. You can install stuff as simply as "go get github.com/gorilla/websocket".

Anyway, I haven't messed with it enough to develop an informed opinion. Considering it's age, I'll probably just relegate it to "fun toy to play with" for now, until it gains traction (if/when).