2 ms·
and people choosing to write desktop apps in HTML + JavaScript/TypeScript + some framework. While the "web everything" trend is definitely responsible for a lo
by userbinator 4y ago
and people choosing to write desktop apps in HTML + JavaScript/TypeScript + some framework.
While the "web everything" trend is definitely responsible for a lot of the bloat, it is upon closer inspection not the whole story. For example, I remember various "AJAX chat" clients were quite popular around the turn of the century, worked in a browser like IE5 on a system with probably 64-128MB of RAM and a single core Pentium II/III, and you could also do other things like listen to music, play flash games, or read other sites at the same time. Those clients loaded relatively quickly over connections with bandwidth measured in KBps, and I don't recall much in the way of complaints about their resource usage.
- seszett 4y agoThey still exist. A small corner of the French free software community uses "tribunes" to communicate, and that was developed a bit before 2000. It consists of a web interface (originally not Ajax) and a standardised protocol supported by a handful of clients (most of which can federate multiple tribunes). It was briefly popular outside this community when I wrote a Drupal module that provided a tribune for any Drupal site, but then the modern web and smartphones happened and today it's really confidential. I still use it though, and the graphical client running on my system (which is also an RSS reader) uses 23 MB of RAM at the moment, displaying 1375 messages.