Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

HTML5 feature request

Name: Anonymous 2010-05-04 15:43

Multi-document pages. I'm too lazy to check specifications.

Not just that server-side #include virtual bollocks, but some kind of <file location="/other/file.html" /> bollocks. I don't want shitty <frame>s. Nor do I want that javascript AJAX or whatever shit.

If images and stylesheets are kept in cache when they haven't changed, then why not (for instance) keep the 19 threads that haven't changed since your last refresh on /prog/? A whole 20KB every time seems a bit wasteful for what is essentially < 100 bytes of information.

Name: Anonymous 2010-05-04 15:58

s/HTML5/HTTP[sup[2.0[/sup]/i

Name: Anonymous 2010-05-04 16:08

>>1
A whole 20KB
Be glad some monkey decided to turn on compression, otherwise you'd be looking at 10 times that.

Nor do I want that javascript AJAX or whatever shit.
What you're asking for is literally one line of code. And it's useless. The HTTP request and reply headers would be larger larger than the actual thread data, and you'd make 18x more requests. Fucking stupid.

To solve this you need a full-blown HTML5 client application with custom refresh (think Gmail and friends).

Name: Anonymous 2010-05-04 16:28

lets face it HTTP and HTML is gay.

Name: Anonymous 2010-05-04 17:31

>>4
I've been saying that since the '90s. It was a fine thing while people were still calling it "Hypertext" but it was never intended as the layout/typesetting multimedia affair it has become. TEX was around by the time we seriously started trying to do this sort of thing, and at that time it would have made a lot more sense to make a networked hypertext out of it than follow the obscene evolution of HTML.

Name: Anonymous 2010-05-04 17:32

>>4
The ironing is delicious

Name: Anonymous 2010-05-04 17:49

Your a raging homophobe, faggot

Name: Anonymous 2010-05-04 22:18

>>5
TEX syntax is disastrous and barely works for its stated purpose of typesetting. It's also too focused on appearance rather than semantics, which makes it unsuitable for a hypertext replacement, given that the WWW is now accessed from many different types of devices (mobile phones, for example).

Name: Anonymous 2010-05-04 22:39

2010: Year of Gopher

Name: Anonymous 2010-05-04 23:25

>>8
TEX syntax is disastrous and barely works for its stated purpose of typesetting.
This is somehow different in HTML? At least TEX renders relatively consistently.

But I did mention extension. If hypertext hadn't been extended the way it has, it wouldn't be particularly useful on phones or anything modern. Without the bells and whistles, it's just a more or less flat format with hyperlinks. Try to keep in mind that TEX already subsumes the functions of hypertext at the stage I said should have been ditched in favour of TEX.

Name: Anonymous 2010-05-05 0:05

>>5,10
Tex is just a shitty hack. Everyone knows that for real typesetting, troff is the way to go.

>>9
There are no gopher clients for Android, J2ME, or even obscure platforms like Windows Mobile, Blackberry, or iPhone.

Name: Anonymous 2010-05-05 0:14

>>11
YET

Name: Anonymous 2010-05-05 5:55

>>11
Tex is just a shitty hack.
How dare you?

Name: Anonymous 2010-05-05 8:22

Name: Anonymous 2010-05-05 8:54

>>11
Tex is just a shitty hack.
Sure, maybe (not really.) No one has yet so much as contradicted the claim that HTML is at least as bad.

Name: Anonymous 2010-05-05 10:56

>>15
HTML is a worse and shittier hack

Name: Anonymous 2010-05-06 9:15

BBCode > TEX

Name: Anonymous 2011-02-03 1:43

Name: Anonymous 2011-02-04 14:33

Don't change these.
Name: Email:
Entire Thread Thread List