Knock on wood, I have not used them in quite a while.
this post was submitted on 16 Aug 2023
424 points (98.4% liked)
Selfhosted
46218 readers
162 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.
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.
In my opinion AWS is considerably more clear and simple than gcloud.
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.