But is it still running on Cern/3.0, installed circa 1993. Ours is: $ nc www0.cs.ucl.ac.uk 80 HEAD /staff/m.handley/ HTTP/1.0 HTTP/1.0 200 Document follows MIME-Version: 1.0 Server: CERN/3.0 Date: Fri, 14 Feb 2020 17:02:59 GMT Content-Type: text/html Content-Length: 9185 Last-Modified: Sun, 16 Jun 2019 15:27:37 GMT It's running on Sun Sparc hardware from the same era, and has been in active use for all of those 27 ye…
18-year-old personal website, built with Frontpage and still updated
311–320 of 487 posts
Re: 18-year-old personal website, built with Frontpage and still updated
#312My personal site was posted on September 12, 1999, is still updated, and has no problems. It;s a static site that mostly uses straight HTML/CSS. There are a few scripts that generate pages, but generating HTML/CSS pretty easy. https://dwheeler.com . Geocrasher said: > 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. Yes. I don't get pai…
Re: 18-year-old personal website, built with Frontpage and still updated
#313Here it was: https://web.archive.org/web/20030908174016/http://www.benibe...
But in 2005, I made a complete redesign: http://www.benibela.de/index_en.html
The backend went through a few reimplementations. Individually made html files (with front page express or something), a template tool written in Delphi, another template tool written in Java, a complete XQuery interpreter written in FreePascal
Re: 18-year-old personal website, built with Frontpage and still updated
#314My father still updates his website with Frontpage (he had a recent 6 month outage because he inadvertently deleted the Windows XP vmdk on his system, but I recovered that for him recently.) He’s 75, and isn’t interested in converting or learning anything new at this stage. The funny thing is for years his home-made site was the top google hit if you searched for “hill's criteria” (See Hill's criteria of causation).…
Hmm, how do you manage to acquire a legal of copy of Frontpage (even Express) these days for your dad?
Re: 18-year-old personal website, built with Frontpage and still updated
#315Earlier quoted context omitted.
> the closest ancestor to MacOS X is System 7. How do you figure? System 7 was part of the Classic Mac OS line, the last of that line was System 9 (Mac OS 9). This was a proprietary kernel developed by Apple. Mac OS X is a Unix based OS derived from technologies they acquired from NeXT. To say MacOS X is an ancestor of System 7 seems completely nonsensical.
No MacOS X when it was originally released had parts from NextStep and parts ported from Classic MacOS including QuickDraw, AppleScript, QuickTime, some audio frameworks etc. The entire Carbon API was a port of classic MacOS APIs to make porting from classic MacOS to OS X easier. MacOS X was a combination of both. That was the whole brouhaha of why Apple ported Carbon APIS to OS X because major developers like Adobe…
I think you're just supporting the original assertion that Apple does not support things for very long. Does Software written for OS X v10.1 run on Catalina today without using 3rd party tools or emulators? Software written for Windows 95 still runs on Windows 10.
Re: 18-year-old personal website, built with Frontpage and still updated
#316Earlier quoted context omitted.
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…
Google controls the major web engine. I don't trust google to not deprecate parts of html over time because the new shiny is "better". I would rather maintain markdown generators which I can update to change the markup to whatever the latest google insists needs to work instead of rewriting all my documents. I'm currently tasked with writing a UI for a machine that has a 25 year expected lifespan before wear means it…
Re: 18-year-old personal website, built with Frontpage and still updated
#317Earlier quoted context omitted.
>> Greek. Amateur F1 driver. Technology enthusiast. Single parent. Liar. thats quite a conversation starter...
Yes, everyone always has lots of fun trying to spot the lies. Hint: "Liar" is the lie.
Re: 18-year-old personal website, built with Frontpage and still updated
#318Re: 18-year-old personal website, built with Frontpage and still updated
#319Here is a life-saver maintained by a 77 year young lawyer for a lot of public good: http://www.drtsolutions.com/ . Case laws against SARFAESI, an Indian law that expedites bank recovery for non-performing assets. He updates it manually in FrontPage even today!
Wow, that page is amazing! I hadn't seen the old Google logo in years: http://www.drtsolutions.com/drtqueries.htm The search widget doesn't even use an . Just a plain .
Sorry, not sorry.
Re: 18-year-old personal website, built with Frontpage and still updated
#320Earlier quoted context omitted.
> 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 that the right way to rephrase that is "use the right tool for the right job". How many blogs are powered by wordpress? How many of them can be replaced with a static gen? HTML has a lot of garbage, but at least it's very hard to break it.
and really it's that everyone uses browsers that still display text and such on the screen even if it's broken in several places.
This could change if google decided to stop showing pages with broken html - like them killing flash big cuts at a time.
I have turned several worpress based sites into static html with one of the static html making plugins - and that turned those tools into the right ones for those jobs. I think most WP sites can be converted and be just fine, most people don't add new posts to them regularly from what I've seen.