71–80 of 487 posts
Earlier quoted context omitted.
This is hilarious! Turns out 18 year old websites were mobile friendly after all
Have you actually tried the site on a mobile device? It's impossible to read the text and navigation is hell. Wouldn't classify that as "mobile friendly".
My personal/hobby business web site ( https://www.rlvision.com ) is based on code 22 years ago. It's built with tables, because that's how you did things back then. The age shows. But I haven't found reason to rebuild it yet. Simply put, it works. It may not be mobile friendly, but the goal is to make available my Windows software, so my aim is desktop users.
My favorite like this site is http://www.burger.com - this dude has a hilarious array of hobbies and awesome beveled button links.
Have to wonder how much that domain name is worth...?
https://godaddy.com/domain-value-appraisal/appraisal/?checkA...
Had I stayed with FrontPage, my life might have been simpler - porting 20 years of content is not simple - but I would have missed out on learning a lot of HTML, CSS, PHP, Python, MySQL, character set conversion, MySQL vs UTF-8, etc.
It's impressive the amount of content inside! There are countless pages about literature, religion and physics. It's a good reminder of the original goal of WWW: share information.
That is what I miss the most about the old web. We wanted to build something better by sharing knowledge. And for a while we did. Then mainstream came and corporates took over.
Earlier quoted context omitted.
There are a ton of attributes in the HTML that dictates how the website should render - it has a bgcolor and a margin on the body tag, a width and height on the main table, center tags all over the place, etc. Suggesting that a browser should ignore the HTML spec and do something else would completely destroy the web.
On the other hand, reader mode suggests that sometimes ignoring the way the site wants to be presented is a good thing.
Here’s an archive link in case this gets hugged to death: https://web.archive.org/web/20200214134509/http://www.fmbosc...
My personal/hobby business web site ( https://www.rlvision.com ) is based on code 22 years ago. It's built with tables, because that's how you did things back then. The age shows. But I haven't found reason to rebuild it yet. Simply put, it works. It may not be mobile friendly, but the goal is to make available my Windows software, so my aim is desktop users.
https://developers.google.com/speed/pagespeed/insights/?url=... 100 Points. Mobile First. Better than React Native.
- drop 99% of the JS (PWA, lazy-loading, infinite scroll, jquery, you don't need any of them for a webpage), convert the remaining for 1% to vanilla js and use it as progressive enhancement.
- use EM or % as layout width/height
- inline css, js, and svg
EDIT
- no webfonts!
The only thing that'll remain as an issue are tables wider, than viewport, on mobile.
My site: https://developers.google.com/speed/pagespeed/insights/?url=...