I’m pretty satisfied with the direction ADG3 is going and the options available . Here’s some thoughts:
I don’t think it’s feasible to offer an un-opinionated UI toolkit that works well with every option a developer might want once you start to include dynamic behaviour. AUI was also opinionated too: it’s coupled with jQuery, is stateful + uses direct DOM manipulation that React (and clones) don’t like.
@remie: Have you considered writing some ADG3 CSS overrides for AUI? Despite using React we chose this option for existing products for the short to medium term and have had great results – inception to shipped in 2 days. FWIW Bitbucket, Confluence and JIRA did this too. Happy to share more about that.
@jcheung: AtlasKit is my choice but I do think the reduced UI pack could be further improved by including more of the possible UI states AtlasKit offers as “dumb” HTML/CSS. That way if @remie or others want to use a different framework (Vue.js) or library (select2) while they’ll still need to make the components interactive (the cost of going against the grain) at least achieving the visual design is easier.
^^ This could better support the community-driven ecosystem of alternative options and help keep them visually consistent with ADG3/AtlasKit.