Jargons of Info Tech industry

G

Gordon Burditt

HTML is designed to degrade gracefully (never mind that most web
authors and many browser developers don't seem to comprehend this), so
you don't really need a "subset" html to get the safety features you
want. All you need to do is disable the appropriate features in the
HTML renderer in your news and mail readers. JavaScript, Java, and any
form of object embedding. Oh yeah, and frames.

And links. And cookies. And any kind of external site or local
file access. And browser history.

Gordon L. Burditt
 
C

Chris Head

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

... and generally these "web based message boards" (i.e. forums I
assume you mean) have none of the useful tools that Usenet offers and
are much, much slower.
[snip]

Arrgh, I *emphatically* *hate* Web-based-(almost anything). Why, oh WHY,
would we subject ourselves to Web-based message boards and Webmail
services? When using a proper e-mail client, your bandwidth usage
consists of downloading your e-mail. When using a Webmail service, your
bandwidth usage consists of downloading the message, PLUS the entire
user interface. Additionally, a user interface operating inside an HTML
renderer can NEVER be as fast as a native-code user interface with only
the e-mail message itself passed through the renderer. I mean, the way
Webmail works, you're at the message list and click on a message to
view. This causes a whole new page, user-interface and all, to be
loaded. In comparison, that's like shutting down and re-opening your
e-mail program for every single message you want to view!

Why can't we use the Web for what it was meant for: viewing hypertext
pages? Why must we turn it into a wrapper around every application
imaginable?

....

</rant>

Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)

iD8DBQFDDoRR6ZGQ8LKA8nwRAvinAKCVi3Sfztpm3ILUk7TnunPJxBEVzwCguvAu
ME8mWt2eVNpPUckJ3NT39KY=
=TdTk
-----END PGP SIGNATURE-----
 
C

CBFalconer

Chris said:
.... snip ...

Why can't we use the Web for what it was meant for: viewing
hypertext pages? Why must we turn it into a wrapper around every
application imaginable?

Because the Lord High PoohBah (Bill) has so decreed. He has
replaced General bullMoose.
 
D

Denis Kasak

Mike said:
I see a difference between "X would be useful for A, B, and C" and "Y will
always be the only proper way."

Don't you?

Y would not be useful because of the bandwidth it consumes, the malware
it would introduce, the additional time spent focusing on the format
rather than quality of the content and, frankly, because it's useless.
As Rich already said, if one wants to look at neatly formatted content,
one can always visit the web. Usenet is meant to be an
information-sharing facility, and I cannot see *any* reason why it
should be exposed to all the disadvantages stated in numerous places in
thread to gain a pale "advantage" such as flashy content. We already
have a World Wide Web, no need to make Usenet it's clone.

-- Denis
 
J

John Bokma

Chris Head said:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

... and generally these "web based message boards" (i.e. forums I
assume you mean) have none of the useful tools that Usenet offers and
are much, much slower.
[snip]

Arrgh, I *emphatically* *hate* Web-based-(almost anything). Why, oh
WHY, would we subject ourselves to Web-based message boards and
Webmail services? When using a proper e-mail client, your bandwidth
usage consists of downloading your e-mail. When using a Webmail
service, your bandwidth usage consists of downloading the message,
PLUS the entire user interface.

Not necessary when using (i)frames + cache
Additionally, a user interface operating inside an HTML
renderer can NEVER be as fast as a native-code user interface with
only the e-mail message itself passed through the renderer.

Nowadays, more then futile.
I mean, the way
Webmail works, you're at the message list and click on a message to
view. This causes a whole new page, user-interface and all, to be
loaded. In comparison, that's like shutting down and re-opening your
e-mail program for every single message you want to view!

This can be designed much better by using iframes, maybe even Ajax.
Why can't we use the Web for what it was meant for: viewing hypertext
pages? Why must we turn it into a wrapper around every application
imaginable?

Because it works?
 
C

Chris Head

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Bokma wrote:
[snip]
Not necessary when using (i)frames + cache

True. Perhaps Hotmail is not very well designed, but it doesn't use
frames. I'm not really familiar with other Webmail systems, but the one
provided by my ISP doesn't either.
Nowadays, more then futile.

Sorry, I don't understand what you mean. Even on my 2.8GHz Pentium 4,
using Thunderbird to juggle messages is noticeably faster than wandering
around Hotmail. Complex HTML rendering still isn't absolutely
instantaneous. It's significantly more painful when I use my 433MHz
Celeron. It simply takes a long time to jump between message, inbox,
other message, inbox, other other message, inbox, etc.
This can be designed much better by using iframes, maybe even Ajax.

