Live data from Hacker News

1999.io: Blogging like it's 1999

1999.io

21–30 of 113 posts

Re: 1999.io: Blogging like it's 1999

#23
post #20

Earlier quoted context omitted.

To edit a blog you have to enable JavaScript because the blogging software is written in JS. It would be possible to create a client that didn't, but that doesn't exist today.

You have to enable JavaScript (from fargo.io) to view posts (or at least to view the About page.)

The About page should NOT have required JS. That was a mistake. I'm going to fix it, but not tonight.

Here's an example of a blog post written in 1999.io.

http://scripting.com/2016/06/08/1311.html

You do NOT need JS on to read it, by design.

Re: 1999.io: Blogging like it's 1999

#27
post #13

1999? XML is our savior! The future of the web will be interconnected SOAP services! It's the year of the Linux desktop! Itanium will revolutionize software if someone would just make a sufficiently smart compiler!

That is funny. Considering Dave Winer's long history with hands on RSS, XML-RPC, (and his close seat to watch the disaster of SOAP)

Re: 1999.io: Blogging like it's 1999

#28
post #13

1999? XML is our savior! The future of the web will be interconnected SOAP services! It's the year of the Linux desktop! Itanium will revolutionize software if someone would just make a sufficiently smart compiler!

To be fair, the neat parts of SOAP, WSDL, still is pretty neat. XML is mostly hated because named closing tags make it stupidly verbose -- a big mistake. After that it was extra complicated which made platforms like PHP have crappy implementations, I guess.

But having to rewrite lots of boilerplate code for everyone's JSON or "REST" API is annoying. There's even projects to describe JSON schemas and APIs because that's actually useful. Maybe this time it'll be simple.

Transactions over SOAP (WS-AtomicTransaction I think) is also sort of neat I guess, but too complicated to be useful on the Internet?

Re: 1999.io: Blogging like it's 1999

#29

When I was blogging in 1999 it involved appending each new blog entry to the top of the html page which went in the content frame. And I don't think I'd heard of "blogging" yet.

Oh my god. Frames. The horror...

We used to append content into a single page because the alternatives were A) independent post files and a cgi script to concatenate them dynamically on each view, or B) re-create the static page from individual post files.

Since using a database was totally overkill, and static + individual posts wasted precious megabytes, and a new dynamic process per page load was way too CPU-intense, we just curated a single static page. Saves disk and CPU. When posts got past a certain number, the process'd do some juggling of content into a new archive file.

Re: 1999.io: Blogging like it's 1999

#30

If I have to enable javascript to view parts of your website at all, then it isn't anything like 1999.

To edit a blog you have to enable JavaScript because the blogging software is written in JS. It would be possible to create a client that didn't, but that doesn't exist today.

[deleted]
Post reply on HN