25 comments

[ 3.4 ms ] story [ 59.8 ms ] thread
http://www.sonnyjs.org/demo/ appears to be down?
I noticed that its broken in Firefox but not Chrome.
I'm able to load it in Chrome and Opera but not in IE or Firefox
And it's a pretty unfortunate failure mode. IMHO, it should at least render a basic failure message that is removed by a working site.
similar to meteor, page needs second or two to load, presenting user a blank screen.
Just over 7s here, and /demo takes 12s and ends up with a blank page.

Not ready for prime time.

Demo site looks to be down? At least not rendering for me, FF nightly on android
Can anyone get the docs page at http://www.sonnyjs.org/?home to scroll correctly? I have to zoom it way out to see everything. OSX 10.10.2/Safari on a 13" Retina display.
Went to http://www.sonnyjs.org/ (latest Chrome, Windows 7) - there doesn't seem to be any way to scroll the left-hand menu (it cuts off at "StorageManager" sub-heading for me at default zoom level, I can see there are more by zooming out though) and of the ones I can see, the menu items "render" and "kill" don't seem to do anything.
It's trying to load a public.html that isn't there?
You know how to make an incredibly fast single page app? Pre-render it on the server. I'm tired of waiting several seconds while the JS framework gets initialized.
truly so. I'm currently developing an isomorphic app with react/flux and pre-rendering on the server is really a revelation.
I've done that for our company's websites. We were sort of forced into it by search engines but overall it's much better now. The frontend is written in Backbone.Marionette and it wasn't exactly simple.
Well, React was designed to be isomorphic. I found it pretty simple.
Our project was started before React was public. I'd certainly look at React if I were to start a project.
You are right, http://huu.la is using server rendering and prefetching technique, which makes the ux x00% better than this one.
Why are people upvoting this broken trash? Because the author put "Incredibly fast" in the title? Is that all it takes?
Why is it trash?
Because it's a slow, broken reimplementation of things which Angular already does better and which only work well in any case when you're on a blazing-fast low-latency Internet connection, or better yet browsing localhost -- did I mention those times I posted earlier were on desktop? I shudder to think what'd happen if I tried loading it on my phone.

And it also appears to be implemented entirely in a single 1300-line-long Javascript file, which, okay, I guess? There are no tests -- yes, there are examples in a directory called "tests", but there are no tests, which is to say there's no way to get any confidence that modifications in that 1300-line Javascript blob haven't produced regressions or new bugs.

Presumably the author has learned something in the process of writing it, although I can't imagine what that may be. I don't know why he'd spend his time on this, though; from the looks of his Github account, he's also written an in-browser Pokemon game engine which looks pretty cool, so I don't know what value he sees in hacking up a half-baked me-too web framework.