5 ms·

AWS wasn't first with per second billing. As the GCP blog states, GCP Persistent Disks had it since 2013. (I work for Google)

deanCommie 9y ago
Maybe instead of constantly having to disclose working for Google, all you Google Compute engineers could just try not bragging about it so much every time there is a discussion thread on it, and just let the community figure it out for themselves what cloud provider they prefer.
- theDoug 9y ago
  We disclose our employer to be clear that while we are super excited about these releases, we're also trying to be as open and clear that our opinions come with a natural bias that others seem to rarely disclose. There's no coordination or conniving to this, people just like rad stuff. Also, I /wish/ I was a Compute Engineer.
- Veratyr 9y ago
  I don't really have a problem with it. So long as they're on topic and relevant (i.e. not trying to sell GSuite in an AWS thread), it's fine. Certainly better than not hearing from them at all.
- BartSaM 9y ago
  This is not bragging, it is an important piece of the information that informs you if someone commenting can be biased or self-promoting in a news, that their company is featured in.
- kylecazar 9y ago
  Seems like parent merely stated a pretty uncontroversial fact. And they are part of this community as much as anyone else is -- I at least appreciate the stakeholder participation and honest disclosure.
  - musage 9y ago
    > Seems like parent merely stated a pretty uncontroversial fact. Exactly. Here's one scenario: > "I think this is a really fun movie, and I thought the ending was very smart (disclosure, I did some FX on the sequences with the Shnorp, and I have an affair with the producer's sister)" here's another: > "You are both right, actually: the running time for the US release is 94 minutes, whereas the Swedish contains the Shnorp nipple scenes which increase the total length to 96 minutes. (full disclosure, I was a roadie on the set)" Guess what I find obnoxious and see many discussions filled with? If it's in a dictionary, thanks for the fact, no I don't care who you work for or how "excited" you are and how "awesome" your team is and whatnot. It's so incredibly needy and tacky and seems the norm now; where the person calling it out actually gets piled on, while BS like this https://news.ycombinator.com/item?id=15342721 https://news.ycombinator.com/item?id=15342721 is fine. It is what it is.
    - musage 9y ago
      Circle the wagons and just clap it out.
- m00x 9y ago
  I actually enjoy the extra information they give, and the clear excitement about what they work on. I've seen how the sausage is made at AWS and the people I've met that worked on it were extremely detached. This very much shows in the product. GCP is behind on features, but I find the features work very well and are super nice to work with.
- azurezyq 9y ago
  (disclosure: I also work for Google Cloud.) I think put the disclosure upfront just make things clearer that we are not dragging. You already know where our butts sit and you can judge our words from pure-technical perspective. Otherwise, people may say Google hire a bunch of ghost accounts just for promotion purpose. I personally prefer the former.
  - vgt 9y ago
    I personally prefer to weave the fact that I work at Google right in the middle of the point that I am trying to make.
    - oh_sigh 9y ago
      There are eleven words in your post to the left of 'Google', but thirteen to the right(like this post) so your post is lies.
      - vgt 9y ago
        my plot's been revealed!
