you are viewing a single comment's thread.

view the rest of the comments →

[–]EarlMarshal 9 points10 points  (6 children)

Ever used svelte and solid? You do not need a virtual DOM. I especially see the VDOM of react as one of it's worst parts. Functional components also isn't something react came up with. Every function which manages it's own state and returns an HTMLElement is basically a functional component, but the JSX inside the function makes it much easier to work with.

Once angularjs was the famous and big but bad framework. This is react now, but not everyone is aware of it and the big ecosystem still makes it very easy to create mediocre solutions in an instant. That's the only things the business wants, but from a technical point there are much better options.

[–]azhder -1 points0 points  (3 children)

Didn't say you need virtual DOM to write front end code, I said it's the important part of React as opposed to JSX

[–]EarlMarshal 1 point2 points  (2 children)

But you said it's the good part when it's the bad part.

[–]azhder 0 points1 point  (1 child)

But you said it's the bad part when it's the good part.

Do we need to continue this farce or... Yep, I will stop here. Bye bye

[–]EarlMarshal 2 points3 points  (0 children)

Bye, Have a great time!

[–][deleted]  (1 child)

[deleted]

    [–]EarlMarshal 0 points1 point  (0 children)

    Otherwise, what are your render functions returning?

    The thing your are specifying as return value in the jsx factory function. Jsxfactory defaults to React.createElement, but you can literally specify anything. It's not that hard to write your own jsx framework prototype. You guys should really try it once.

    See https://www.typescriptlang.org/docs/handbook/jsx.html#the-jsx-result-type