Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

fmboschetto.it

Post reply on HN
Print view View original

261–270 of 487 posts

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

#261

Post by cptskippy »

wolco wrote: post #224
randomdude402 wrote: post #196

Earlier quoted context omitted.

I know a person who is maintaining a few sites she built in like 2005 with a version of Dreamweaver a little older than that, so never dares to upgrade the Dreamweaver version. The whole thing is terrifying and horrific to me, but they keep paying her to do the work so she's fine with it.

You would just edit the html pages lol. I still use dreamweaver for the visual editor if I need to copy and paste from a pdf and want perfect html. No one has made anything like it. No current editor has a quick sftp that allows you to connect/edit move on.

Early versions of Dreamweaver were pretty slick. I used it as my primary IDE for developing ASP pages in early 2000.

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

#262

Post by user5994461 »

jahlove wrote: post #216
user5994461 wrote: post #198

Earlier quoted context omitted.

Trac has been end of life for some time. It doesn't run on python 3. There are open bug tickets about it that have been stale for years. Maybe it will be upgraded now that python 2 is officially dead, but given it wasn't so far and there was no effort in that direction, I wouldn't bet on it.

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 libraries in use are effectively abandoned.

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

#263

Post by Lucadg »

I learned Frontpage in 2000 in a King's Cross (Sydney) internet cafe where you paid 2 AUD for unlimited time...but you couldn't leave, not even to go to the toilet.

That html went straight to Geocities.

The feeling of power part of a minority of people who could actually publish something on the net was amazing.

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

#265

Post by SilasX »

jsaldes wrote: post #40
stabbles wrote: post #34

Earlier quoted context omitted.

This is hilarious! Turns out 18 year old websites were mobile friendly after all

Have you actually tried the site on a mobile device? It's impossible to read the text and navigation is hell. Wouldn't classify that as "mobile friendly".

What do you mean? It has reasonable column width so you can zoom in and out as necessary, often with a double tap. That is, it leaves it up to the client to adjust as necessary -- in contrast with the typical mobile site, which:

1) Forces a particular size/resolution, locking out zoom capabilities

2) Has a floating header with a constant size relative to your device screen, blotting out the same real estate no matter how much you zoom. And, of course, using the same header pixel height for portrait vs landscape, making the latter practically unusable.

Yes, this site is better than 99% of mobile sites out there.

Edit: Some further comments: It's generally better to have a site that obeys the standards and thus plays nice with any client, than one that locks you into the hip designer's meth-addled decision. This site in particular works well with my extensions like VimFX for clicking links from the keyboard.

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

#266

Post by SilasX »

matsemann wrote: post #253
Mirioron wrote: post #222

Earlier quoted context omitted.

I find HN to be one of the best mobile websites. It's fast and text isn't massively oversized. You can actually fit information on screen. Many mobile websites I've seen are horrible to use, because they have very poor information density and the sites seem to be designed for 4" or smaller screens.

I tried to upvote you about HNs great mobile design, but the buttons are so small I accidentally downvoted ;)

Then zoom in, which most "mobile optimized" sites prohibit.

My further comments: https://news.ycombinator.com/item?id=22328505

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

#267

Post by dep_b »

I really have a soft spot for these kind of sites. Often people have pretty interesting and unique content on this kind of websites. I always try to help by keeping things very simple to maintain but just a bit better, like making a PHP include of the menu and then replacing the top part on every page once.

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

#268

Post by btrettel »

dredmorbius wrote: post #242
btrettel wrote: post #225

Earlier quoted context omitted.

I appreciate your reply. Seems Markdown is more complex than I recognized and this just makes me want to avoid it more. If you do find the rant you mentioned, let me know. > HTML has ... proved less robustly stable over the 25+ years I've worked with it The first website I made in 2002 still views fine in a modern browser. I didn't do anything fancy, though. I would be interested in what has been unstable as it might…

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 seen as primitive in 15 years.

> The fact that there's no HTML-native footnoting / endnoting convention ... bothers me.

I've seen people use the HTML5 element for sidenotes, styled with CSS. Some even make them responsive, folding neatly into the text as the viewport shrinks. I'm not sure if this is the intended use for but the result is reasonable and I intend to do the same. If you're set on footnotes, though, yes, I don't know a native implementation.

Equation support with MathML is okay in principle but not practice. I'd like to have equations without external dependencies (MathJax's JS alone is like 750 kB!), but that's not possible until Chrome decides to catch up with Firefox and Sarafi on MathML. I've been thinking about just using MathML as-is (no external math renderer), and if Chrome users complain, I'll tell them to get a better browser. ;-) Maybe that'll help some Chrome users understand why they should test their websites in other browsers.

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

#270

Post by khana »

geocrasher wrote: post #90

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…

Yeah now to tell the Chrome devs to put their coding hands behind their back.
Post reply on HN