Live data from Hacker News

18-year-old personal website, built with Frontpage and still updated

fmboschetto.it

61–70 of 487 posts

Re: 18-year-old personal website, built with Frontpage and still updated

#64
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.

Re: 18-year-old personal website, built with Frontpage and still updated

#65
post #13

One 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

He even reviewed one of my favorites albums launched recently: https://www.scaruffi.com/vol8/bentknee.html

Re: 18-year-old personal website, built with Frontpage and still updated

#68

https://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

Just because mobile phones got same (or better) screen resolution than in 1990s/2000s desktop PCs

Re: 18-year-old personal website, built with Frontpage and still updated

#70
post #35

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.

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.

Users should be able to override the default behaviour of their browser if they want to, but the default behaviour should still be defined by the HTML spec rather than the browser vendor.

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.

Post reply on HN