4 ms·
Just basic adherence to web standards I think is really the problem people have with these interfaces. Basic support for already existing web client functional
by kafkaIncarnate 5y ago
Just basic adherence to web standards I think is really the problem people have with these interfaces.
Basic support for already existing web client functionality. For instance, I shouldn't have to sacrifice the ability to open a link in a new tab, or sacrifice the ability to link _period_ which is commonly the case (which interferes with bookmarking, etc). I shouldn't be logged out or yelled at by an app for hitting the back or refresh buttons on my web browser.
Most of these things are reinventing the wheel. Just for prettiness they'll break a basic browser functionality, then they try to re-implement in their framework and it just creates an abstraction layer on top of an abstraction layer, creating unnecessary bloat.
Many times this is even just so they can show you a blog post, which is just text and some images. I shouldn't need JavaScript to see that, especially if I don't know you or trust you. Even Google AdWords has had malware injected in its JavaScript, a blogger is not going to be worth my time to read if I have to trust his code isn't malicious just to see what he has to say about an obscure fruit.