4 ms·
Because I can. Because I like them. Because I believe in Any Browser. Because of retro-computing. Because with every known scenario I cover, several more un
by forgotmypw17 6y ago
Because I can.
Because I like them.
Because I believe in Any Browser.
Because of retro-computing.
Because with every known scenario I cover, several more unanticipated ones are also covered.
Also, yes, I can imagine being limited to a particular older version of a browser, NN 2.0 included.
Because it's fun as heck.
Because I'm fucking tired of browser monoculture and I want the Web to be compatible again. If I, one determined developer, can make it work in Mosaic, IE3, Netscape, Opera 3 and 12, Lynx, Links, Dillo, Netsurf, w3m, PaleMoon, Waterfox, Google Translate, and yeah, with some grinding, Chrome, with and without JS, hopefully some devs out there feel embarrassed for their code and try a little harder...
- ssijak 6y agoWhy would anyone ever be embarrassed that their code from 2021 is not working on IE3 or Netscape?
- KaiserPro 6y agowhy would a watchmaker be embarrassed for not polishing the inside of a case that only the watchmaker can see?
- forgotmypw17 6y agoBest answer I've seen :)
- ssijak 6y agoIt is false analogy.
- forgotmypw17 6y agoCan you explain what is false about it?
- DC1350 6y agoBecause the standards you’re building against are arbitrary and just made up by other people. I can make a browser that crashes when it encounters a <div> tag. It’s a shitty browser. Will you feel bad when your stuff won’t work on it?
- forgotmypw17 6y agoYou're describing something purposely made non-functional, while I am building against software widely distributed and still occasionally encountered in the real world, hardly arbitrary.
- DC1350 6y agoDo you test for compatibility with the Wii and Nintendo DS browsers?
- forgotmypw17 6y agoI have not yet, but I would like to. If you can help, I would appreciate it. Due to the wide variety of scenarios and configurations I already have tested with, I think it would be more likely than not that I'd be able to complete my base features test script with few issues. Your question is a perfect example of why I go so far with testing.
- DC1350 6y agoOk. I tried to make fun of you but you’re still friendly so I’m curious. Do you mind if I ask what kind of stuff you’re maintaining where you see any traffic from these old browsers? Do you think it would ever be possible to transpile a site into some shared common set of syntax/features/whatever instead of making browser specific corrections? And what do you think about features like WebGL which are impossible to replicate on older browsers in a performant way?
- 6y ago
- KaiserPro 6y agoIts not really. This person obviously takes great pride in making their websites uber compatible. It takes great skill and effort to do this. Sure its a little batshit, but I applaud the level of perseverance that goes into it. I might have a different view if I was trying to ship something to a specific market segment in a hurry. However I'm not, and it pleases me immensely to see people do such silly[1] (and I mean this with the greatest of respect) things. [1] For reference, adding chamfers and geneva stripes under things like the main barrel, is utterly silly. However, should I be paying >£50k for a watch, I full expect that _every_ inch of that watch is going to be a masterpiece of finishing (reference: https://www.crownwatchblog.com/how-it-works/finishing-school-six-key-movement-finishes https://www.crownwatchblog.com/how-it-works/finishing-school...)
- forgotmypw17 6y agoWell, maybe not IE3, but I think it is embarrassing to deny access to, e.g. a five-year-old device with no upgrade path. Many devs are out of touch with the world where people can't afford a new one. I don't buy the security argument either, it's often just information access which is limited.