|
|
|
|
|
by nonrandomstring
1533 days ago
|
|
We used to have this concept in software engineering, called
"coupling". Dependency or independence of each module greatly
determines the quality and reliability of the overall system.
Generally, too much coupling is bad. But you can also use
inappropriate coupling, where even a little is bad. This is an
example of inappropriate "external control coupling" (where js code is
being chenged remotely - am I wrong?) arising where light
data coupling (where data only is pulled in) is required. The "web" has been going to hell in this way for a decade at least,
because it ceased to have boundaries. Without boundaries there cannot
be responsibility. Widespread introduction of JavaScript created a
quite different kind of technology from the WWW in which concepts of
client-browser and document-server made any sense. Minus any reliability/security it can't be considered safe for
delivery of important materials now. If even the site owner can't
trust what you see on a site that's bad (though as people point out,
we've had this even since banner ads) But it's why I think the future
of critical "information services" (as opposed to e-commerce / social
media) is on something like Gemini. |
|