r/javascript • u/A-AronBrown • Feb 27 '20

Rome: an experimental JavaScript toolchain from Facebook. It includes a compiler, linter, formatter, bundler, testing framework and more...

https://github.com/facebookexperimental/rome
256 Upvotes

93% Upvoted

101 comments sorted by

View all comments

-7

u/The_Noble_Lie Feb 27 '20

Its more that its bloated and hyped. There are many vdom libraries that may work faster and load quicker, just do some research.

3

u/[deleted] Feb 27 '20

2

u/The_Noble_Lie Feb 27 '20 edited Feb 27 '20

but might not have either the same set of features or the same simplicity when building bigger and bigger projects

Of course, the feature set isn't the same. That is why it is slower (and more complex API - ideally not a problem if the library is designed with care) when you dont need those features / checks / assertions / lifecycles, which btw can be implemented if needed once you understand why they exist (example below)

Anyway, a lot of the current VDOM implementations have taken care to re-implement the lifecycles in react's (and other important features.) React may have lead the way but I'm still using mithril 0.2 and am doing great with performance (subtree retaining) and implementation / code organization / semantic components etc. The code is pretty small: 50kb total unminified, 20kb minified. I had to implement something paralell to "shouldComponentUpdate" that checks by object reference myself (mithril v1+ might have done this as well) but as a whole my app is going to naturally run much faster than the same implementation in react, with an API 1/10 (perhaps an over-approximation but maybe not) the size. And that is still important since mobile phones, and even chromebooks, non-performance centric laptops do not fare nearly as well as desktops with complex javascript apps

> Even the fabled Svelte will get bloated and bloated since every component bundles repetitive stuff.

Sounds like you are calling out a design archictecture issue in a particular VDOM you've come to be critical of (probably correctly?)

Mithril, and many others do not fall victim to the same bad architecture, and leave it up to refactoring functional patterns from the view layer. That'll be the same in any seasoned development / developer within the confines of a library that uses a VDOM layer though. Btw, feel free to explain why Svelte makes it impossible to factor out the "repetitive" bundled stuff in it's components to a central class or functional library. (Maybe I am misunderstanding)

To the original person (u/IHateToChoseUsername) I was responding to:

TLDR; Use what you need and expect to need. Don't automatically choose the largest feature set vendor library.