Show HN: FuelDOM – A React-compatible virtual DOM implementation | Hacker News Reader

Show HN: FuelDOM – A React-compatible virtual DOM implementation

github.com

29 pointsbrn2728 comments

ok, i'll be "that guy".

the obvious thing everyone wants to know [and is not addressed] is why someone would use this over Preact [1] or Inferno [2]?

[1] https://github.com/developit/preact

[2] https://github.com/infernojs/inferno

So It's my hobby side project. I want to try to implements vdom.

cool :)

you need a lot of tests to cover all your features as assurance that regressions won't happen and everything works as designed.

Is React slow for people? Maybe I haven't pushed it to any limits performance-wise yet, but I don't think I clearly understand the use case for breaking out of the ecosystem for an alternative virtual DOM implementation.

The motivation for many clones is the Facebook patent clause in the react license. My company said "no way" to using react because of it, and I'm sure many others do as well.

So use a similar technology, likely also infringing on Facebook's React patents vs. protection that only applies if you don't sue Facebook over patent issues?

Software parents are a minefield. For bigger companies it's definitely not worth the logistics to keep track of which companies you can and can't sue

Facebook's Patent grant is expressly for use in case you sue Facebook over patents... I'm pretty sure if you do that (sue fb), they'll look at everything they can use to sue you... That would include other technologies that may infringe on any Patents related to React.

I don't think the problem with React is with the DOM aspect, it's state management and persistence where things get bogged down conceptually.

Thanks for reaction. I think so too. But other vdom implementaion is more bad things, like riot. React state and props system is not bes, but it's easy to use and understand for javascript developers. I think reactjs is enter maturity stage not bogged down.

Why? I don't think it is.

React is pretty damn good. I don't really see the problem all these clones are trying to solve, including the latest Vue hype.

Going to digress a bit but I'm working on a project in Vue and while at first it seemed like a literal breath of fresh air I came to the awful conclusion that no matter what SPA framework/library you're using, if it's javascript, you gonna be using webpack + a medium size build pipeline for es2015, jade, scss, bundling, file watching, hot-reload etc. The arguments for small libraries aren't as strong anymore because the advantages of the larger ones have enough cost/benefit that you're going to be pulling them in EVENTUALLY so might as well do it from the beginning.

You don't happen to know how to get vuex working idiomatically with deeply nested data do you? I can work with it but only if I start passing around object references, which seems like a terrible idea.

No clue, haven't used vuex yet :/ .

ah ok, no worries - I think it's similar to Redux largely, which unfortunately includes being severely incompatible with nested state values.

In redux I use functional lenses to create composoable getter/setter functions to handle deeply nested data safely. I do that even without redux, but it is very useful there. Take a look at the lens functions in Ramda, or safety-lens

I'd never thought to use lenses for this. Thanks for the advice, that actually really helps!

> including the latest Vue hype

I don't see anything here exceeding the hype on React...

> including the latest Vue hype

yeah, what's about that? AFAIK Vue isn't new and wasn't that special back then.

I've only previewed vue at this point so I can only say this about why it's "better": preference.

When I looked at vue2 I saw a lot of the same features as angular2 except the binding syntax looks better to my eyes and way of thinking.

When I look at jsx I go cross-eyed.

When I look at HTML, I want to "see" the view and construct it in my head. I don't want JavaScript mixed in it.

Note: I realize vue and angular bindings are essentially JavaScript in attributes, but they can (and should) be minimal and fade into the background IME.

If you look at React components as components, it makes a bit more sense, at least to me that the view rendering is part of the component, and not the inverse.

Yea agreed, super confused on what's wrong with React. I know the renderer is being re-worked, but that only matters for Facebook-sized projects afaik, which 99.9% are not.

Well, Vue is a different approach... I find Vue closer to WebComponents than to React.

The github page says "more simple and fast". Can't find any benchmarks.

Out of subject, but I glanced at the title and kinda wished the name was "FreeDOM" :)

There's actually another pretty interesting library 'react-lite' https://github.com/Lucifier129/react-lite

It's a slim down version of React. "intended as a drop-in replacement for React, when you don't need server-side rendering in browser(no ReactDOM.renderToString & ReactDOM.renderToStaticMarkup)."

Could you tell in README.md what problem does it solve or how different it is in comparison to React?

Reply on news.ycombinator.com