Looked at it yesterday and chitchatted a bit with mouser on IRC about it - but haven't looked at it enough to have any super well-formed opinion. Some ideas seem nifty, others perhaps less so. Not sure what to think of it being pageless - the idea that your "reading progress" is saved is nifty, but for really long threads you're going to have a veeeery tiny drag-selector on the scrollbar. OTOH, it's nice not having to do a page refresh (and losing contents of your edit box...) to read more - but that could be accomplished with AJAX in a paged environment as well.
Guess I'll have to play with it a bit more, and see what happens as it gets more polish. My initial impression is that it could work well for some sites, but I don't think it'd suit DoCo.
I also can't help but wonder how well it will scale because it's written using ROR.
I was pretty puzzled when I saw it was built on ROR, considering how well ASP.Net has worked for the StackExchange platform. But I guess it's a combination of only parts of the ASP.Net stack being open, and (perhaps more important) not being able to run ASP.Net gratis
(you really do need to run it on Windows, MONO is not quite there yet).
Fans of Ruby often argue it's not Ruby itself that's the problem (as in sloooooow) - but the way people (who don't understand it well enough) code it.
Ruby itself is damn slow and doesn't support multithreading (there's projects like JRuby
, but meh), and while Ruby is a sorta-kinda-OK language it's not really that special in and by itself... if it wasn't for Rails, it would still be a niche language most people hadn't heard about. And Rails is a big effin' rats nest of vulnerabilities - stay clear
Ruby follows the old crappy UNIX notion of "let's spawn a process per request! Processes are cheap!
", so to get any kind of decent speed, you need a load balancer that dishes work off the one of several spawned Ruby processes (which need to be restarted every now and then because of memory leaks). There are hacks
to reduce the impact of this, but... meh.
I really don't get why one chooses to do anything but prototypes in Ruby/Rails, really. You've already moved beyond the "Runs on every cheap-ass host" PHP and into the domain of having to pay at least a bit for the hosting, so why Ruby
- and if you need fast turnaround, go Play
around (despite the name, it's ready for production use).