Those are the Canvas PRs. Should be able to include them in your app with this in your Gemfile:
gem 'bowser', git: 'https://github.com/clearwater-rb/bowser.git', branch: 'canvas-support'
gem 'clearwater', git: 'https://github.com/clearwater-rb/clearwater.git', branch: 'canvas-support'
I just realized Clearwater Playground (https://clearwater-rb-playground.herokuapp.com) was down. It uses Neo4j as a data store and I didn't set up the Neo4j SSL certs correctly. They were automatically updated when they expired, but symlinks were pointing to the old versions, which caused an SSL validation error while connecting to the DB.
It's back up now, though. :+1:
@fkchang I've given talks on it a few times. Here are the slides from the first place I gave it: https://s3.amazonaws.com/jgaskins/uploads/Neo4j.pdf
I didn't talk about it from the perspective of Ruby, more from a data-centric perspective since that's arguably the more important part, but the
neo4j gem is pretty great. It's heavily inspired by ActiveRecord, but handles the graph properties really nicely and I love its associations API. I don't think it supports has_many :through, but N+1 queries are a lot less common.
It's a feature we had at my old job for report data, but we used Postgres and it was painful to do. CTEs are hard, I don't understand them, and they're slow on Postgres.
Actually, I believe the author of the
neo4j gem gave a lightning talk at RubyConf last year.
Click the link, though. The embed doesn't start at the right time.
I only realized he gave the talk because he was directly after a friend of mine.
Indeed :-) I saw it when GitHub released their dependency graph feature. I wouldn't doubt it's an extraction of some of the patterns they used for https://arkivdigital.se
@fkchang But I didn't realize there was a full-on website for it. Thanks for the heads up there!
I just published
clearwater-virtual_list, a gem for rendering large lists without putting the entire thing in the DOM.
It requires either Opal 0.11 (I think) or at least has to have opal/opal@07610e0 applied.
Built a Clearwater component the other day that renders promises, mostly inspired by React Suspense. It uses method chaining to declare what to render up front, at various time delays, and on resolution/rejection of the promise: https://clearwater-rb-playground.herokuapp.com/playgrounds/598a3a3d-b0f7-472d-9f88-aa3c1a1b9ae2
I don't use a lot of promises within components typically, but if I need to, I can't imagine it getting any nicer than this. I certainly like it more than what I've seen of React Suspense.
is http://jgaskins.org/blog/2016/02/28/turbolinks-vs-the-virtual-dom still a fair article? 8ms for clearwater seems too good to be true
@foucist That article is definitely still fair. :-) I just checked the Clearwater app linked in the article and it actually took 6ms from the click event to the final paint.
That's less than the 8ms I measured for that article, but I'm on a newer machine than I was when that article was written, and less than 2ms of that 6ms was spent in JS. The rest was layout/paint. With some reasonable render caching, even large vDOMs can be blazing fast.
My favorite Clearwater performance story is from a real-time order dashboard I developed with Clearwater while I was at Groupon. We were getting hammered by data over websockets and even with about 10-15k nodes in the DOM (nearly all of which were managed by the Clearwater app) and we were still hitting 30-60fps renders.