Not I, but I’m definitely curious to hear what you find out!

@venantius might have some wisdom, I'm currently trying to figure out how to use the Accountant library

@coyotespike: I can’t comment on how well Accountant works with search engines, but there’s no need for hashbang magic

It's much prettier without hashbangs!

However, even with the intuitive goodness of Accountant, it turns out that Google is not any happier with , as this returns a 404

So I'm working on http://prerender.io - I'll try to throw the results of all this into a gist @eggsyntax

What are good arguments on using display none vs not emitting the html at all?

@mbertheau: for me it mostly fits into declarative programming style

@pepe: which it?

@mbertheau: sorry, emitting html

but it could be it is only my own mental model

and for sure, the debugging could be harder (on-mouse-enter and such)

is creating a cursor from a cursor supported?

@mbertheau: I would not recommend display:none for components which have deep DOM structure or potentially render other components. Bail out as early as possible and let react effectively update the DOM by not emitting html at all. Display:none was handy in times of $(“.section”).hide(), that is history.

I haven't used display:none, but it does seem to be React's official recommendation (if your component is stateful & you don't want to lose track of that state): https://facebook.github.io/react/docs/multiple-components.html#stateful-children