Am 03.01.2020 um 20:13 schrieb Nathan Andelin <nandelin@xxxxxxxxx>:
I can't take the time to respond to everything in your post.
But thanks for the responses you actually did. Interesting insight!
The point is that when you have an architecture that supports outstanding response times, you can also create more robust user interfaces, as opposed to the dull, lagging user interfaces that one sees generally on the Internet.
I'm really not sure if this is an architectural issue (as in OS/Hardware-combination). If I'm using my LAN-local Mediawiki running in Vmware on an old AMD CPU based, comparably slow (power savvy) Linux system, it's still running blazingly fast in my local Browser (Safari on an 2012 Mac Mini). Render times are way under one second with average article size around 6 KiB and rarely embedded images. All coming from MySQL on the same host.
Most pages on the Internet suffer from embedded ads. And there are slow sites like eBay, even if it has become considerably faster in the last years.
Creating outstanding (aka: feels like a real application) UI in the browser isn't exactly easy, since a multitude of techniques must be mastered to enhance a technology which in it's very basic form suffers from the same issues as 5250 or 3270. Funny in a way, I think.
PGP-Key: DDD3 4ABF 6413 38DE - https://www.pocnet.net/poc-key.asc
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.