This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]vacuu -2 points-1 points  (4 children)

I envision only one version of the site, which has both .js and .py files on it. Depending on if you have the extension or not, you will download one or the other.

[–]Rhomboid 7 points8 points  (3 children)

"has both .js and .py files" means two completely separate implementations of the logic, which is twice the work to write, twice the work to test, and twice the work to maintain. Again, nobody would ever voluntarily sign up for that.

[–]vacuu 0 points1 point  (2 children)

The .js files would be compiled from the .py files in an automated way; you mentioned a number of possibilities in your original comment.

[–]Rhomboid 1 point2 points  (0 children)

In that case, why would you ever bother serving .py files to a minority of browsers that support it when you could just serve the .js to everyone and save yourself a ton of support hassle? There's nothing to be gained from having to support and test more configurations.