[lookingsideways]

> Bulletin board system gains nothing from "single page application" style architecture, it is a collection of documents, stick with it.

I'd have to say the Discourse project (http://discourse.org) provides a fantastic counter example to this. It shows what can be achieved when SPAs embrace the URL and a lot of thought is put into how the modern browser features can be used to improve the user experience rather than just jumping on the bandwagon.

Example forums:

http://meta.discourse.org http://discuss.atom.io http://discuss.emberjs.org

[hpaavola]

Discourse emulates the normal behaviour really well, good for them. After a quick look looks like they do not suffer from the issues I mentioned before.

I just do not see any benefits going SPA style when working with data that is essentially collection of documents.

[nawitus]

Single-page applications can change pages faster.

[aikah]

not convinced discourse UX is that good either,in fact NodeBB copies a lot from discourse.

[dingdingdang]

neither am I, there's a good reason people are willing to pay for older BB systems like IPBoard and vBulletin, they work and they are iteratively improved upon instead of 'UX-rebooted' like Discourse and NodeBB. I personally don't think any of the systems are perfect but the the older forums work fine as long as they are popular enough that resources are dedicated to policing them.. so I personally feel proper inter-forum karma integration should be top priority, more-so than new UXs!

[hiphopyo]

This is why I prefer https://github.com/radar/forem by the "Ruby hero" Ryan Bigg. It's also for Rails but without the bells and whistles from Discourse. A.k.a. "The best Rails forum engine. Ever.", it's perfect if you want to build something unique from the ground up.

[ttty]

You can see my app too: http://PlaysZone.com uses the same single page concept with server side rendering for the first loaded page. The other pages loads some json with ajax.