Re: [dev] Interesting Web Browser Decoupling Concept

From: <>
Date: Tue, 13 Jun 2017 09:55:27 +0000

On Sun, Jun 11, 2017 at 02:19:08PM +0200, Hiltjo Posthuma wrote:
> Coming back to the real practical world: until then I try to keep my (personal)
> HTML pages simple[5] and use as little Javascript as possible (no jQuery!).

A noscript web portal should be mandatory for the web sites which the services
they implement are reasonable to be provided through such web portal (at least,
the sites which provide critical services over internet).

If an essential aspect of your web portal is hard-dependent on only 1 line of
javascript driving a modern web engine, game over (a.k.a. you are f*cked).

basic xhtml with basic forms and file upload/download ensure the technical cost of
client programs stays in "reasonable" boundaries.
The real "hard" stuff in the web stack is in http and TLS where we have
Ofc, some internet sites do provide services which are hard dependent on a rich
GUI (I usually mention soundcloud). Those internet sites should provide a
minimal and simple web API, that to lower the cost of client program
implementation (and to foster credible alternatives, which is a _good_ thing).
But careful... many internet sites using OAuth as their auth API mandates often
the use of a modern web engine which defeats the whole purpose of having a web
API, namely to have platforms free of any modern web engine.
As I stated here before, fixing this hardly can be done in a "nice and gentle way":
  - either you contact the web devs, they understand and fix the issue (most of the time it's dirt cheap).
  - or they send you to hell and you have to go legal if the service is critical.
P.S. make the line size 80 chars :))
Received on Tue Jun 13 2017 - 11:55:27 CEST

This archive was generated by hypermail 2.3.0 : Tue Jun 13 2017 - 12:00:16 CEST