| Fair enough. I think technical users probably don't need this site, but I think there is value to be had (even for those technical users!). For a bit of context: I found myself using this site via my xbox's web browser to make sure my wifi latency is acceptable where I put the xbox. Also, my spouse and I just moved to a new place, so I used this site on my phone to get a quick idea of the latency on wifi in my spouse's office. There's tons of web-based tools to test your bandwidth, but I feel there just isn't a similar ecosystem of quick, web-based "ping" (well, latency, since I can't send ICMP packets from a web browser) tools. - RE: HTTP only, good point. I've set up certbot and the page supports https now. I am not certain how HTTPS will impact the latency measurements, it appears the results are typically a bit higher and occasionally much higher when using HTTPS. - I don't get the disappointment with the use of JS. It's just a bit of inline JS, easy to manually audit if concerned. JS is quite safe IMO and is a very powerful tool, it makes a rich universe of interactive applications possible in the humble web browser. I basically got into CS because of the fun I had creating things for and sharing things on the web. |
Sure you did. But there's a whole category of phone apps called Wifi Heat maps, that would actually be "super simple" for a non-techie to use.
People are commenting on your use of javascript, where you are arguing that you built a super simple solution. As many already pointed out, the ping command is already there and is more "super simple" to use than to self host a website to get a skewed HTTP "ping" from some cloud service...