4 ms·
I don't use AWS, so I cannot compare. But I've been using Azure for ~2 years and have no problem doing what I need to do there. Surely, they can make the portal
by programmertote 6y ago
I don't use AWS, so I cannot compare. But I've been using Azure for ~2 years and have no problem doing what I need to do there. Surely, they can make the portal and UI more consistent (e.g., Azure Data Factory and Azure DevOps does not seem to reside in the same UI theme as the other Azure resources such as Logic App or Blob). Again, this is just my experience and I am sure for anyone who just started using it, Azure portal can be overwhelming and confusing to use.
- philistine 6y agoI'm not a software developer, but I set up two static sites in a so-called serverless fashion on AWS using only their products (Here's one of them, just as a shameless plug: gameboyessentials.com). They are reasonably consistent with their nomenclature and their error messages, but I definetely felt I was using a jackhammer to put screws in drywall. The amount of settings and types of setups per product is staggering. You definetly need to read a how-to to figure out what to do. You cannot figure it out on your own. In terms of UI, the fact that every separate product uses a different view model is bonkers. I understand that letting each product reflect its own functionnality is important, but a list of checkboxes should not have three different ways to display them across three different products (Route 53, S3, CloudFront). Oh and those naming schemes, jeez. Who thought Route 53 was a good idea?
- pier25 6y ago> but I definetely felt I was using a jackhammer to put screws in drywall That's a great metaphor to describe this. :)