RKearney 9y ago
AWS is miles ahead in IPv6 adoption though. Why do GCP employees always post in HN articles about how much "better" GCP is than AWS or how GCP "did it first"? Our company literally can't use GCP, full stop, because Google is completely ignoring IPv6 support. I heard load balancers are now in beta, which just terminates IPv6 and connects to the back end with IPv4. When am I going to be able to make an outbound IPv6 connection from GCP? Specifically the Compute Engine VMs.
- boulos 9y ago
  The IPv6 termination is now GA, but I agree with your sentiment (we're behind on IPv6). That said, it's a very binary thing: you either have IPv6 throughout the virtual networking stack or you don't. We're not ignoring it, particularly since Google cares so deeply about IPv6 worldwide, but we are behind. Disclosure: I work on Google Cloud. Edit: I'm not sure why you're being downvoted, it's a fair criticism.
- samstave 9y ago
  Can you ELI5 what we ppl who are deploying to any cloud should have as First Principles WRT IPv6 and why we should be architecting around it? Disclosure: I like turtles.
  - blasdel 9y ago
    Apple's App Store review has a hard requirement that everything works on a pure IPv6 network
    - soccerdave 9y ago
      The only thing that you have to do to satisfy this requirement is don’t hardcode IPv4 addresses in your app. If you are using domain names for everything then it doesn’t matter if those are only resolvable to v4 addresses.
      - snuxoll 9y ago
        Correct, using DNS on a IPv6 only network is enough since the point is to use DNS64/NAT64 to handle the transition until services are IPv6-native.

deanCommie 9y ago

Maybe instead of constantly having to disclose working for Google, all you Google Compute engineers could just try not bragging about it so much every time there is a discussion thread on it, and just let the community figure it out for themselves what cloud provider they prefer.

theDoug 9y ago
We disclose our employer to be clear that while we are super excited about these releases, we're also trying to be as open and clear that our opinions come with a natural bias that others seem to rarely disclose. There's no coordination or conniving to this, people just like rad stuff. Also, I /wish/ I was a Compute Engineer.
Veratyr 9y ago
I don't really have a problem with it. So long as they're on topic and relevant (i.e. not trying to sell GSuite in an AWS thread), it's fine. Certainly better than not hearing from them at all.
BartSaM 9y ago
This is not bragging, it is an important piece of the information that informs you if someone commenting can be biased or self-promoting in a news, that their company is featured in.
kylecazar 9y ago
Seems like parent merely stated a pretty uncontroversial fact. And they are part of this community as much as anyone else is -- I at least appreciate the stakeholder participation and honest disclosure.
- musage 9y ago
  > Seems like parent merely stated a pretty uncontroversial fact. Exactly. Here's one scenario: > "I think this is a really fun movie, and I thought the ending was very smart (disclosure, I did some FX on the sequences with the Shnorp, and I have an affair with the producer's sister)" here's another: > "You are both right, actually: the running time for the US release is 94 minutes, whereas the Swedish contains the Shnorp nipple scenes which increase the total length to 96 minutes. (full disclosure, I was a roadie on the set)" Guess what I find obnoxious and see many discussions filled with? If it's in a dictionary, thanks for the fact, no I don't care who you work for or how "excited" you are and how "awesome" your team is and whatnot. It's so incredibly needy and tacky and seems the norm now; where the person calling it out actually gets piled on, while BS like this https://news.ycombinator.com/item?id=15342721 https://news.ycombinator.com/item?id=15342721 is fine. It is what it is.
  - musage 9y ago
    Circle the wagons and just clap it out.
m00x 9y ago
I actually enjoy the extra information they give, and the clear excitement about what they work on. I've seen how the sausage is made at AWS and the people I've met that worked on it were extremely detached. This very much shows in the product. GCP is behind on features, but I find the features work very well and are super nice to work with.
azurezyq 9y ago
(disclosure: I also work for Google Cloud.) I think put the disclosure upfront just make things clearer that we are not dragging. You already know where our butts sit and you can judge our words from pure-technical perspective. Otherwise, people may say Google hire a bunch of ghost accounts just for promotion purpose. I personally prefer the former.
- vgt 9y ago
  I personally prefer to weave the fact that I work at Google right in the middle of the point that I am trying to make.
  - oh_sigh 9y ago
    There are eleven words in your post to the left of 'Google', but thirteen to the right(like this post) so your post is lies.
    - vgt 9y ago
      my plot's been revealed!

RKearney 9y ago

AWS is miles ahead in IPv6 adoption though. Why do GCP employees always post in HN articles about how much "better" GCP is than AWS or how GCP "did it first"? Our company literally can't use GCP, full stop, because Google is completely ignoring IPv6 support. I heard load balancers are now in beta, which just terminates IPv6 and connects to the back end with IPv4. When am I going to be able to make an outbound IPv6 connection from GCP? Specifically the Compute Engine VMs.

boulos 9y ago
The IPv6 termination is now GA, but I agree with your sentiment (we're behind on IPv6). That said, it's a very binary thing: you either have IPv6 throughout the virtual networking stack or you don't. We're not ignoring it, particularly since Google cares so deeply about IPv6 worldwide, but we are behind. Disclosure: I work on Google Cloud. Edit: I'm not sure why you're being downvoted, it's a fair criticism.
samstave 9y ago
Can you ELI5 what we ppl who are deploying to any cloud should have as First Principles WRT IPv6 and why we should be architecting around it? Disclosure: I like turtles.
- blasdel 9y ago
  Apple's App Store review has a hard requirement that everything works on a pure IPv6 network
  - soccerdave 9y ago
    The only thing that you have to do to satisfy this requirement is don’t hardcode IPv4 addresses in your app. If you are using domain names for everything then it doesn’t matter if those are only resolvable to v4 addresses.
    - snuxoll 9y ago
      Correct, using DNS on a IPv6 only network is enough since the point is to use DNS64/NAT64 to handle the transition until services are IPv6-native.