On Mon, Oct 10, 2011 at 8:20 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> On Mon, Oct 10, 2011 at 4:04 PM, Konstantin Khomoutov <
> flatw...@users.sourceforge.net> wrote:
>
>> All those flashy JS bells and whistles consistently make me think
>> they're really there for the sake of being there.
>>
>
> But what better reason could there possibly be ;).
>
Providing the reader a better experience.
Yes, I know you weren't really serious. But enough web authors seem to take
that attitude seriously that it's a sore point for me.
Such things are generally there to hide the fact that the content isn't
worth reading. In this case, there's useful information there, so why not
actually present it?
Personally, I find the "colorize the code on the client" hacks incredibly
wasteful. You could colorize it once when you generate it, but instead you
colorize it every time someone wants to read it? Talk about a silly waste of
CPU. Or has CPU really gotten so cheap that this is now acceptable, and I'm
doing nothing more than showing my age by worrying about it?
Now, there *is* something useful that could be done here. Let the reader
control the colorization. Of course, that can be done with dynamic CSS, and
you could provide it and still only colorize things once. But I haven't seen
a colorizing tool that does even that much.
In this case, you're generating the diff at read time, so there's no savings
in avoiding doing things in JS. But if you're going to do that, at least
take the opportunity and let the reader control what they see.
<mike
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
