4 ms·
Yes! Web development is "weird" because we (developers) are basically constantly trying to put square pegs into round holes. Over the past ~25 years, a document
by icedchai 7y ago
Yes! Web development is "weird" because we (developers) are basically constantly trying to put square pegs into round holes. Over the past ~25 years, a document delivery system has been perverted into a application delivery system. The underlying, fundamental technologies were not intended for "UI" app development.
- krapp 7y ago99% of those "apps" are still just documents with client-side rendering, though. And the web was designed with the intent of running code practically from the beginning, albeit with support envisioned for multiple languages, so programmatic elements in a website aren't really a perversion of the original intent.
- pgcj_poster 7y agoI didn't know that. Is there anywhere I can read about it?
- krapp 7y agohttps://eager.io/blog/a-brief-history-of-weird-scripting-languages/ https://eager.io/blog/a-brief-history-of-weird-scripting-lan... mentions support for multiple languages, including TCL. And the possibility of scripts is mentioned at least as far back as HTML3[0] in 1996, with the script tag being added as a placeholder element in HTML 3.2[1], and Java applets were already supported. So while it wasn't there at the very beginning, it's clear the architects of the web didn't consider running code in the browser to be antithetical to its purpose. [0]https://www.w3.org/TR/WD-script-960131.html https://www.w3.org/TR/WD-script-960131.html [1]https://www.loc.gov/preservation/digital/formats/fdd/fdd000478.shtml https://www.loc.gov/preservation/digital/formats/fdd/fdd0004...
- rswail 7y agoThe original thesis on REST by Fielding [1]. Section 5.1.7 Code On Demand [1] https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding_dissertation.pdf https://www.ics.uci.edu/~fielding/pubs/dissertation/fielding...
- romaniv 7y ago>And the web was designed with the intent of running code practically from the beginning This is absolute nonsense. In the beginning the web didn't even have inline images. It was a text-only protocol. https://www.wired.com/2008/09/history-of-img-and-embed-tags/ https://www.wired.com/2008/09/history-of-img-and-embed-tags/ Cookies and script tags were hacks added by Netscape, IIRC.
- krapp 7y ago>This is absolute nonsense. In the beginning the web didn't even have inline images. It was a text-only protocol. Maybe you misinterpreted my comment. "practically from the beginning" does not mean the same thing as "from the beginning." I think something that was considered to be a part of the HTML spec, regardless of how it came about, since the 1990s counts as "practically from the beginning." >Cookies and script tags were hacks added by Netscape, IIRC. Tim Berners-Lee didn't seem to have a problem with the premise of embedded scripting in HTML in 1992[0], albeit not with the script tag and JS per se. And my comment was more referring to whether or not executing code in a browser was considered a legitimate use of HTML and the web at the time - and clearly it was, albeit not universally. That paradigm wasn't something Netscape just "hacked" in and entirely forced upon an unwitting web. [0]http://1997.webhistory.org/www.lists/www-talk.1992/0064.html http://1997.webhistory.org/www.lists/www-talk.1992/0064.html
- pjc50 7y agoThe web is "weird" because it's not a platform with a monopoly owner, but the place where platform would-be monopolists fight. Microsoft had a go with ActiveX and lost. Then came back with IE6's incompatibilities and lost again. Adobe had a longer go with Flash and lost. Sun kind of tried with Java applets. Now we can see the two big vendors Google and Apple trying to slip in features that help their apps or platforms. This is partly why some people worry about the dominance of Chrome; once it's totally dominant, Google can e.g. interfere with adblockers without worrying about losing users to the competition.
- mxuribe 7y ago> ...a document delivery system has been perverted into a application delivery system... I love it; this is great! I imagine somewhere in the world today, a witty instructor is teaching a computer basics or CIS 101 course and using something like your phrase above as the definition for the term "world wide web". lol :-)
- 0x445442 7y agoYeah, the main problem web apps were meant to solve was the delivering of a client and keeping that client up to date on the desktop. This was during the era where most client software was delivered on disk in a shrink wrapped box. But shortly after that software like iTunes essentially solved the problem. This is borne out by the fact that most users don't have a problem installing or keeping up to date the browser which is required for all these web apps. And of course there's phones, phablets, tablets, chromebooks and the like where it's essentially all client apps.
- gambler 7y ago>Over the past ~25 years, a document delivery system has been perverted into a application delivery system. ...and a protocol for inter-object communication. That's probably the most important part, because that's what creates most of the complexity and security holes today. There is no end to this in sight. Alan Kay warned web developers about this in 1997: https://www.youtube.com/watch?v=oKg1hTOQXoY https://www.youtube.com/watch?v=oKg1hTOQXoY Nobody listened. The majority of web devs still don't get it. (Can't wait for the arrogant replies here.) We ended up reinventing and re-implementing "internet objects" in the shittiest way possible.
- deleted 7y ago[deleted]
- zmix 7y agoI wonder, why you folks do not * build your own runtime * running in your own window * using your new protocol * using a sane UI language Because the way it is now, the document centric web well may be destroyed, sooner or later by trying to fulfill more and more non-document needs. And we know, how that goes: where the money is...
- ratww 7y agoI think the document centric ship sailed around 1993 when HTML forms became a standard.
- theandrewbailey 7y agoI think it was somewhere between the introduction of Javascript, browser plugins, and/or XMLHttpRequest.
- zmix 7y agoI disagree. Nobody said, a document can not be "interactive". With new technologies, old terms expand. What I am talking about is the total applification of the web, as it happened in the last decade.
- taffer 7y ago> document delivery system has been perverted into a application delivery system The Web is much more than a document delivery or archiving system, it is hypertext and the boundary between hypertext and apps is fluid. Is Wikipedia an app or a collection of articles? Is HN an app or a collection of comments and links? There is no precise boundary. When Berners-Lee invented the Web he was heavily inspired by Hypercard [1], an app development kit based on linking cards together. Web development is "weird" because the web tries to be device- and platform-agnostic. The web works on large widescreens, laptops, smartphones, in text mode or on a Braille display. Other technologies that have been used to develop UI apps from the beginning, such as Adobe Flash, assume that the display is a kind of fixed screen on which you can draw, with little or no accessibility and linking in mind. [1] https://en.wikipedia.org/wiki/HyperCard https://en.wikipedia.org/wiki/HyperCard
- icedchai 7y agoThere is no precise boundary, you are correct. However delivering a blob of minified, obfuscated Javascript code that renders the entire UI is obviously an "app", not a document. Web stuff that does entirely client side rendering is an abomination, IMO.