Agreed. Judicious use of frames (internal or otherwise) or
Javascript-based partial reloads could seriously improve the situation.
They might also provide an easier way for Webmail providers to implement
their pages in valid HTML: if you render the entire e-mail message alone
in a frame, you don't have to start stripping out pieces of e-mail
because they already exist (html and body elements, for example)
Because it works?

.... and purpose-built client applications (e.g. Thunderbird) don't?
Maybe I'm old-fashioned but I still very much prefer thick clients. They
simply feel much more solid. Perhaps part of it is that thin clients
have to communicate with the server at least a little bit for just about
everything they do, while thick clients can do a lot of work without ANY
Internet round-trip delay at all. Hotmail has to talk to the server to
move a message from one mailbox to another. Thunderbird doesn't. Ergo,
Thunderbird is faster as soon as the Internet gets congested.

Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)

iD8DBQFDDqXh6ZGQ8LKA8nwRAsVyAKCjwP9iyrPRBnMsI1pB+wqZdANE6ACfYeGx
w8SLwXln0VjpuwF+L7BDfKM=
=pZ/B
-----END PGP SIGNATURE-----
 
M

Mike Schilling

Denis Kasak said:
Y would not be useful because of the bandwidth it consumes, the malware it
would introduce, the additional time spent focusing on the format rather
than quality of the content and, frankly, because it's useless.

Threaded mail-readers too, screen-based editors , spell-checkers, all
useless frills.
 
G

Gordon Burditt

HTML is designed to degrade gracefully (never mind that most web
What is the risk with browser history?

spyware and viruses (which can come from places other than email)
sending it somewhere. Actually, there's not much point in keeping
a browser history if all it can contain is mail in YOUR mailbox
that may or may not have been already deleted.

Gordon L. Burditt
 
U

Ulrich Hobelmann

John said:
LOL, how? I can't post to RSS feeds. Or do you mean for lurkers?

I said "information side", meaning stuff like RSS is used for.
It has been used like that for ages (or as long as I can remember).

Yes, but for some reason people jumped onto the RSS hype. I wonder why.
Heck, even I am subscribed to a bunch of RSSes, because those
institutions don't offer NNTP ;)
It's called www. It's already here (or there)

Well, but forums only emulate the posting/reply structure. It would
make more sense to use NNTP for that, and use $WHATEVER, e.g. HTML, for
markup inside the posts. WWW is something else; a bunch of pages with
hyperlinks to each other. Maybe we shouldn't call web forums and other
dynamic websites www, as they don't really follow that purpose. They
are just abuses of HTTP/HTML/JS for thin clienting. ;)
But why do you want that? (Oh, and you can't read news with Outlook). Why
do you want more people on Usenet?

No, I'm not talking about usenet. I'm glad if the SNR keeps as high
(haha) as it is, and messages in plain text.

I'm talking about using the technology for communication, instead of
reinventing the wheel with crappy web forums.

Oh, and I've heard there are people reading our in-house newsgroup with
Outlook.
And what's wrong with that?

It's slow and pointless. All interaction that's more than clicking a
link has to be emulated with Javascript (heard of Ajax already?) to make
it more smooth.

NNTP has advantages like giving you only the headlines first, so you can
choose what to check out. Then you can get the article if you like (in
the communication case) or the news description (in the RSSoid case) and
maybe click on a link inside. Saves bandwidth and is quite faster than
waiting for some overloaded PHP server to send you a bunch of HTML
tables. Responding doesn't involve *any* HTTP requests, just a keypress
and you're typing.

Web forums are stone-age, as are most web-pages.
 
U

usenet

In comp.lang.perl.misc Ulrich Hobelmann said:
That is because NNTP and its applications didn't evolve to feed the
glitzy need lots of users have.
I don't think they have "glitzy need", they are just fed glitzy (but
slow) forums as the way to get support etc. If they were told about
the alternatives as well and told how to use them then I thiink those
alternatives would be used.

"NNTP and its applications" have evolved to provide a set of much more
sophisticated means of accessing and giving information than any forum
I've ever seen.

Sadly web forums (esp. the ugly, sloooow PHPBB, and the unspeakable
Google groups) are increasingly replacing usenet, but there are
exceptions (DragonflyBSD).
One good solution is a furum which is also accessible by NNTP.

On the information side (in contrast to the discussion side) RSS is
replacing Usenet, with some obvious disadvantages: go on vacation,
return after a week, and -- yahoo! -- all your RSS feeds only turn of
the, say, most recent 30 articles, while your newsgroups all show
everything you missed.
Same applies to most newsfeeds, depending on retention. If you want
to look a long way back in a thread, use Google Groups.
 
U

usenet

