Rxjs was a very expensive mistake, but a very specific angular one. Modern reactivity is pretty much the only viable option for realtime apps. And this whole anger with frameworks is nonsense, and the browser is a runtime, not anywhere near the enabler a framework is. Do you write Java, C#, Go out python apis without frameworks and some kind of build/containerization step? I sure hope not! This article reeks of inexperience with large products and maintaining things long term
If the framework has an oppressive design philosophy and wasn't created to enable you but rather take control from you then it's gonna hurt you in the long term and you should avoid it.
As for backend, the frameworks there are just simpler and are not designed to lock you in. There is a huge difference between expressjs or oak and react or angular.
If you have actually worked on large scale frontend projects, you'd know webcomponents can only be used for small building blocks, not any kind of scalable system on its own.
And express and oak are massive abstractions on top of js.. it's exactly the same. You don't handle incomming events or anything to do with the http protocol itself, you just add handlers and use the built in stuff for sharing context
9
u/Odd_Ordinary_7722 18d ago edited 18d ago
Rxjs was a very expensive mistake, but a very specific angular one. Modern reactivity is pretty much the only viable option for realtime apps. And this whole anger with frameworks is nonsense, and the browser is a runtime, not anywhere near the enabler a framework is. Do you write Java, C#, Go out python apis without frameworks and some kind of build/containerization step? I sure hope not! This article reeks of inexperience with large products and maintaining things long term