4 ms·

You should try Azure sometime. It’s a cloud service run by some scrappy upstart in the Pacific Northwest. I heard they have some of the best support for develo

You should try Azure sometime. It’s a cloud service run by some scrappy upstart in the Pacific Northwest. I heard they have some of the best support for developers, despite not having the name cachet around HN that the bigger players have.

samb1729 4y ago
They also unfortunately have some shockingly bad issues with securing their services
mschuster91 4y ago
Azure's UI is so shockingly bad, confusing and complex it puts AWS to shame.
- highwaylights 4y ago
  Seriously? I thought it made way more sense. I kind of wonder if this is a case of what-I-already-know bias for both of us.
  - smeagull 4y ago
    I found similar. Their documentation often refers to things that simply don't exist. Pictures of how menus used to look and no longer do. Multiple ways of doing the same thing that give slightly different results, with no real reason for the difference. I have heard though, that it makes more sense for people coming out of sysadmining Windows Server networks.
smeagull 4y ago
I did not expect to hear their support lauded by anyone. They prevent solutions to problems from ending up on their forums, aren't widespread enough to have solutions on stack overflow, and have documentation that is often simply inaccurate (i.e. they've changed the names of things, or moved options, etc.) Here's an example. We have an issue, find other people on their forums that have also had it, but no solution is visible. We file a ticket. They say it's a known problem with a known workaround and tell us the workaround. Why isn't it shared? Because they wouldn't share the solution unless you're paying for support. Some of their systems are a mess too. There are multiple ways of getting logs out of function apps, and only the most pain in the ass way that requires the most configuration is going to contain all the logs. Other viewers and ways of reading the logs will be partial. Resource groups are a great idea though.

samb1729 4y ago

They also unfortunately have some shockingly bad issues with securing their services

mschuster91 4y ago

Azure's UI is so shockingly bad, confusing and complex it puts AWS to shame.

highwaylights 4y ago
Seriously? I thought it made way more sense. I kind of wonder if this is a case of what-I-already-know bias for both of us.
- smeagull 4y ago
  I found similar. Their documentation often refers to things that simply don't exist. Pictures of how menus used to look and no longer do. Multiple ways of doing the same thing that give slightly different results, with no real reason for the difference. I have heard though, that it makes more sense for people coming out of sysadmining Windows Server networks.

smeagull 4y ago

I did not expect to hear their support lauded by anyone. They prevent solutions to problems from ending up on their forums, aren't widespread enough to have solutions on stack overflow, and have documentation that is often simply inaccurate (i.e. they've changed the names of things, or moved options, etc.) Here's an example. We have an issue, find other people on their forums that have also had it, but no solution is visible. We file a ticket. They say it's a known problem with a known workaround and tell us the workaround. Why isn't it shared? Because they wouldn't share the solution unless you're paying for support. Some of their systems are a mess too. There are multiple ways of getting logs out of function apps, and only the most pain in the ass way that requires the most configuration is going to contain all the logs. Other viewers and ways of reading the logs will be partial. Resource groups are a great idea though.