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

361–370 of 487 posts

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

#361

Post by scarface74 »

criley2 wrote: post #352
scarface74 wrote: post #280

Earlier quoted context omitted.

A quick Google search for running PPC Mac software under emulation. https://www.thefreecountry.com/emulators/macintosh.shtml#pow... For the most part yes. If you want to run Mac software you need to own Mac. As far as going back 30 years. Now you’re in the Classic Mac era. There are plenty of cross platform emulators that run Mac software that old. If you want to go back 40 years. Apple // emulators are a dime a doze…

That's fair, but this was about virtualization not emulation. Similar but different, but that's certainly a solution too.

If the current version of OS X was backwards compatible with 10.0 - 10.4. It would still need both a PPC emulator and a 68K emulator since iOS 9 still had 68K code.

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

#362

Post by scarface74 »

virtue3 wrote: post #356
scarface74 wrote: post #329

Earlier quoted context omitted.

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…

https://en.wikipedia.org/wiki/Carbon_(API) "Carbon was an important part of Apple's strategy for bringing Mac OS X to market, offering a path for quick porting of existing software applications, as well as a means of shipping applications that would run on either Mac OS X or the classic Mac OS. As the market has increasingly moved to the Cocoa-based frameworks, especially after the release of iOS, the need for a port…

So, what exactly did you say they refuted anything I said?

The Carbon API was 32 bit only and was supported until the latest release of MacOS.

Do you realize how many deprecated end of life frameworks that Microsoft has been lugging around for decades?

So should Apple have kept support for 68K software in 2019?

Also, do you realize that for all intents and purposes the entire .Net Framework is deprecated and EOL except for minor compatibility updates?

There are plenty of “pissed” .Net Framework developers who feel abandoned by MS.

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

#363

Post by jimhi »

giantrobot wrote: post #273
tasuki wrote: post #184

Earlier quoted context omitted.

I've been running a WordPress blog since early 2006 with very little maintenance. I'm sure it's all outdated again, but still appears to work.

If you haven't been keeping the WP back end up to date it's not functionality that's a problem it is security. Unpatched WordPress installs account for a huge portion of malware distribution. There's a number of exploits that allow attackers to upload files to your server. So they upload malicious payloads that exploits then download to infected systems.

Most of those exploits are from plugins. If they aren’t using those they can also change the default login url. Also Wordpress lets you export and reimport to current versions without coding. I think it’s one the best future proof platforms, most of the web still runs on it.

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

#364

Post by quink »

usrusr wrote: post #304
scarface74 wrote: post #231

Earlier quoted context omitted.

You haven’t tried to run 16 bit software on 64 bit Windows have you?

And so the mystery of why a 32bit version of Windows 10 still exists is solved. What's mildly annoying is that much of the early 32bit Windows software came packaged in 16 bit installers. Office 97 would be such a breeze on modern hardware.

> https://docs.microsoft.com/en-au/windows/win32/winprog64/app...

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

#365

Post by generationP »

Santosh83 wrote: post #210
generationP wrote: post #200

Earlier quoted context omitted.

Can't you just keep editing the html in a text editor? Frontpage's generated html isn't that unreadable.

Presumably the author used a WYSIWYG editor in the first place because he is not a technical person, so for him/her to now not only learn enough HTML/CSS/javascript to turn to hand editing but to also understand Frontpage's noisy output would probably take enough effort that they might rather decide to shut down the site if they're not able to continue using Frontpage. Hiring a dev to redo the site is another option…

Nah, I don't think this is such a big deal. Adding a row to a table is much easier than creating a table from scratch. And Frontpage's output isn't that noisy -- I had to go through that experience myself. That said, my old Frontpage from 2005 (which I copied from Win XP probably) still works fine except for a warning it throws at start about not finding some registry value. I wouldn't want to use it any more (it doesn't understand CSS and screws it up), but if I wanted, I could.

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

#366

Post by dmje »

As I spent half a day trying to wrangle my way through some sass grunt compiler frontend bullshit just trying to update the colour of some links on a client website, I find myself nodding sagely again. In the early days you could view source, see what was going on, copy and recreate someone else’s site, learn a whole bunch of new stuff and actually get shit done. Now, it’s all JavaScript bullshit and 100k lines of css. It’ll last about a month before it’s out of date and replaced by the Next Big Thing. HTML, css, a sprinkle of JavaScript. That’s what’s proven to last.

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

#367

Post by jimhi »

znpy wrote: post #348
cameronbrown wrote: post #43

Earlier quoted context omitted.

"Webmaster" - I miss that term..

Ah, the time when you could actually "master" all the web technologies to keep a website up and running...

You still can. We sure make things more complicated than they have to be sometimes.

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

#368

Post by snowwrestler »

djsumdog wrote: post #247
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.

I mean .. it's just a static HTML editor at that point (maybe it does some includes/builds to simplify things). If you're just pushing out static content, you don't have to worry too much about outdated libraries and security issues, so long as the web server it's being served from is maintained and up to date.

"Dreamweaver Templates" was basically an early static site generator that made it really easy to design and include site-wide or section-wide elements.

Yeah you could always edit the individual files that it outputted, but in some cases people were using this system to manage sites with hundreds or thousands of pages. As recently as a couple years ago it was how the natural history museum in DC managed their site content.

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

#369

Post by scarface74 »

kome wrote: post #332
scarface74 wrote: post #229

Earlier quoted context omitted.

You realize that you’re talking about a FrontPage site. The very definition of building something on a technology that won’t last.

but look at the code... are modern website really better? i think that FrontPage did an awesome job there.

There were all sorts of FrontPage server side extensions to IIS that you could use to support your site if I am not mistaken.

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

#370

Post by bentcorner »

danielbarla wrote: post #96
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…

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

> exactly what properties of HTML make it so long lived?

I think we're thinking about this backwards. It's not anything inherent to HTML that make it long lived, it's that the code to parse static HTML is simple, it's more or less standardized and has stuck around for a long time.

Post reply on HN