Is this a Go-flavored version of something like https://jclouds.apache.org/?
Portable Cloud Programming with Go Cloud
91–100 of 158 posts
Re: Portable Cloud Programming with Go Cloud
#92Maybe it's a biased and distorted perception that I have, but Go seems to be the most consistent and unsurprising language I've used, and I mean this positively. I haven't written any Go for over a year since my current job mostly uses Node, but I feel immediately comfortable jumping in to the examples in this blog post. I don't think that I'm explaining what I mean very well, but it's something I don't think is so t…
Our company uses Go. Most people who join have no experience in Go yet usually they can get comfortable with the language in 1-2 weeks to start contributing. I know nothing about Node/JS but I'm sure that takes much longer?
Most people who join have no experience in Go yet usually they can get comfortable with the language in 1-2 weeks to start contributing.
A lot of what makes anything hard to learn are the non-obvious gotchas. The design philosophy of golang is aimed at avoiding the non-obvious gotchas and the creep-up-on-you-at-scale gotchas.
Re: Portable Cloud Programming with Go Cloud
#93I like to see how Go seems to getting some traction within Google. For years, I had the impression that Google was more Java/JS/Python driven and I was wondering why they weren't using their own language for more projects :-D
Google is actually C++ centric - every other language is a bit of a "second class citizen" when interacting with infrastructure. Go is still new and Google is "old", so there is surprisingly little Go code at Google - it doesn't make sense to rewrite critical infrastructure just because you have a shiny new language. The derivative is positive though, and slowly Go is being used for more and more new development.
I can assure you that on Android world C++ feels pretty much "third class citzen".
Re: Portable Cloud Programming with Go Cloud
#94Re: Portable Cloud Programming with Go Cloud
#95ironically terraform is already written in golang. https://github.com/hashicorp/terraform Go 96.1%
Terrafirm isn't provider neutral. It is just a declarative wrapper for cloud provider APIs. Code using one provider is not easily translated to another. I do think it's an excellent configuration management and provisioning tool, but Go Cloud solves a different problem.
Yes, we are solving a different problem. Terraform is about provisioning resources, Go Cloud is about interacting with them.
We actually use Terraform for provisioning in our samples, and we see the two working hand in hand.
Re: Portable Cloud Programming with Go Cloud
#96It took us a while to get here. But it appears as if we've finally recreated the guestbook. And now it runs on someone else's machine.
Re: Portable Cloud Programming with Go Cloud
#97Wait until Microsoft introduces their voodoo magic into their APIS that it would be impossible to write wrappers around them.
Re: Portable Cloud Programming with Go Cloud
#98Earlier quoted context omitted.
Google is actually C++ centric - every other language is a bit of a "second class citizen" when interacting with infrastructure. Go is still new and Google is "old", so there is surprisingly little Go code at Google - it doesn't make sense to rewrite critical infrastructure just because you have a shiny new language. The derivative is positive though, and slowly Go is being used for more and more new development.
I can assure you that on Android world C++ feels pretty much "third class citzen".
Yep. Google has built multiple ecosystems and they each have their own preferences. The grandparent was talking about Google's internal, server-side ecosystem. People working in that area sometimes assume that's it's the default.
Client-side development is a whole different thing. It's fragmented between browser, Android, and iOS. (And each of those is further fragmented, with multiple languages available.)
Re: Portable Cloud Programming with Go Cloud
#99Earlier quoted context omitted.
> we are very aware of our responsibility to be cloud provider neutral Yet, Azure support is listed as unplanned. The language could mean that this is not going to be planned. The fact that y'all have not worked with Azure Go folks to get this moving is something to ponder. A reminder that Go is a Google language and isn't vendor neutral?
PM for Go Cloud here (and poster of the Azure feature request). "Unplanned" on the issue tracker just means we haven't assigned it to a sprint milestone for the team yet. Azure and more clouds are very much in the works. As an open project, there are many approaches and we're open to all of them. One other point: since Go interfaces are implicitly fulfilled, anyone can write and share implementations of Go Cloud for…
Hi PM guy. If project is to remain independently cloud-gnostic and people file a lot of bugs and pull requests it'll definitely help Google or Alphabet or whatever deliver that k8s abstraction y'all've workin' on. That's great for you.
My my question is, what if developers want access to innovations in specific cloud providers, such as reduced redundancy storage on S3? Wire up or own provider? Will there be some sort of community-provided provider registry or will we be grepping awesome lists on GH? Are providers extendable in any way?
Thanks and have a sunny day.
Re: Portable Cloud Programming with Go Cloud
#100Maybe it's a biased and distorted perception that I have, but Go seems to be the most consistent and unsurprising language I've used, and I mean this positively. I haven't written any Go for over a year since my current job mostly uses Node, but I feel immediately comfortable jumping in to the examples in this blog post. I don't think that I'm explaining what I mean very well, but it's something I don't think is so t…
Go is certainly very easy to reckon with. But I was surprised at how little O cared for it when I tried it, given the hype I'd heard. The two things that immediately jumped out at me were error handling and generics. I understand both were deliberate choices but I'm still surprised they were made - I've been working with Swift a lot lately and it just feels like it makes so much more sense to me. I do love how opinio…
I feel like a caveman typing out error handling code in go, but on the other hand (even as a beginner in Go) I _never_ run into unexpected conditions. There's tradeoffs of course but every time I find myself thinking about what kinds of error conditions may be happening in my Node code (where I spend most of my time), and whether I covered them all... i think I'd trade.