I figured they wanted to keep this written solely in Perl.
Not to keep it in Perl, specifically, but to keep it entirely on the server.
There is a reluctance to make any feature of the site depend on Javascript, or any other
browser-side technology (other than HTML and CSS).
There is also a concern about Javascript specifically, and that is its potential
for cross-site scripting attacks and other hackage.
See thread Let users link in a javascript library for one representative discussion of the issues.
Between the mind which plans and the hands which build, there must be a mediator... and this mediator must be the heart.
| [reply] |
Not to keep it in Perl, specifically, but to keep it entirely on the server. There is a reluctance to make any feature of the site depend on Javascript, or any other browser-side technology (other than HTML and CSS).
Just wondering... Could one avoid the full page reloads that are needed for voting, even without AJAX, by using... Iframes? I realize that Iframes are bad and deprecated and all, but they might be suited for this job:
Just put a "++" and a "--" button into an iframe above every post. Of course it would need some more requests to initially load all these extra frames, but that doesn't need any database access, and connection caching should mitigate most of the overhead.
| [reply] |
The full page reload upon casting a vote is inferior as a user interface to the Ajax-driven dynamic HTML you see everywhere these days (YouTube, Amazon, etc). It's tedious to click, scroll, click then reorient myself after a reload. Especially when reloads are slow because the site is slow.
It also seems likely that voting-triggered full reloads contribute to the site's overall sluggishness.
| [reply] |
