Dude's gonna wonder why he had a sudden 6500% jump in traffic.
18-year-old personal website, built with Frontpage and still updated
161–170 of 487 posts
Re: 18-year-old personal website, built with Frontpage and still updated
#162does anyone know what year the tag became depreciated? I’m surprised my iPhone renders it
Re: 18-year-old personal website, built with Frontpage and still updated
#163These simple sites show us something profound: If you want something to last, don't base it on something that won't last. There are a some technologies that will never allow somebody to build a site and leave it unchanged for 20 or 25 years. Cold Fusion comes to mind. Almost nobody hosts it anymore for one. Can you imagine running the same WordPress version for 25 years? The version of PHP it runs on will be EOL long…
> If you want something to last, don't base it on something that won't last. and > I guess what I'm saying is that if you want to build a site to last 25 years without numerous redesigns, build a static HTML page. While simplicity is a great way to future proof things, I'm not convinced that this argument in general would work nearly as well without the benefit of hindsight. One could be forgiven for confusing it wit…
My text files still work. I have MUD design documents from when I was in high school (mid to late 90s). Org mode and Markdown are kind of eternal formats. Even if all the tooling dies, they still look decent. Basic HTML still works well enough as well. You can write a parser for XML pretty easily. HTML can also be processed and rendered trivially. I think we could collectively find some other technologies that are likely to be around in another 20 years. The simpler the file format the more likely it is to be around :)
edit: A few more popped into my head. CSV. SQL schema + Data dumps (text format). The common theme to everything here is plain text. SQLite, although binary, is probably close to eternal. Git is eternal enough (recent HN post showed even POSIX shell is good enough to write a basic git client). JSON is easy to write a parser for as well. YAML.
Re: 18-year-old personal website, built with Frontpage and still updated
#164http://explorermag.com/ My 21 year old site focuses on Windows NT and the upcoming Windows 2000 release. Back when MSFt focused on operating systems. Billg still in charge!
This really takes me back, in a good/nostalgic way. That 3 column layout with a header on top was the go-to layout for content heavy sites.
Re: 18-year-old personal website, built with Frontpage and still updated
#165Earlier quoted context omitted.
You say that as if it’s weird to call an iPad a mobile device. Would you say that a tablet is not a mobile device? What do you define as mobile device, and what devices would you use to determine if a web site is “mobile friendly”? The common definition of mobile device is phone or tablet. The common definition of laptop is computer. These despite the fact that phones and tablets are computers and despite the fact th…
Does that definition matter if tablets are probably less than 1% of all mobile devices?
Why Google something for two seconds when you can just speculate wildly? Tablets are almost 10% of mobile sales via my first search hit https://www.zdnet.com/article/smartphone-market-a-mess-but-a...
The question of whether definitions matter when one sub-category or subset is a minority or majority... I’m not sure how to answer that. Why would a definition stop mattering just because something different is a small subset? I must assume that a categorical term includes everything in the category. If you don’t mean everything in the category, then don’t use the term that refers to the category. If you mean phone, then say phone. ?? Right? I’m confused why you would argue anything else.
Re: 18-year-old personal website, built with Frontpage and still updated
#166These simple sites show us something profound: If you want something to last, don't base it on something that won't last. There are a some technologies that will never allow somebody to build a site and leave it unchanged for 20 or 25 years. Cold Fusion comes to mind. Almost nobody hosts it anymore for one. Can you imagine running the same WordPress version for 25 years? The version of PHP it runs on will be EOL long…
While this website still works fine, the actual HTML that Frontpage generated isn't exactly easy to maintain if Frontpage stops working for whatever reason.
The author of this website is basically stuck using whatever version of Frontpage supports the markup of his website. And I bet there have been plenty of people who used who are no longer able to maintain their website because their editor no longer runs on their system.
Re: 18-year-old personal website, built with Frontpage and still updated
#167These simple sites show us something profound: If you want something to last, don't base it on something that won't last. There are a some technologies that will never allow somebody to build a site and leave it unchanged for 20 or 25 years. Cold Fusion comes to mind. Almost nobody hosts it anymore for one. Can you imagine running the same WordPress version for 25 years? The version of PHP it runs on will be EOL long…
This is the internet as I remember it.
Re: 18-year-old personal website, built with Frontpage and still updated
#168Earlier quoted context omitted.
100 points on pagespeed is not that hard with static sites. - 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.…
Don't know about PWA. Service workers are pretty lightweight and help with caching. But yeah, lazy-loading, infinite scroll, etc., are all designed to cover up design flaws that impact performance. I think lazy-loading can be potentially done right, but almost none of us do anything right. > use EM or % as layout width/height Why? EM/REM is good for handling font sizes, but for anything else it may not make sense and…
> Why? EM/REM is good for handling font sizes, but for anything else it may not make sense and a custom font setting in the browser can break layouts if the size of boxes are based on font sizes. PX is perfectly adequate for layout, and is actually a relative unit(PX !== hardware pixel). Same for borders, padding, margin, etc. Even REM is better than EM for most cases. People who adjust the font size in their browser don't necessarily want their layout to change and potentially degrade as a result.
I had a lot of bad experience with px, but it is true that for borders it's the only reasonable choice.
REM is not that well supported, especially in awkward browsers (Dillo, for example).
Imo EM is nicer for padding/margin; it keeps the text/layout ratio even if the font is resized, unlike px.
But point taken, it cannot be used as the only unit.
Re: 18-year-old personal website, built with Frontpage and still updated
#169These simple sites show us something profound: If you want something to last, don't base it on something that won't last. There are a some technologies that will never allow somebody to build a site and leave it unchanged for 20 or 25 years. Cold Fusion comes to mind. Almost nobody hosts it anymore for one. Can you imagine running the same WordPress version for 25 years? The version of PHP it runs on will be EOL long…
There is an obscure search engine called wiby.me that only indexes pages like what is posted here. I used to design websites in the late 90's, and very much miss the simple HTML pages of yore.
Re: 18-year-old personal website, built with Frontpage and still updated
#170There is a search engine dedicated to finding "classic" websites:
Click the "surprise me..." link to see a random one.