Yes, definitely. MathJax gives really nice-looking output, scales with screen resolution, and can be added to the site without much effort. The only downside is that it's a bit of a large download, but that's what caches are for. If you include the JavaScript file at the end of the HTML body, rather than in the head, it will download after the page is rendered, so the loading time shouldn't be noticeable.
I'm pretty excited about this.
If you include the JavaScript file at the end of the HTML body, rather than in the head, it will download after the page is rendered, so the loading time shouldn't be noticeable.
I am skeptical of this claim.
Does your browser never become unresponsive at unpredictable times? Mine (Firefox 3.6) does.(Firefox 4 is much worse, BTW.) Since I use Flashblock, I tend to believe that the main cause of these lapses is javascript though I am willing to listen to arguments to the contrary.
MathJax requires memory for one thing (after it has been running a while, Fir...
In the next month, the administrators of Less Wrong are going to sit down with a professional designer to tweak the site design. But before they do, now is your chance to make suggestions that will guide their redesign efforts.
How can we improve the Less Wrong user experience? What features aren’t working? What features don’t exist? What would you change about the layout, templates, images, navigation, comment nesting, post/comment editing, side-bars, RSS feeds, color schemes, etc? Do you have specific CSS or HTML changes you'd make to improve load time, SEO, or other valuable metrics?
The rules for this thread are:
BUT DON’T JUMP TO THE COMMENTS JUST YET: Take a few minutes to collect your thoughts and write down your own ideas before reading others’ suggestions. Less contamination = more unique ideas + better feature coverage!
Thanks for your help!