Agree Ritesh. Lars is just flaming.. there are definitely use cases for running code at the start of a component. I was honestly hoping he would post a URL to these phantom "frameworks" he refers to.. 🤷♂️
One example could be frameworks that are actually written in Typescript.
Frameworks that utilize observables and not promise-based logic.
Frameworks that don't require a "root component" in components, they can actually handle templates without a root component that doesn't do anything.
Frameworks that embrace standard HTML, not forcing absurd syntax like "className" just to set at class.
Just the clutter of having to use horrible syntax for useEffect() to have something running at the start of a component, is absolutely nuts.
Could you link us to some of the mentioned "modern frameworks", please?
Lol actually there are a lot of advantages of React which make it 100% worth the disadvantages
Agree Ritesh. Lars is just flaming.. there are definitely use cases for running code at the start of a component. I was honestly hoping he would post a URL to these phantom "frameworks" he refers to.. 🤷♂️
Flaming? that was not my intention. Of course there's use for running code at the start of a component.
One example could be frameworks that are actually written in Typescript.
Frameworks that utilize observables and not promise-based logic.
Frameworks that don't require a "root component" in components, they can actually handle templates without a root component that doesn't do anything.
Frameworks that embrace standard HTML, not forcing absurd syntax like "className" just to set at class.
Just the clutter of having to use horrible syntax for useEffect() to have something running at the start of a component, is absolutely nuts.
These are just a few examples.
Sounds great! Would you mind posting a URL to one or two of these?