this post was submitted on 20 Aug 2025
492 points (98.6% liked)

Technology

74265 readers
4217 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

Published earlier this year, but still relevant.

you are viewing a single comment's thread
view the rest of the comments
[–] vacuumflower@lemmy.sdf.org 5 points 6 hours ago (1 children)

In the 90s "web" was about knowing FTP, HTTP and HTML. Should have stayed this way. Scripts in browsers were a mistake.

[–] grrgyle@slrpnk.net 2 points 5 hours ago (1 children)

I blame social media and this perverse need to display notifications instantly. Technically very interesting problem to work on, but basically useless to a customer.

We had a button for that, on demand - it was called F5

[–] vacuumflower@lemmy.sdf.org 2 points 3 hours ago

I remember that those were used for games like Travian (displaying time and resources), dynamic content (like blasting music on a webpage) and web chat (that's what I blame the most, because it was in demand).

Well, they didn't do that, but I can imagine another "standard and convenient" way could have been taken to add realtime notifications to a webpage - a set of tags for displaying messages of an IRC channel, sending a message to an IRC channel, and so on, with maybe associating actions (going to an URL? or maybe updating part of DOM, but without full agility of JS, just add/remove/replace tag by id) with events. Like refreshing a page on a message in the channel, but no more frequent than N seconds.

Combined with iframes (I'll admit I consider iframes a good thing, burn me at the stake), this could give you a pretty dynamic experience.

IRC is, of course, not secure, but maybe if such functionality were present and if it became popular, IRC over SSL would become normal earlier too.

Or maybe something like WS could have been standardized far earlier. For pushing events to client.

I agree about F5, but the effect of realtime changes was psychologically very strong.