With this, however, comes frustration from the inevitable duplication. Business logic is duplicated between Rails models and Backbone models. URL routing logic is duplicated between Sinatra and Sammy.js. Views need to be rendered in the browser for users, but on the server for Google.
The rise of Node.js gave developers a common language shared between client and server, yet the two environments are so different that sharing code between them was still difficult. Clearly there is a demand for tooling that helps solve these problems and DRY up our code.
Having worked on developing the Drumkit.js code-sharing framework over the last year, I have first-hand experience seeing what approaches work and which ones fail. As a software engineer at Groupon (which is primarily powered by Ruby code), I have been able to introduce Node.js apps into the ecosystem that were built quickly and are maintained easily thanks to these code-sharing techniques.
NOTE: While Drumkit.js will be used as an example of how code-sharing techniques can be implemented, this talk will NOT be a pitch to use the framework.
Attendees will walk away having learned about…
In addition, attendees will be given access to an open-source demo that exemplifies the explained techniques and can be used as a starting point for their own project.
People will want to attend because…
For information on exhibition and sponsorship opportunities at Fluent conference, contact Gloria Lombardo at (203) 381-9245 or email@example.com.
For information on trade opportunities with O'Reilly conferences contact mediapartners
View a complete list of Fluent contacts