Where can I find more sites like this
Try here https://wiby.me/ Hit the 'surprise me' link
18-year-old personal website, built with Frontpage and still updated
321–330 of 487 posts
Re: 18-year-old personal website, built with Frontpage and still updated
#322Its.So.Quick.
I love the speed of the page! And seemingly nobody is eavesdropping me.
Re: 18-year-old personal website, built with Frontpage and still updated
#323Earlier quoted context omitted.
Yes, everyone always has lots of fun trying to spot the lies. Hint: "Liar" is the lie.
Long time listener, first time caller: You're into auto racing?! Link some stuff?
No, it's a joke! Because it says "liar" afterwards. And the previous post was also a joke, ie that I was lying about being a liar, which is a paradox.
I am a below average driver, alas. I am Greek, though, and some would say that's more exciting!
Re: 18-year-old personal website, built with Frontpage and still updated
#324Earlier quoted context omitted.
> It's an interesting line of thinking though: exactly what properties of HTML make it so long lived? I've thought about this on and off for a few years. Here's what I've come up with: 1. Popularity. You can't really display anything in a web browser without it, blank pages with one AJAX script notwithstanding. 2. Ease of use. Open a text editor, type some markup, save the file with .html, and open in a browser. When…
I'd argue your #3 is wide of the mark. It's not that there's a well-defined open standard. It's that browsers will eat any old crap that's thrown at them and turn it into something plausible, if not precisely what the author intended or reader really wants. Yes, there's a standard, and yes it's open. It's observed far more in the breach, as a few minutes with a validator on well-known sites will demonstrate. Your com…
Even worse, the browsers could not handle standard html.
HTML was based on SGML and it has all the nice SGML features. Something like But then the browser never implemented it properly, so html5 just describes the behaviour of the browsers.
Re: 18-year-old personal website, built with Frontpage and still updated
#325Earlier quoted context omitted.
Is "EOL" the right term? They released a new version 2 days ago: https://trac.edgewall.org/wiki/TracChangeLog
I find it odd too that they did some minor releases, yet python 3 was not on the radar. End of life is correct. It is end of life since it doesn't run on current platforms. I am not sure if the latest distributions (Ubuntu, Debian, RedHat) have all removed python 2 packages. If not, it will be gone with the next major release. You're going to be in trouble to run software with no available interpreter, plus all the l…
> I am not sure if the latest distributions (Ubuntu, Debian, RedHat) have all removed python 2 packages. If not, it will be gone with the next major release
Red Hat has not. Ubuntu has not in its most recent stable release. Debian "unstable" is still using Python 2, so I don't think your statement holds up.
https://distrowatch.com/table.php?distribution=redhat
https://distrowatch.com/table.php?distribution=ubuntu
https://distrowatch.com/table.php?distribution=debian
Also, Trac developers ave been making progress on Python3 as recently as 8 days ago:
Re: 18-year-old personal website, built with Frontpage and still updated
#326These 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…
I don't think this is really unique to Web 1.0; certainly something that still works from the Web 1.0 days seems "impressive" just because of the passage of time, but there's probably some element of survivorship bias there. You mention ColdFusion as an example, but this guy's site is made using FrontPage. He didn't know in 2001 that he'd still be able to run FrontPage in 2020. He made a bet, and it paid off. Other people made similar bets, on other technologies, and unfortunately got it wrong.
My personal website uses Jekyll, and while there's always the possibility it would become abandoned and stop working (I've definitely found someupgrades to be a pain, and ruby tooling in general doesn't help either), I'll always have the simple, readable markdown files the site is based on. While this wouldn't be an option for a non-technical website author, if I really had to, I'm sure I could write a simple markdown->html renderer over a weekend (or a converter to transform it into the future format-du-jour).
Re: 18-year-old personal website, built with Frontpage and still updated
#327My 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?
The later versions "Sharepoint Designer" are free from Microsoft and still available on their downloads page.
Frontpage may be old enough to consider it 'abandonware,' a quick Google for "free frontpage" has a lot of downloads including one from Kean.edu with an embedded key.
Re: 18-year-old personal website, built with Frontpage and still updated
#328One made with Word and still updated: http://villemin.gerard.free.fr/
Re: 18-year-old personal website, built with Frontpage and still updated
#329Earlier quoted context omitted.
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 would disagree, most of what was brought from Classic OS was ported, adapted, out of necessity and short lived. OSX was an entirely new operating system that ported some frameworks and software but wasn't backward compatible. Were it so, they wouldn't have provided an emulator. 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.…
You call the Carbon API that existed from 2001-2018 “short lived”? The entire Carbon API was used to port software like PhotoShop and Office.
Carbon was a port of enough of the Classic API to port major important programs.
AppleScript is still built into the current version of OS X. It was introduced in 1993-94
And seeing that 10.1 was PPC only, do you expect them to keep a PPC emulator around?
Can you run PPC based Windows NT software today on an x86 PC?
Re: 18-year-old personal website, built with Frontpage and still updated
#330Earlier quoted context omitted.
My sense is that Markdown is probably pretty safe for most uses, particularly if you control the processing. If not, then yes, it can bite. For me that means pandoc to generate endpoints such as HTML, PDF, etc. I'm fairly confident that most of that toolchain should continue to work (provided computers and electricity exist) for another 2-4 decades. For certain more complex formatting, Markdown has limitations and fe…
I agree with you entirely on the abandoning of conventions with HTML. I haven't paid much attention to multi-column layouts in CSS over the years but my impression is that it's gone from tables to CSS floats to whatever CSS does now that I'm not familiar with. Browsers are typically backwards compatible so this isn't that big of a deal to me. But I have no idea if what's regarded as the best practice today will be se…
Semi-relatedly, I think even the linear form of UnicodeMath [1] is very readable, and it would be great if there was more support for building it up into nicer presentation forms in the browser wild (MathJax has had it on the backlog since at least 2015, for instance), as that seems to me to be a better "fallback" situation than raw MathML given its readability when not built up.
[1] http://www.unicode.org/notes/tn28/UTN28-PlainTextMath-v3.pdf
> I haven't paid much attention to multi-column layouts in CSS over the years but my impression is that it's gone from tables to CSS floats to whatever CSS does now that I'm not familiar with.
CSS Grid [2] is the happiest path today. It's a really happy path (I want these columns, this wide, done). CSS Flexbox [3] is a bit older and nearly as happy a path. Some really powerful things can be used with the combination of both, especially in responsive design (a dense two dimensional grid on large widescreen displays collapsing to a simple flexbox "one dimensional" flow, for example).
Flexbox may be seen as primitive in a few years, but Grid finally seems exactly where things should have always been (and what people were trying to accomplish way back when with tables or worse framesets). Even then, Flexbox may be mostly seen as primitive from the sense of "simple lego/duplo tool" compared to Grid's more precise/powerful/capable tools.