design-system-builder

If you don't have to support IE11, there has been a very interesting trend of JS Proxy based state managers (immer, react-easy-state, overmind, etc.). It reduces the boilerplate compared to redux while giving basically the same architecture. I have been using my own implementation, because react-easy-state did not work well with styled components (https://github.com/UgnisSoftware/lape), while I was building https://github.com/UgnisSoftware/Ugnis if you want to see this approach in use.

I think Bubble is great and we need more people experimenting with visual programming! We have been working on a visual tool[0] for ourselves and the development speed gains are incredible. Hopefully, there will be more non-text based programming environments. [0] https://github.com/UgnisSoftware/ugnis

> Do you not count e.g. jQuery as a framework? Not really, it was used as a library to make JS work consistently across browsers and add missing features like querySelector and ajax fetch. But it had no opinion on how you should structure your app. Angular, Backbone and Ember is from the same post-jQuery era when talks about Web components started. > Being standardized, i.e. any old framework that can work with the DOM can with them But does a developer really care that it's possible to use the same component in different frameworks, when you need it to work with just one (yours)? I think the biggest fallacy is that people expect a technology to appear where you could just drop the component and it would work perfectly. From my experience, that will never happen - external component libraries are 90% what you need and 10% of hacking aroun