424
Looks like google domains is no more. (lemmyonline.com)
submitted 3 years ago by to c/selfhosted@lemmy.world
124 comments fedilink hide all child comments
 

Knock on wood, I have not used them in quite a while.

you are viewing a single comment's thread
view the rest of the comments
[–] 10 points 3 years ago* (2 children)

Not to mention that the cpanels, documentation, and APIs for Google Cloud look like they were written by alien robots to be consumed by alien robots. I've never seen any other platform or docs as confusing and pointlessly convoluted as gcloud docs.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 11 points 3 years ago (1 child)

    They're the absolute worst. Doc links will go in circles, redirecting you back to where you just were, API documentation is out of date - or worse it's out of date and doesn't tell you until the end of reading if it even tells you at all.

    Not even mentioning how everything is in permanent "alpha" and "beta" state. Things are never finalized so they can get away with changing the definition on a whim and say "sorry it was in beta, now it's in beta5". I had to rewrite Pub/Sub code at least once a month because they changed their spec on that, and that was one of their "most finalized" products.

    Fuck GCP, I will actively avoid jobs that code on it now. If you want enterprise customers, provide an enterprise product. This isn't chat where you can rebuild it every year because your marketers are bored. These are enterprise products that companies depend on.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 8 points 3 years ago (1 child)

    Doc links will go in circles, redirecting you back to where you just were

    Right? Who the fuck created this standard? You'll arrive at a doc trying to figure out how to get somewhere and it'll tell you everything except for how to actually get there. It'll finally have a link with the link text being the name of the section you're trying to find, but noooo... It doesn't actually link there, it links to a second document explaining the fucking history of that section, why they named it what they did, the engineer's dog's puppy's name, and anything else to fluff out the doc without actually being useful. Why in the hell would you write a doc about an interface and not link to the relevant interface? I guess it's probably because they completely rebuilt the way that website interfaces work and you can't actually bookmark or deep link to anything. You always end up at the same page regardless of what you bookmark and then you have to manually navigate there. They took all the wonderful working features of the internet and broke them, then made alternatives that are 1000x worse.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 3 years ago

    I'm so happy, I'm not alone anymore... this frustration was a constant dread that I felt alone, and I feel like we're two lost souls, wandering the plane of Google's terrible documentation, lost forever looking for the json schema for the API we need, constantly searching, never finding it.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 0 points 3 years ago* (1 child)

    Honestly, it's not as bad as AWS or Azure. Plus if you use k8s it's first-in-class support, since Google came up with k8s. There is a fairly steep learning curve though.

    If you're deploying anything in cloud infra you need to make sure it's portable between providers. Vendor lock-in is a big avoidable no-no.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years ago (1 child)

    In my opinion AWS is considerably more clear and simple than gcloud.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 3 years ago

    They're both very complex so it's understandable people would have different experiences. In general I've found GCP fairly straightforward, with shitty documentation, generally good support of fundamentals, great k8s support, good prices, fairly modern APIs, and relatively low feature coverage. AWS more built out, awful & totally inconsistent UI, better feature coverage, higher prices, and some pretty janky XML APIs if memory serves.

  • permalink
  • fedilink
  • source
  • parent