In comp.lang.perl.misc John Bokma said:
Yup, Slow because of all the HTML and avatars. And you suggest to introduce
such a thing to Usenet?
No, quite the opposite, I like Usenet News as it is.

And which useful tools do you require?
A choice of news readers to suit different people with different
interfaces, filtering, kill files, etc. etc. A forum provides a
single, usually rather limited, interface for the user with no way for
the user to change it radically.
 
U

Ulrich Hobelmann

Mike said:
No, they don't. Minimalist Unix distributions don't include a browser
by default. I know the BSD's don't, and suspect that gentoo Linux
doesn't.

HTML is designed to degrade gracefully (never mind that most web
authors and many browser developers don't seem to comprehend this), so
you don't really need a "subset" html to get the safety features you
want. All you need to do is disable the appropriate features in the
HTML renderer in your news and mail readers. JavaScript, Java, and any
form of object embedding. Oh yeah, and frames.

That's a good idea. I have parts of it disabled. The advantage of
disabling them all is that you don't have to visit all those crappy
modern websites, because they don't work.

What I hate about most are the sites that don't even *mention* that they
want cookies. Often I have to wonder, reinput input fields etc. and
then after ten minutes trying *bang*, the idea, maybe to allow cookies
for that site. Some people really don't have a clue, but kludgy "web
standards technologies" (by the oh-so-omnisavant W3C) kind of force it.
 
J

John Bokma

Chris Head said:
John Bokma wrote:

Sorry, I don't understand what you mean. Even on my 2.8GHz Pentium 4,
using Thunderbird to juggle messages is noticeably faster than
wandering around Hotmail. Complex HTML rendering still isn't
absolutely instantaneous.

It can be made much faster. There will always be a delay since messages
have to be downloaded, but with a fast connection and a good design, the
delay will be very very small and the advantages are big.
It's significantly more painful when I use my 433MHz
Celeron. It simply takes a long time to jump between message, inbox,
other message, inbox, other other message, inbox, etc.
....


Agreed. Judicious use of frames (internal or otherwise) or
Javascript-based partial reloads could seriously improve the
situation. They might also provide an easier way for Webmail providers
to implement their pages in valid HTML: if you render the entire
e-mail message alone
in a frame, you don't have to start stripping out pieces of e-mail
because they already exist (html and body elements, for example)
Yup.


... and purpose-built client applications (e.g. Thunderbird) don't?

if A -> B, it doesn't say that B -> A :) I.e. that it works via HTML
doesn't mean it doesn't with a dedicated client ;-).

I live in Mexico, most people here rely on so called Internet cafes for
their connection, and even the use of a computer. For them Thunderbird
*doesn't work*.
Maybe I'm old-fashioned but I still very much prefer thick clients.
They simply feel much more solid. Perhaps part of it is that thin
clients have to communicate with the server at least a little bit for
just about everything they do, while thick clients can do a lot of
work without ANY Internet round-trip delay at all.

Each has it's place. A bug in a thick client means each and everyone has
to be fixed. With a thin one, just one has to be fixed :-D.
Hotmail has to talk to the server to
move a message from one mailbox to another. Thunderbird doesn't.

