18-year-old personal website, built with Frontpage and still updated
61–70 of 487 posts
Re: 18-year-old personal website, built with Frontpage and still updated
#62https://developers.google.com/speed/pagespeed/insights/?url=... 100 Points. Mobile First. Better than React Native.
Re: 18-year-old personal website, built with Frontpage and still updated
#63My favorite like this site is http://www.burger.com - this dude has a hilarious array of hobbies and awesome beveled button links.
Re: 18-year-old personal website, built with Frontpage and still updated
#64Re: 18-year-old personal website, built with Frontpage and still updated
#65One of the most prolific and well-known music reviewers - Pierro Scaruffi - has a website built in 1995 with a design not updated much, or at all, since: https://www.scaruffi.com
Re: 18-year-old personal website, built with Frontpage and still updated
#66https://developers.google.com/speed/pagespeed/insights/?url=... 100 Points. Mobile First. Better than React Native.
Re: 18-year-old personal website, built with Frontpage and still updated
#67Re: 18-year-old personal website, built with Frontpage and still updated
#68https://developers.google.com/speed/pagespeed/insights/?url=... 100 Points. Mobile First. Better than React Native.
This is hilarious! Turns out 18 year old websites were mobile friendly after all
Re: 18-year-old personal website, built with Frontpage and still updated
#69Re: 18-year-old personal website, built with Frontpage and still updated
#70Earlier 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.
User agents already can ignore css and have user defined stylesheets and even JavaScript. None if this is new and it's a failure of our profession that that is abnormal and produces spectacularly poor results for users.
It's really frustrating when two browsers implement important parts the spec differently and push website developers to work around the behaviour one browser or the other with browser-specific code. It doesn't lead to sites being rendered differently as developers embrace the variety of user agents. It leads to people adding "This site is best viewed in Netscape Navigator" gif or "This application requires Chrome" on log in pages. Those are bad things.