I wonder about the complexity and AWS motivations.
What does AWS gain by improving IAM? There are barely any competitors, so they won't be losing people for that. They offer their own AWS professional services happy to charge you for making it "understandable". Their service agreements largely absolve them of client mistakes. Which usually result in larger bills from AWS.
AWS is a ball of complexity because it grew organically that way, and they don't have a culture of explaining, or, keeping things simple.
Both of those things would require strong strategic guidance, and a real effort to do.
Unless Bezos edicts: "Our APIs must remain simple even as they scale, and we must document in a manner that keeps the 80% common path easy to use, while the remaining 20% arcane functionality available ..." then it would happen.
But it won't.
It's reasonably well curated arbitrary complexity, it is what it is.
No cynacism meant. My mistake. "motivations" was incorrect. I was trying to ask about how the business of AWS manifests such a thing. Which I think you've described. Thanks!
"hence not in CLI applications" is that specific aspect accurate? I'm no longer mac user but thought mdfind (https://ss64.com/osx/mdfind.html) was the command line version of what smart folders use. Not the same as a filesystem but usable for many CLI apps.
Scala has a history of embedded domain specific languages that are difficult to understand. (Rather like Perl now that I think about it.) This is not universal in scala EDSLs but definitely exists. So it's a fair concern in general. IMO Chisel is a nice EDSL so, in this context, the concern is unwarranted.
No worries for Amazon SDEs! The amazon software developer "outside contributions" agreement basically states that you are not allowed to do anything without approval anyways. /s
Seriously tho. When I was employed by them their agreements were by far most draconian compared to any other company I've worked for. Ridiculous.
Most companies I've worked did have a route to enable you to contribute to projects outside of work and still retain the rights. Tho the easiest route is to establish something within a domain you want to work and then state that on a "inventions and copyrights" pre-employment agreement. This will outright eliminate you from certain jobs but... That's the US for ya.
IIRC prior to being treated you agree to be financially liable for the costs. Prior to even knowing that that will be or even the costs involved. Or even if you know what is involved are you going to understand what a reasonable cost is? EG: Sling is easy but what about a x-ray study? Is that 200$ or $150?
Just like a proper capitalist system! You know, like when you agreed to pay whatever for your iPhone prior to even know it'll work.
> You know, like when you agreed to pay whatever for your iPhone prior to even know it'll work.
I can contact Apple for help with any issues I have with my iPhone. I can contact my carrier for any issues I have with my iPhone. I can return my iPhone within a grace period if I don't like it.
For fun I do this: I ask them how much it'll cost upfront. (they can rarely even give bounds). Ask about refund policy (?!?!?!). Tho must be done nicely as the person handling the questions is no way responsible for the absurdity.
I know these won't actually succeed in adding a bit of capitalism but it does succeed in highlighting the absurdity.
I'm not sure what your argument is. Is it that it is fine that our healthcare is like shopping at an Apple store? Or that medical costs cannot be predicted? Or that we should be happy with the system we have?
Other than pedantry, what are you trying to get across?
What does AWS gain by improving IAM? There are barely any competitors, so they won't be losing people for that. They offer their own AWS professional services happy to charge you for making it "understandable". Their service agreements largely absolve them of client mistakes. Which usually result in larger bills from AWS.