129 karma · joined August 9, 2014
I think when an essay from 20 (or 35) years ago claiming "X sucks" is referenced, it's kinda foolish not to draw attention to the history that followed.
That reads to me like "RCE if you have RCE". Which I guess is a fair description of the DLL vulnerabilities if you ignore the privilege-escalation parts.
The DirectShow and (perhaps) passwordless RDP vulnerabilities seem rather more severe to me.
How is that leader quote appropriate?
That depends on how you view Javascript.
If you consider it a programming language, the growing-up is a good thing. Making developers more productive and all that jazz. Of course, core WATs in JS are at a deep enough level that they're going nowhere (backward compatibility folks!), and anyone who's not already invested in JS should have the sense to look elsewhere.
If you consider it a runtime for delivering applications to the browser, it's really not so clearly a positive. A more complex language means more lock-in to existing runtimes, more room for bugs, more wasted engineering effort supporting the moving standard, less opportunity for lighter abstractions or more declarative assets amenable to static analysis ...
That's enough to get most "responsive" websites showing with no left margin at all, which looks fucking awful. Worse still, half the time I get a hamburger menu and mobile-style navigation!
Apologies for not adding anything to the conversation, I just had to rant about another web anti-pattern :(.
The context you are speaking in entirely determines the answer to this question.
Your context reminds me of "is there REALLY a difference between a 'list', an 'array', a 'tuple' and a 'vector'?", as different languages overload these terms with different (sometimes the same!) properties.
The OP seems to be taking a perspective embedded in operational semantics, where a non-halting, unspecified or incorrect "named callable" should not be properly called a procedure.
Personally, I find both kinds of hair-splitting semantic arguments a waste of time when they're isolated from the underlying question, which should be:
> what sort of conversation do we want to be having about these things? What notation or terminology is going to make that easier?
At least on Firefox. Chromium seems to respect the user a little more.
Pisses me off no end.
Nice characterisation, I might re-use that.
Surely somebody has done a study of this effect. In web and software design it's particularly hilarious (in an I-want-to-cry way) since so much good sense has been written (Tufte etc) which is completely discarded by these trends. I expect the same is true in architecture, only I'm less familiar with the literature of that domain.
* breaking established addressing conventions. Gmail (last time I used it) made it difficult to distinguish between To: and Cc:, both in received emails and when sending.
* messed-up quoting, and other broken conventions.
* the one that's been discussed to death here recently: it's on the way to impossible to send email and expect it not to be silently dropped if you're not on gmail.
* the email authenticity measures linked to the last point also screw up mailing lists and forwards. Most of the DMARC notifications I get from gmail now include a bunch of FAILs for people that forward from another domain to gmail. Soon, they'll simply stop receiving most mail.
Email is walking dead, and gmail is largely to blame.
This trend of design fashions negatively impacting usability has become so blatantly visible across the web (and apps, and desktop interfaces) during this century that I've become quite curious what psychological/organisational effects are at force.
Are there historical examples of the same tendency that can be examined? Tools, signage, forms or public spaces becoming a progressively more difficult and less usable mess under the aegis of "making things easier for users"?
"aspirational" is an optimistic way to describe it. As the article illustrates, every ~2 years the "pythonic" approach is different. Innovation is good, but it hurts re-use of code and of skills.
If you're on this site and haven't already been strongly reccommended to read Oliver Sacks, do so. Broader than neuroscience, look for memoirs of British surgeons during WWII.
http://www.tclcommunityassociation.org/wub/proceedings/Proce...
Instead of "this model fits the curve and sounds attractive and sciencey" it becomes "this model fits the curve and was done by computer!"
Not really the "empiricism coming to economics" that the author claims, but I guess it could support better outcomes. For a while.
But of course the OP continued to make the same mistake, which I pointed out way up at the beginning of this branch.
But I see I'm in the minority here, thinking software should be predictable and leave the user a sense of control, so feel free to disregard my opinion.
Even if the browser is providing your entire desktop experience, you should be able to switch applications or close them in a predictable way.
I get a nag screen when videos in the browser go full screen, telling me loud and clear that expected behaviour is changing and telling me how to get control back. When a website overrides keyboard controls, the first I know about it is when I can't scroll properly, or switch to another tab, or go back, or close the window that's yelling at me and making my machine thrash ...
Disruptively changing modes without notification violates fundamental rules of interaction design, affordances and basic security. How is that okay?
The workaround is typical of web stuff as well: deal with the symptoms one by one while leaving the underlying problem unquestioned.