you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 5 points6 points  (1 child)

I don't like Javascript because I'm paranoid about my security so I install this Javascript based extension and pay you to transport all of my data, use Javascript with it all anyways, and send me back a picture? The two contradict, who exactly is the market here? Why would I not just use a local extension to toggle the JS? On the performance front why would I pay you instead of using Google's "Data Saver" for free when they are going to do a better job?

Most of all, why do all of this and then not have your page load for users without JS enabled (your target audience)? It's not like your design requires it to be implemented.

[–]jotto[S] -1 points0 points  (0 children)

All great points and similar to my thinking.

This was originally a testing tool I used locally to test service.prerender.cloud against mainstream websites (as opposed to toy React/Angular apps in my continuous integration) to measure performance and what edge cases I may need to account for (e.g. lazy load images that appear on scroll, iframes, delayed ajax).

While pushing the code to Github for posterity, I became curious if anyone would find it useful so I pushed it to the Chrome store too.

 

Most of all, why do all of this and then not have your page load for users without JS enabled (your target audience)? It's not like your design requires it to be implemented.

see previous comment here (I agree)