Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: John Wallace <johnwallace4@xxxxxxxxxxx>
- Date: Sun, 19 Jul 2009 04:14:46 -0700 (PDT)
On Jul 18, 12:46 pm, Neil Rieck <n.ri...@xxxxxxxxxxxx> wrote:
On Jul 17, 10:25 am, yyyc186 <rol...@xxxxxxxxxxxxxxxxxxxx> wrote:
On Jul 17, 6:45 am, Neil Rieck <n.ri...@xxxxxxxxxxxx> wrote:
ps. does anyone remember adding third-party software to MAC-OS or
Windows-95 to provide TCP/IP connectivity? Users new what was going on
but vendors were totally oblivious (MS was pushing NetBios/NetBUI +
SMB while Apple was pushing Apple-talk. DEC was pushing DECnet and LAT
while IBM was pushing SNA).
Ironically, those proprietary protocols solved a problem TCP/IP never
will...security. They were so finicky about the hardware they worked
with that "hacking in" from somewhere was almost impossible...at least
until someone hooked up a plain old modem and set it up as a non-
challenged terminal port.
So the point of my original post is that Google seems to be doing a
lot of adhoc network programming which will probably coalesce into a
new set of networking APIs. This paradigm shift could be as big as
adding device drivers to operating systems. (or at least as big as
adding network storage devices)
Maybe, maybe not. I find it very difficult to believe that people
want to use word processing applications which exist entirely on the
Web and store your work somewhere you don't know about in a manner you
cannot control or even audit who has seen. I imagine certain people,
like Dick Cheney would love it if everybody, except the inner circle
at Halliburton, were forced to use it as the _only_ word processor in
the world since it would make surveillance easier.
Imagine if J. K. Rowling had been forced to use it for the final Harry
Potter novel...There would be hundreds of different versions printed
all around the globe, long before her publisher got even one copy out
the door.
Sharing of documents and document collaboration is fine. That was
one of the original concepts behind All-In-One if I remember
correctly. Too bad the alienated the entire DEC programming world by
mapping the keypad to something other than EDT. All-In-One at least
kept everything on your secured global cluster.
Google is in a knock-down-drag out with the publishing industry over
their scanning of books for Google Books. Since Google doesn't make
any money printing books, they thought they had some God-given right
to scan all copyrighted materials and sell advertising on-line while
presenting the work up for free. The big brave stories about how they
expected all publishing houses to sign up allowing their "plea-
bargain" have quieted down now that the opt-out period has been
extended and more publishers, like myself, are opting out while also
forcing them to take down books of ours they scanned which are still
in print.
You are 100% correct but humans love to communicate and socialize
which means that security will almost always take a back seat to
connectivity. Think I am wrong? Everyone knows that STDs can be
controlled (eliminated?) by incorporating safe sexual practices and
yet STDs are running rampant and appear to be mutating faster than we
can imagine.
I, more than anyone else I know, was a huge fan of LAT + MOP (which
were not routeable protocols) and DECnet. But rather than looking at a
possible sci-fi inspired utopia of a world-wide data network, -ALL-
computer companies clung to their proprietary protocols. What is worse
was the high cost of licensing these technologies. For example, 10
years ago I was tasked with building a data connection between our VMS
platform and IBM's national ticketing center in Kentucky. We were
given two options. Use SNA or "MQ-series over TCP/IP". The SNA
solution was going to incur huge up-front hardware-and-software costs
while "MQ-series over TCP/IP" was almost free. Today, the windows-
weenies have banned SNA and DECnet from our corporate intranet so we
can only use it by doing "DECnet Tunneling over TCP/IP" (tip of the
hat to TCPware)
TCP/IP might be crap because it is the lowest common denominator
technology, but it has allowed me to build data channels between
between any platforms from any vendor. So I consider TCP/IP to be more
of a Rosetta stone than anything else. Sure it would be better if
everyone spoke Latin put try to convince the Egyptians of this.
Neil Rieck
Kitchener/Waterloo/Cambridge,
Ontario, Canada.http://www3.sympatico.ca/n.rieck/docs/GHLE.html
Calling TCP/IP a "Rosetta Stone" is a bit generous. It's more like a
higher speed longer distance extended addressing version of multidrop
RS232; all it does is get a string of bits from box A to box B
(potentially via some intervening boxes). It has nothing to say about
the interpretation of those bits. The OSI suite of protocols
prescribed both a mechanism for moving bits around and interpretations
for those bits in various defined classes of applications. OSI was an
architects/engineers solution and possibly at least ten years ahead of
its time given that IPv6 is still struggling to catch on, but as
readers here know, the market generally prefers cheap.
.
- Follow-Ups:
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Arne Vajhøj
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- References:
- ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Obaid
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Neil Rieck
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Arne Vajhøj
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Neil Rieck
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Arne Vajhøj
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Neil Rieck
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Neil Rieck
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: yyyc186
- Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- From: Neil Rieck
- ### Google Drops a Nuclear Bomb on Microsoft ###
- Prev by Date: test---ignore
- Next by Date: *.*_OLD
- Previous by thread: Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- Next by thread: Re: ### Google Drops a Nuclear Bomb on Microsoft ###
- Index(es):
Relevant Pages
|