14

In 2013, the web development blog CSS Tricks ran a poll with a single question: “Is it useful to distinguish between “web apps” and “web sites”? Seventeen thousand people responded. 72% answered Yep. They are different things with different concerns. The remaining 28% answered Nope. It’s all just the web.

That question, circulated in different ways, has become a common refrain. Every few years it re-enters the web development zeitgeist. At the center, however, lies the same question: is the web divided? Is there one web meant for desktop-like applications and another meant for content. One web that serves, and another that creates.

In practice, it offers little more than a thought experiment, though a useful one. It can frame a moment of web development practice. Equally useful is tracing the conversation back to one of the earliest times the conversation cropped up, back to the history of DHTML and a company called Oddpost.

you are viewing a single comment's thread
view the rest of the comments
[-] cypherpunks@lemmy.ml 7 points 1 day ago

Weird this article doesn't mention Hotmail and RocketMail, which both had email client web apps in 1996.

[-] GenderNeutralBro@lemmy.sdf.org 4 points 1 day ago

I don't think anyone called those "web apps" though. I sure didn't.

As I recall, the phrase didn't enter common usage until the advent of AJAX, which allowed for dynamically loading data without loading or re-loading a whole page. Early webmail sites simply loaded a new page every time you clicked a link. They didn't even need JavaScript.

[-] cypherpunks@lemmy.ml 2 points 16 hours ago

I don’t think anyone called those “web apps” though. I sure didn’t.

As I recall, the phrase didn’t enter common usage until the advent of AJAX, which allowed for dynamically loading data without loading or re-loading a whole page. Early webmail sites simply loaded a new page every time you clicked a link. They didn’t even need JavaScript.

The term "web app" hadn't been coined yet but, even without AJAX I think in retrospect it's reasonable to call things like the early versions of Hotmail and RocketMail applications - they were functional replacements for a native application, on the web, even though they did require a new page load for every click (or at least every click that required network interaction).

At some point, though, I'm pretty sure that some clicks didn't require server connections, and those didn't require another page load (at least if js was enabled): this is what "DHTML" originally meant: using JavaScript to modify the DOM client-side, in the era before sans-page-reload network connections were technically possible.

The term DHTML definitely predates AJAX and the existence of XMLHTTP (later XMLHttpRequest), so it's also odd that this article writes a lot about the former while not mentioning the latter. (The article actually incorrectly defines DHTML as making possible "websites that could refresh interactive data without the need for a page reload" - that was AJAX, not DHTML.)

[-] dhalucario@social.doggoat.de 1 points 16 hours ago

@cypherpunks @GenderNeutralBro I started webdev around 2019, I always found it odd it's called XMLHttpRequest because we send JSON using it :D

this post was submitted on 07 Feb 2026
14 points (100.0% liked)

Technology

42145 readers
102 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 4 years ago
MODERATORS