Submission + - Ask Slashdot: Do you test your webpages with Microsoft Edge? 1
shanen writes: If you're doing any webpage programming for money, then I'm pretty sure you are paid to support Edge, too. Probably even required to test it. So this question is really directed to the relative amateur programmers among us. As I think about the topic from my overly philosophic perspective, I even considered asking "Do you feel pressured or even blackmailed to support MS Edge?"
Context seems called for, but as often happens, mine is messy. I have an ancient PERL/CGI system. The server is not under my control, but after 15 years of pretty good service, recently it has become flaky. It is a messy and crufty system that deserves a page-one rewrite, but who wants to do that these days? (Answer: Better and more industrious programmers than yours truly.) So my latest old-tool approach is to resort to JavaScript. I have (too) often used a kludgy approach with moderately complicated data structures embedded in JS files that are loaded on the fly, but... Prevert [sic] that I am, I'm considering the straightforward (for twisted values of straight) approach of doing the same thing with 800 KB of data. Sort of a page-zero rewrite, but with a focus on eliminating a bug in one of the messy regexes. Should work well enough for big computers with unlimited data, but quite probably a strain for my older smartphone. Since it's mostly for my own use, I don't care at all about Edge, but it got me to thinking and led to this question.
Now about the "There's no such thing as a stupid question" thing. My last accepted Ask Slashdot question was trying really hard for stupid. Though it triggered a pretty long discussion it was of limited interest and I feel sort of obliged to apologize for it. Especially since the question was mostly answered in the first comment and I should have figured it out on my own, too. Will it help to blame Microsoft again? (As I type into a Windows 10 box (in spite of having plenty of other OSes available on various boxen around here).)
Context seems called for, but as often happens, mine is messy. I have an ancient PERL/CGI system. The server is not under my control, but after 15 years of pretty good service, recently it has become flaky. It is a messy and crufty system that deserves a page-one rewrite, but who wants to do that these days? (Answer: Better and more industrious programmers than yours truly.) So my latest old-tool approach is to resort to JavaScript. I have (too) often used a kludgy approach with moderately complicated data structures embedded in JS files that are loaded on the fly, but... Prevert [sic] that I am, I'm considering the straightforward (for twisted values of straight) approach of doing the same thing with 800 KB of data. Sort of a page-zero rewrite, but with a focus on eliminating a bug in one of the messy regexes. Should work well enough for big computers with unlimited data, but quite probably a strain for my older smartphone. Since it's mostly for my own use, I don't care at all about Edge, but it got me to thinking and led to this question.
Now about the "There's no such thing as a stupid question" thing. My last accepted Ask Slashdot question was trying really hard for stupid. Though it triggered a pretty long discussion it was of limited interest and I feel sort of obliged to apologize for it. Especially since the question was mostly answered in the first comment and I should have figured it out on my own, too. Will it help to blame Microsoft again? (As I type into a Windows 10 box (in spite of having plenty of other OSes available on various boxen around here).)
I don't. (Score:2)
If I test I avoid the quite erratic variations that Javascript can create as much as possible and resort to HTML and CSS Validators.