search

zetachang / react.rb

Opal Ruby wrapper of React.js library.
http://reactrb.org/
MIT License
547 stars 35 forks source link

Selectable/Seperated Rendering engine #141

Open Thermatix opened 8 years ago

Thermatix commented 8 years ago

This is a feature request.

I think making the rendering engine selectable can only be a good thing.

For mostly the following Reasons:

Sticking to react.js forces you to be constrained by it.

Sticking to react.js also adds an unnecessary abstraction layer that you don't have control over.

Server Side rendering would run in native ruby, so you would not need a JS engine for that and it would be faster.

You'd only have to define some common semantics that would allow a common interface so that you could use either clear water, react.js or any other as the rendering engine.

You could even build your own rendering engine and add any feature you want.

wied03 commented 8 years ago

@Thermatix - seems like a pretty tremendous undertaking. Wouldn't it be better off going the Clearwater direction if that's what you want?

Thermatix commented 8 years ago

Actually, that's exactly what I proposed but catmando said (in the gitter chat for react.rb).... actually I can't recall what was said exactly; but I think he said something that went along the lines of: that you should be able to chose and that react.rb's DSL should act more as an abstraction layer for clearwater,react.js or whatever else you want.

wied03 commented 8 years ago

Just my opinion, but it would be hard for me to see the value in trying to build that, especially for the core react.rb project. I've seen many case of abstraction layers that try to hide something really big like this and they usually fail.

sollycatprint commented 8 years ago

This issue was moved to reactrb/reactrb#141