|
|
|
|
|
by layer8
852 days ago
|
|
There is no good reason that this kind of content would need any client-side logic. Not being able to view it with tools like w3m is an unnecessary limitation. It’s also ironic that the one thing HTML was designed for, namely presenting static content, is now deemed unworkable without having to run custom client-side code. |
|
One such reason might be that it allows the developer to host their frontend statically, which usually is much simpler to set up and operate.
I would find it fair to appreciate that the author provides their service for free to the world. So while it might be true that their website isn’t fully compatible with certain client-side tools, that kind of support doesn’t come for free, and it also may not align with the goals of the author. (Which in this case apparently are educational ones, and not to maximise accessibility for a broadest-possible audience.)