3 ms·
>It's faster, cheaper, more configurable. The documentation is actually comprehensible. The docs have more 404s than trumps twitter account... who payed/paid y
by ranman 10y ago
>It's faster, cheaper, more configurable. The documentation is actually comprehensible.
The docs have more 404s than trumps twitter account... who payed/paid you to write this?
- vgt 10y ago>>It's faster, cheaper, more configurable. The documentation is actually comprehensible. >The docs have more 404s than trumps twitter account... who payed/paid you to write this? (ranman works at AWS..and talking to an AWS premier partner... the delicious irony)
- ranman 10y agoGreat job addressing those 404s.
- vgt 10y agoAgain, a weird thing for an AWS employee to say about an opinion from an AWS customer and an AWS platinum partner, and then accuse them of expressing those opinions due to monetary compensation.
- ranman 10y agoI'll disengage... this argument doesn't really serve our customers well. I'll fully admit that the AWS docs are a pain... but to claim that the google docs are better is... I lack an appropriate adjective.
- owenmarshall 10y agoholy shit you two are embarrassing as hell. absolutely cringeworthy. I'd half consider migrating to Azure since it seems they're the only adult in the room... too bad it's such a terrible service;)
- ranman 10y agoYou're totally right. I apologize.
- vgt 10y agoYou're right, I crossed the line and sincerely apologize. I post here on my own time, and represent my views only. I recently noticed that AWS employees throw (sometimes not so) subtle shade at their competitors on HN without disclosing their allegiances. That's all fine, but I saw the same undertones directed at opinions made by a very good customer, which upset me. Throughout the thread I've attempted to engage in discussion, gather feedback, and share some info. I was set off a little :/
- merb 10y agoshame on you both. you are biased to google, but I actually preferred the AWS documentation. I still will migrate sooner or later to GCP, because of the superior pricing model. However missing postgres is still bad for us and we don't want to "go trough a partner". Cloud is already not so cheap, especially when we only need 3 boxes and a database. The problem is there aren't many alternatives that lets you have a managed database and 3 boxes in your own small network. If you want to do it yourself you either need a VPN or you would pay the same price as a Cloud if you want to interconnect hosted servers on non Cloud providers.
- vgt 10y agomerb, I apologize for getting a little heated. I saw an AWS employee attack a customer opinion (without disclosing their employer), and I wanted to set things right. On the feedback, I hear you. Please reach out to me offline for a further discussion (if you want).
- ignoramous 10y agoJacques doesn't speak for all of Pivotal. Its of course his personal opinion that GCP is way ahead of AWS. And Jacques, personally, is entitled to his opinion. There might even be merits to his statement here but he hasn't backed it up at all with data. Pls do not pass off his statement here as an official stand by Pivotal. Unless of course that's what Jacques here meant to do (I wouldn't know)...
- jacques_chester 10y agoIt is correct that unless I explicitly say otherwise, I do not officially speak for Pivotal. It'd basically be a terrible idea to give me an official mouthpiece, given how bombastic I am. And, of course, my opinion of GCP is just, like, my opinion, man. In my personal projects I have stuff on AWS. In fact I'll be adding more soon, since Pivotal Web Services is housed on AWS. And there's still a lot that AWS can do that GCP can't. It's just that, for the tiny slice of the world I've seen, I like GCP a lot more. No matter which platform you prefer, everyone will benefit from the fierce triangular tug-o-war between Amazon, Microsoft and Google. Especially if they're on a relocatable platform like Cloud Foundry (disclosure: Pivotal sells a version of this) or OpenShift.
- ignoramous 10y agoI like people who are critical and honest with their assessment. I value your opinion very highly, since you claim to have experience with the tools you are assessing. Thanks for clarifying statements and for the feedback. I would appreciate immensely if you can elaborate your frustrations with AWS apart from the ones you have mentioned already. You could either do it here or I could email you, or if you have a comment trail on this topic on reddit/hn/twitter, I'd appreciate the links. Thanks once again.
- jacques_chester 10y agoRemember, I am frequently wrong and fond of bombast. I feel that AWS has a strength and weakness in the fact that its longevity has led to a massive feature set. For those who've grown in expertise alongside it, AWS seems natural and obvious. I have instead come to this super-featuresome platform and found myself totally lost. If I was one of the people who'd consumed the new features piecemeal over the space of a decade, it wouldn't seem so daunting. I guess the same will happen to GCP. But even so, I find it much easier to get around in GCP. The console is obviously built as a unified experience. It still has a CRUDish flavour to it, insofar as it requires you to have some of the underlying model in your head to use efficiently. But it needs less and it tends to be less of a hunt for the foo that uses the bar that depends on the baz based on the quux which is ten bloody screens away under an ill-chosen name. Oh and AWS console seems to have a vendetta against allowing me to open up a bunch of tabs easily. I hate that. I usually want to look at two things side by side because weirdly, I find it hard to retain randomly-generated strings in my short term memory. As for performance, GCP brings up VMs extremely quickly, the networking is really fast and the prices are nicer. Truthfully, I've touched maybe 5% of what AWS or GCP offer. But the 5% I've seen is compelling. I think Google are going to finally break their total reliance on advertising revenue.
- jacques_chester 10y agoI haven't hit any yet. The AWS docs are enormous, cover every angle, and take me quite a while to work out. I'm not very bright. That said, Google's concepts are confusing in places. The one that caused me a lot of head scratching was the difference between forwarding rules and global forwarding rules. AWS has better diagrams in a number of places.
- ranman 10y agoThanks for the follow up and sorry for initial attack. As I said below AWS docs could be dramatically improved for accessibility.
- jacques_chester 10y agoI don't mind. You're passionate about your work. That's a good thing.