blog.worldmaker.net VS riot

The biggest flaw that I think most other flaws derive from is making the huge dependency on RxJS, but then not trusting it and building in escape hatches that end up making "Angular Best Practices" wind up becoming "RxJS Worst Practices" and performance suffers accordingly. I noticed that even the Roadmap now mentions that they are finally re-evaluating the play between RxJS, Angular Change Detection and Zone.js. Rx.JS is "push" oriented so why do you need two complex "pull" oriented systems around it?

(In my opinion: Zone.js and Angular Change Detection are these extremely baroque, over-complicated systems that aren't necessary at all if Angular actually trusted RxJS to "push" changes. Or they could skip the huge RxJS dependency and go all in on "pull" like Vue/Svelte. What they have today is a worst of all worlds compromise that benefits no one.)

Blog post is here: https://github.com/WorldMaker/blog.worldmaker.net/blob/gh-pa...

Or you can read it on my actual blog site but it scrolls horizontally when the browser is wider than tall and that got a lot of hate the last time my blog was on HN that distracted from the contents: http://blog.worldmaker.net/2021/06/26/angular/

While we are at it, here's the Component Framework I built out of what felt like necessity to try to make following RxJS best practices easier in building Angular Components (and make it easier to switch components to ChangeDetectionStrategy.OnPush and apps towards being able to set Zone.js to "noop"), which I built out of some struggles doing performance optimization work in Angular and some patterns I was already following in Component building: https://worldmaker.net/angular-pharkas/

These articles form a series focusing on RiotJS paired with BeerCSS, designed to guide you through creating components and mastering best practices for building production-ready applications. I assume you have a foundational understanding of Riot; however, feel free to refer to the documentation if needed: https://riot.js.org/documentation/

This article covers how to create an Riot input component, using the Material Design CSS BeerCSS. Before starting, make sure you have a base application running, or read my previous article Setup Riot + BeerCSS + Vite.

However, Riot is my first choice when creating a front-end, here is why:

Riot.js is designed to be lightweight and easy to learn, making it a good choice for developers who are familiar with HTML and JavaScript — without requiring them to learn the rigors of coding with a specific framework. Riot.js emphasizes simplicity, performance, and modularity, its ecosystem allows for easy integration of third-party libraries and components, making it suitable for both small-scale and large-scale projects.

how about getting a hold of your sanity and allowing yourself a few hours to learn https://riot.js.org/ - almost no learning curve, only pure awesomeness. even if you won't use it in the enterprise (because policies, bla bla), it is still worth knowing things can be done differently - in a good way.

Riot.js prides itself as a light and simple UI library that helps developers hit the ground running when creating elegant UIs for their applications.

Thanks! Glad you like it. I'm the original author of Riot (https://riot.js.org/) so that's the style of frontend development I'm most comfortable with. We're using our own flavour of the library, which has the original super-mimimalistic feel on it.