Depends on where your mailbox resides. Isn't there something called
MAPI? (I haven't used it myself, but I recall something like that).
Ergo,
Thunderbird is faster as soon as the Internet gets congested.

Ah, yeah, wasn't that predicted to happen in like 2001?

Also, unless you have some program that kills spam on the server, you
have to download all with Thunderbird. I remember a funny day when I got
2000 messages/hour due to a virus outbreak :-( With hotmail, if you have
100 new messages you download them when you read them. Or kill them when
you don't want to read.
 
D

Denis Kasak

Mike said:
Threaded mail-readers too, screen-based editors , spell-checkers, all
useless frills.

Interestingly enough, I have explained my opinion in the part of the
post you have trimmed. On the other hand, things you mentioned are far
from being useless. They introduce no intrinsical slowdown due to
increased bandwidth consumation, nor potential security problems. They
have no downsides I can possibly think of and have many advantages. They
are useful. HTML on Usenet is not.

-- Denis
 
J

John Bokma

Ulrich Hobelmann said:
I said "information side", meaning stuff like RSS is used for.

Nah, I wouldn't call it a replacement. Maybe of mailinglists with latest
news.
Yes, but for some reason people jumped onto the RSS hype.

You think so? Like on push technology, VRML, and what more? Most of my
friends have no clue what RSS is. Maybe in IE7, when it's more hidden,
people will use it. But I wouldn't call it a hype, unless a hype is
something many people shout you have to have it (hmm...)
I wonder
why.
Heck, even I am subscribed to a bunch of RSSes, because those
institutions don't offer NNTP ;)

But they probably have (or had) a mailing list.
Well, but forums only emulate the posting/reply structure. It would
make more sense to use NNTP for that,

Why? It now works in the browser, you don't need to install another
client. Moreover, many people, especially where I live, don't have a
computer at home. Same for many students I know, they use the computer
at school. And many people I know with a job use the computer at work.
And not everybody wants to install a client for each and every protocol.
Hence why things like webmessenger are used.
and use $WHATEVER, e.g. HTML,
for markup inside the posts. WWW is something else; a bunch of pages
with hyperlinks to each other. Maybe we shouldn't call web forums and
other dynamic websites www, as they don't really follow that purpose.
Nonsense.

They are just abuses of HTTP/HTML/JS for thin clienting. ;)

Like UUencode is abuse of ASCII? LOL!
No, I'm not talking about usenet. I'm glad if the SNR keeps as high
(haha) as it is, and messages in plain text.

I'm talking about using the technology for communication, instead of
reinventing the wheel with crappy web forums.

What is exactly crappy about those forums?
Oh, and I've heard there are people reading our in-house newsgroup
with Outlook.

Amazing, since I always understood that it can't do NNTP.
It's slow and pointless.

The huge success of web based message boards seems so say something
entirely different. When I post with X-news, there is a delay, when I
post with my browser, there is a delay. I have no idea which delay is
more significant. Maybe they are too close.
All interaction that's more than clicking a
link has to be emulated with Javascript (heard of Ajax already?

Yes, I even mentioned it in this thread. And what's the problem?
) to
make it more smooth.

HTML was never a programming language, and will never be. Hence for
fancy stuff you have to use a programming language. Nothing wrong with
that.
NNTP has advantages like giving you only the headlines first, so you
can choose what to check out.

Funny, I see the same when I use phpBB. Headlines.
Then you can get the article if you
like (in the communication case)

Yup, same with phpBB, I click a link, and bzzzt.. there is the article,
and the replies to it.
or the news description (in the
RSSoid case)

Yup, there is a mod for phpBB that makes it possible to give each post
besides a title a short description.
and maybe click on a link inside. Saves bandwidth and is
quite faster than waiting for some overloaded PHP server to send you a
bunch of HTML tables.

Hence, overloaded servers shouldn't use PHP, or use special caching
tricks. I can't remember having seen slow boards, even not the ones with
hundreds of simultaneous users (for example phpbb.com).
Responding doesn't involve *any* HTTP requests,

No, but it requires sending your post to an NNTP server. Which takes
time (when I press send, I don't see this window close immediately).
just a keypress and you're typing.

Just a mouse click.
Web forums are stone-age, as are most web-pages.

Maybe you should visit one and check out for yourself. Age has little to
do with it, Usenet is way older, works. IRC is way older, works.
 
J

John Bokma

"NNTP and its applications" have evolved to provide a set of much more
sophisticated means of accessing and giving information than any forum
I've ever seen.

Example(s). And do users need those sophisticated things?
 
J

John Bokma

In comp.lang.perl.misc John Bokma <[email protected]> wrote:

[ web based boards ]
A choice of news readers to suit different people with different
interfaces,

- different browsers, different stylesheets, different board styles
(themes).
filtering,

There is often a search function, which filters away everything that
doesn't match. There are also things like word filters, etc.
kill files,

etc. etc.
http://www.phpbb.com/mods/

A forum provides a
single, usually rather limited, interface for the user with no way for
the user to change it radically.

Does the user want this? And with a user stylesheet you can change it
quite radically :)

And in return the user gets: colors, fonts, font sizes, embedding of
images, flash, you name it. Moving avatars, even sounds.

Oh, yes, I would love to see an XML interface on the board I use. Maybe
I can just install a mod, or write one myself.
 
J

John Bokma

Ulrich Hobelmann said:
What I hate about most are the sites that don't even *mention* that
they want cookies. Often I have to wonder, reinput input fields etc.
and then after ten minutes trying *bang*, the idea, maybe to allow
cookies for that site.

So your browser doesn't warn you?
 
J

John Bokma

Denis Kasak said:
Interestingly enough, I have explained my opinion in the part of the
post you have trimmed. On the other hand, things you mentioned are far
from being useless. They introduce no intrinsical slowdown due to
increased bandwidth consumation, nor potential security problems.

You can't be sure: errors in the handling of threads can cause a buffer
overflow, same for spelling checking :-D
They
have no downsides I can possibly think of

Some people never use them, and hence they use memory and add risks.
and have many advantages. They
are useful. HTML on Usenet is not.

Of course can HTML be useful on Usenet. The problem is that it will be much
more often abused instead of used.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
474,261
Messages
2,571,040
Members
48,769
Latest member
Clifft

Latest Threads

Top