Nobody is disputing that client-side rendering is great after first load. But that doesn't mean you can get away not doing server-side rendering on first load.
You've got it all backwards. Why do you think twitter went into full client-side rendering and then back to shared rendering? SEO? Lol.
Client-side rendering is never faster than server-side rendering for first load. It just can't be. I can't believe I have to point this out to people.
Hey,
Yeah I saw yours, and I didn't mean to "overthrow" your package or anything, but the only piece of functionality I was really looking for was publishing news.
Unifying our efforts sounds like a good idea. I could add you as a collaborator :)
So far it just logs in, posts or edits news, removes news, and retrieves news. Do you think there's use cases for the rest of the API?
(getting comments, posting and removing/editing comments, updating your profile, voting, password reset, creating an account, logging out)
What features would you miss when making the switch to Dominus?
Note, though, that the point is to provide a library that does one thing well (DOM querying and manipulation), so it won't ever have XHR baked into it, for instance.