Anyone programming in Go?
-
If so what for? Pros? Cons?
-
If so what for? Pros? Cons?
-
If so what for? Pros? Cons?
That's a no go. :) Marc
Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project! Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny
-
If so what for? Pros? Cons?
Do not pass Go...
-
If so what for? Pros? Cons?
I am curious too! But since I use Xamarin at work and at home I am interested in GUI Desktop application, Go hold little practical interest for me.. :~
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
If so what for? Pros? Cons?
-
If so what for? Pros? Cons?
No, but I'd give it a go, sooner or later. For rest of the stuff, Go (programming language) - Wikipedia, the free encyclopedia[^]
The shit I complain about It's like there ain't a cloud in the sky and it's raining out - Eminem ~! Firewall !~
-
If so what for? Pros? Cons?
-
If so what for? Pros? Cons?
Apparently there are some people[^] using Go! :omg:
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
If so what for? Pros? Cons?
-
If so what for? Pros? Cons?
-
Original or Judas Priest's cover?
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
-
If so what for? Pros? Cons?
I think its time for new essay... Go too Considered Harmful ;-) (I'll fetch my coat)
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
I think its time for new essay... Go too Considered Harmful ;-) (I'll fetch my coat)
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
Do not pass Go...
I agree. One should definitely stop and check it out. The community is large and growing, the support is great, and the language makes tasks that are difficult in other languages a breeze. One important place where Go fits very well is as a Node.js replacement.
-
Original or Judas Priest's cover?
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
In either case: Johnny be good! ;P
-
If so what for? Pros? Cons?
Looked at it & did a little test harness with it a while back, but (despite some really nice features like goroutines) it didn't quite hit the mark for me. I'm currently writing some stuff in Rust[^], which I like for a variety of reasons - one being the strong, static type system. Oh - and the surrounding tooling (Cargo[^], the all in one project scaffolder/package manager/build tool/test runner, and rustup[^], which lets you manage installed versions of the compiler toolchain) is excellent.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
If so what for? Pros? Cons?
At my last employer, a colleague and I had to learn Golang (what Go is usually called online, because have you ever tried to google a two letter word? I doesn't work out well, usually) to build a API interface for our employer's cloud hosting API. It was to allow another company (Rancher) to be able to deploy Docker containers onto our employer's infrastructure fairly seamlessly. Learning it and using it was both maddening and enlightening at the same time. First off, we were able to learn it well enough to write our interface after the first week. We then spent another couple of weeks building the interface, then another week polishing it, writing unit tests, etc. Over a few succeeding months we had to make a few changes here and there, but overall it was done and "ship-able". My only regret during the whole exercise was that we were pair-programming to learn and support each other during the entire project, and it was under my colleague's account - so my name hardly (never?) appears in the github project. Oh well, c'est la vie I guess. It was maddening because Golang enforces the most strict rules you can imagine on you as part of the idea of avoiding bugs by not introducing any. One that really "got us" was the fact that you can't declare a variable, then never use it. You must use it subsequently, or the compiler will hate you. There are ways to get around this, but such means actually make things more difficult for you in the end. There was also the weird way of how the language isn't object oriented - it is closer to being a modularized functional language (think Javascript and Require.js) than anything else; wrapping our heads around that took a bit of cringing and whining, but we didn't have a choice in the manner, so we soldiered on. There was another issue we ran into, that had to do with data structures. Golang is fairly strict there; how they are organized on the Golang side (and typed) needs to be the same as what you were pulling from elsewhere; if they didn't match, you had to fix one or the other. Our problem was that our employer's API was originally developed in PHP (we also had a small hand in it - that was our main job - but most of it was there long before we were employed there - legacy code, right?) - and the RESTful interface spat back JSON encoded data that wasn't consistent from call-to-call. This was maddening - we couldn't change the results from the API to make it easier for the Golang side, because that would have broken anyone's code who used the original PHP and RESTful A