Live data from Hacker News

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

fmboschetto.it

91–100 of 487 posts

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

#91
post #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.

This website looks extremely familiar. I think I visited it about 15 years ago and I am not completely sure but didn't you have a nice drawing and photo editing software there? I can't remember the name of it but it was the best ever, until it was disappointingly discontinued because of lack of buying customers :(

Yes, ArtGem (https://rlvision.com/artgem_about.php). We were a couple of guys that tried at making shareware, but sadly failed. I continued running the site to host my own utilities, some of which eventually turned into shareware. I don't earn much money from it, but I enjoy making software and it makes me happy when other people find them useful as well!

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

#93

I'm surprised to see still exists and works in modern browsers. And saddened to see it updates at ~20fps, at least on Safari. Time for a smooth, GPU accelerated 60+fps marquee implementation?

Wait, how do the rest of you test if a field accepts or rejects html?

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

#94

My 23 year old web site: https://jgc.org/ It's still updated from a Perl script that generates static HTML.

I guess you have some sort of "classic car" feelings towards it? How often does the perl script get updated?

Whenever I need to update the site.

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

#95

These 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…

Fortunately there are plenty of static site generators. Frontpage is out of support and likely the currently popular generators will meet their end one day as well. But even then you can still run them in the future, and their output should not have any major issues (unlike a CMS which might get hacked if it's not kept up to date).

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

#96

These 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 with "guess the future correctly". Plenty of relatively safe bets from 10, 20, 30 years ago haven't panned out that well. It's an interesting line of thinking though: exactly what properties of HTML make it so long lived?

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

#97

These 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…

Use static HTML and javascript, I don't think they'll break js compatibility in a long long time, ES3 is still well supported and it's out in 1999.

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

#98
post #74

My personal favorite, which is in a similar vein - an Italian, although the site is in English; Frontpage; still updated - is https://www.luigicases.com/ . He makes leather straps and cases for cameras. Famous in the classic camera community. Only active site that I can think of that still uses frames.

Those pics tell a glamorous story worth of a movie.

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

#99

These 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…

I think you can generalise the advice: remove as many processing steps as you can.

It's not so much that you needed to guess that HTML was going to be as long-lived as it is, it's that HTML is the final product that actually loads on the users computer, and those tend to stick around for a long time (or at least be emulated). The code that lives on a backend server somewhere, not so much.

For what it's worth, I don't think this example is necessarily bulletproof: it requires a working copy of Frontpage. If Microsoft behaved more like Apple it might have been deprecated away long ago!

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

#100

I missed the tools like FrontPage/DreamWaver and gorgeous Flash websites.

Agreed. The modern-day version of those would be Scratch (https://scratch.mit.edu/) which kids use to start exploring coding, but it's not the same.
Post reply on HN