uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions

Re:uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions by arca_vorago on Wednesday August 09, 2017 @11:31PM (#14976108)

If people would focus on content in HTML and CSS for layout and newfad devs weren't shoving 50 jscripts a page down our throat this wouldn't be happening as bad. I plan to make all my future sites librejs compatible, and forgoe js altogether whenever possible.

[ Parent | on HN ]

Re:uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions by arkh on Thursday August 10, 2017 @03:51AM (#14977374)

History keeps repeating.

Flash? Now you have heavily javascripted "website".

Table layout? Now you have bootstrap and friends.

Progressive enhancement? Fuck that, we don't have time.

And 5 years from now people will rediscover those and accessibility. Then 5 years later another kind of hell will have appeared to replace this.

The only big change for the current wave is that everything is obfuscated so it's harder for a newcomer to learn by checking how people coded things.

[ Parent | on HN ]

Re:uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions by edgartaor on Thursday August 10, 2017 @02:14AM (#14976934)

How this could be done if your backend it's a REST API?

[ Parent | on HN ]

Re:uBlock Origin Maintainer on Chrome vs. Firefox WebExtensions by yjftsjthsd-h on Thursday August 10, 2017 @07:13AM (#14978489)

You can still render server-side, an with a REST endpoint it should be easy to do so.

[ Parent | on HN ]