Every library and even using no library is a compromise between time, performance and features (maintenance costs time, so a library that makes it easier will save time).
I'm currently using react at work and it's a rather good compromise, because we work with 4 teams of varying experience on a very complex application.
But back to the original point: a virtual DOM is not a necessity, but merely one way to solve a certain set of problems – and in some (but not all) cases, other solutions might be a better fit.
That's a good way to put it, I just rephrased the title of the article so it's a bit more vague, but no longer claims that it's a necessity. Thank you!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You're right.
Every library and even using no library is a compromise between time, performance and features (maintenance costs time, so a library that makes it easier will save time).
I'm currently using react at work and it's a rather good compromise, because we work with 4 teams of varying experience on a very complex application.
But back to the original point: a virtual DOM is not a necessity, but merely one way to solve a certain set of problems – and in some (but not all) cases, other solutions might be a better fit.
That's a good way to put it, I just rephrased the title of the article so it's a bit more vague, but no longer claims that it's a necessity. Thank you!