Because you can't have too many UI frameworks, can you?
Amazon Web Services has released AWS UI, which the cloud services biz describes as "the first step in a larger process of creating a new open source design system." The context for this is the open-sourcing of the user interface code for the .NET Porting Assistant, a tool to scan Windows-only .NET Framework applications to …
Wasn't there an apocryphal story about the number of groups working to develop a compiler determines how many passes the compiler would have?
Seems to me every large independent organization ends up building up its own in-house framework. Maybe several. It's just natural.
And management comes along and says "a framework is not a product, why are you wasting time on this? You should be working on ..."
And then some bright spark says "Hey, let's opensource it for the creds (and to validate our egos) and... just maybe... to get free help from everyone."
Later, management comes along and says "why are you working on community engagement? That's not a product! You should be working on ..."
And that opensource framework dies. It's just natural.
If you're wanting to use AWS UI on your own projects, you should know that I wrote an open-source component for customizing the theme of your AWS UI components:
* npm: https://www.npmjs.com/package/awsui-theme
* GitHub: https://github.com/CharlesStover/awsui-theme
And a no-configuration-necessary dark mode
* npm: https://www.npmjs.com/package/awsui-dark-mode
* GitHub: https://github.com/CharlesStover/awsui-dark-mode
Biting the hand that feeds IT © 1998–2021