Closed elfassy closed 7 years ago
Interesting read
"Before finalising on this approach, we analysed a number of other options including Angular. We determined that writing our own binding system would allow us to keep the framework small, and the process would help us to determine exactly what our requirements were from it. We suspected that moving to another JavaScript MVC framework would bias us towards that framework’s design. We were also skeptical as to whether any JavaScript MVC framework would be immune to the same problems we experienced with Batman, and that we would ever be able to create a native feeling application at our scale. These frameworks work well for highly interactive apps with complex user interface requirements. We only needed a small piece of what a full framework would offer."
Reed:
I just found out about another approach to separating backend and frontend concerns. It uses Node+Reactjs to implement views-as-a-service over HTTP. The example uses a PHP app for the backend but it should be easy to do the same thing with a Rails app. The javascript code is "isomorphic" so it's write once--you don't have to write separate code for both node and react--and it runs on either the server or the client making it search engine friendly.
@elfassy that sounds great. I'm excited about the idea of separating FE and moving away from javascript frameworks. I'm a React fan myself.
Moving this discussion in its own issue