4 ms·
I'm going to ignore the "Shit HN says" vibes on this one for the most part, but I suspect that Microsoft and the Azure team specifically might have some relevan
by mhoad 5y ago
I'm going to ignore the "Shit HN says" vibes on this one for the most part, but I suspect that Microsoft and the Azure team specifically might have some relevant thoughts about building distributed systems regardless of if you like their dashboards or not.
As for Blazor, I think you might be missing the larger point here that I am trying to make. But .NET is still this Windows thing in the minds of most people. That hasn't officially been true for a couple of years now but the .NET crowd are coming to things like Linux and Front End now for the first time.
There are about to be a lot more conversations between say the React crowd and the Enterprise app development crowd, I am actually excited to see what they can all learn from one another.
- gjhr 5y agoI'd agree with them that the portal is terrible. Multiple times a day I get blank page errors, where the page is completely blank except for a single non-sensical error message in black text. However their actual services are also pretty terrible. Pretty much everything takes significantly longer to deploy than the AWS couterpart. There are so many preview and deprecated features that it is often hard to judge exactly what feature set you are getting, this is often compounded by the fact that almost everything has multiple SKUs which also change available features. Azure AD RBAC is a bit of a mess, although its conceptually simpler than AWS IAM policies its just a pain to use in practice, and its often slow for changes in permissions to actually reflect. Azure VM disks are annoying to use too, you can't set the size of the OS drive at creation and extra data disks come unformatted. "Grossly incompetent" is probably an overstep though, Azure is very impressive, just not as impressive as its competitors right now. Having said all that their are a couple places where Azure really shines in my opinion: * Resource groups (GCP has a similar feature) allow you to more easily keep track of related resources across services. * Price transparency. Many (not all) services tell you up front hourly/monthly costs as you are deploying them through the portal. You don't have to track down a pricing page or calculator yourself. * Azure functions are amazing when using C#/.Net. A huge amount of the regular boilerplate is abstracted away into simple C# annotations so you can get a large % of business logic.
- MisterKent 5y agoHi, I work on the portal team. Would you mind sharing what the issue is you're seeing?
- gjhr 5y agoHi, thanks for replying. I'll send you a message on Monday when I get back to work to recreate it.
- AdrianB1 5y agoHi, can you guys look at the portal security? In some corporate accounts most people have limited access to do stuff, but it is all enabled; you spend a few minutes to create a new resource just to get an access error after you submit, when it should be disabled (displayed, but disabled) if you cannot do it, do the access check before not after. There are so many options we never know which one is enabled and which one is not.