You often want to build an app as quickly as possible. To get some kind of MVP in the hands of users, giving them value and something for you to incrementally improve. Most features can come later, but if you ever intend to offer a shared editing experience of any kind, you really need to think about it up front.
At Threads Styling we were faced with such a prospect when planning their Social Story builder. Having worked with CMSs in the past, we knew the pain of managing document locks with all their edge cases. We also knew that eventually the use case will arise to concurrently edit the document, and if you haven’t planned for it, it is a monumental task.
By treating the document as a stream of JSON patch changes from the very beginning, we were able to offer real-time collaborative editing with conflict resolution smoothly handled by an Operational Transformation algorithm. In this talk, Jason will discuss the concepts involved and demonstrate a simple, but working example of a shared document using our open source library.
By Jason Green, Principal Developer at Threads Styling - Twitter: @aziraphael
I confirm my talk is 20 mins long in total.
I confirm that I will abide by the Code of Conduct
Ever since the start of Node-RED, the runtime and editor components have been packaged together as a single blob of npm module.
With the 0.20 release we split the internals apart into 6 separate new npm modules, along with the original node-red module to glue it all back together - and we did it without end users ever knowing (apart from us talking about it at every chance we got).
This talk reveals how we went about this refactoring and the challenges of managing multiple modules in a single repo. I'll talk about why we ultimately decided not to use one of the various mono-repo tools, such as Lerna, and ultimately decided to roll our own approach.
I'm an Open Source developer at IBM and the creator of Node-RED. I can be found online as @knolleary in lots of the usual places.
I presented about Node-RED at LNUG in its very early days of September 2013, not long after we'd first open sourced it.
