|
This was my introduction to any sort of large network when I worked in London Guildhall University in the late eighties
JANET - Wikipedia
"We can't stop here - this is bat country" - Hunter S Thompson - RIP
|
|
|
|
|
|
I wonder if this is the namesake of Janet in "The Good Place" TV show.
|
|
|
|
|
Very, very long ago, I used the Adidas network 
|
|
|
|
|
Ah! SneakerNet! Still faster than the web, sometimes. 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Kind of mandatory[^]
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Don't underestimate the bandwidth of a 747 full of micro-SD cards.
FedEx Bandwidth
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
In the early 1990s, when I was teaching computer networks at a tech college, one problem in the final exam was to compare a 9600 bps modem line to my St.Bernhard "Bass", trained to run arbitrary distances at a speed of 15 km/h, carrying (rather than a keg of whiskey) under his chin a box of ten 1,44 Mbyte floppies. (Sure, the idea came from A. Tanenbaum: Computer Networks; I just had to brush up the speeds and capacities a little bit.)
One of the students made some remarks about noise along the line, in the form of bitches in heat along the route. Another one commented that the data was physically protected against theft ...
|
|
|
|
|
I was *just* about to post that
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
LOL
|
|
|
|
|
LO
L
ftfy
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Well I clicked on the link and I didn't see a picture of Al Gore anywhere! 
I, for one, like Roman Numerals.
|
|
|
|
|
...it was October 29, 1969.
|
|
|
|
|
OriginalGriff wrote: feeling old yet?
It's not very often, these days, that I can say "I wasn't even born then", but I wasn't born until mid 1970, so just missed the invention of ARPANET
|
|
|
|
|
I can say that I was around at that time. I was 13 days old, but I was around.
Kelly Herald
Software Developer
|
|
|
|
|
For me, 50 years ago, I was programming using punch cards. Sure glad those went away. Computers back then weren't exactly fast either, I doubt they had the power of a modern calculator. Gratefully, we have come a long way and computers have become far more powerful and easier to work with. Might I also add, a lot more fun.
mvarey
|
|
|
|
|
- Dad, what is "calculator"?
(Around 1995 I was lecturing in computer and telecommunication networking. When introducing signalling systems, I figured I should start out with something basic and well known: The interrupt signalling used by rotary dial phones. The studens gave me a blank stare - What is that? It turned out that of 54 students, a single one had ever used a rotary dial phone, one knew his aunt to have one, and a third student had seen such a thing. A few of the remaining students had seen them in old movies, but not in real life. ... I would expect young people of today not knowing that we had dedicated devices for running a calc app only, and nothing else. They won't see the purpose of it, why we would want to have one piece of equipment for adding the grocery ticket, a second for talking though, a third one to swich the TV to another channel, a fourth one to turn the heat up... Why???)
|
|
|
|
|
Fifty years ago, and a few more, I was using paper tape, bit switches and an ASR33 attached via current loop at 110bps.
I think I got more practical stuff done then than I do now using multiple screens and a hyped up IDE, but today's stuff looks prettier.
|
|
|
|
|
The third message contained a link to a cat video that wouldn't be available for another 40 years. They were so forward-looking back then.
|
|
|
|
|
Whippersnapper! I wrote my first program in the summer of 1965, in FORTRAN II on an IBM 1620.
|
|
|
|
|
FORTVER = FORTRAN90 - FORTRAN77 - FORTRANII
IF (FORTVER) 10,20,30
10 CALL FORTRANII()
GOTO 99
20 CALL FORTRAN77()
GOTO 99
30 FORTRAN90()
99 STOP 1
ET phone home now.
|
|
|
|
|
I was at UCSB when the ARPANET was up in mid 70's running on an IMP processor. I used it to run the MIT Math lab remotely and other things. The Culler-Fried (we called it KFC, but his name sounds like Freed ) on-line system used a card-oriented interface (COL, I think, IBM 80 columns) and a math interface (MOLSF). Had a double keyboard with math functions on top, the output was on a Tektronix Storage Oscilloscope. "Clear Screen" was the erase button! Ran all my Fortran simulations on it connected to a 360/75 with real iron-core memory.
|
|
|
|
|
I was a student at MIT at the time. The MIT network (prior to Athena) was ChaosNet and it used TCP to link to the ARPANET.
|
|
|
|
|
|
Just as most programmers today warn people not to use assembler, probably future programmers will warn people not to use anything other than natural language.
It is written in book Java How to Program ninth edition that instead of using the strings of numbers that computers could directly understand, programmers began using English-like abbreviations to represent elementary
operations:
1.5 Machine Languages, Assembly Languages and High-Level Languages
Programmers write instructions in various programming languages, some directly understandable by computers and others requiring intermediate translation steps. Hundreds of such languages are in use today. These may be divided into three general types:
Machine languages
Assembly languages
High-level languages
Any computer can directly understand only its own machine language, defined by its hardware design. Machine languages generally consist of strings of numbers (ultimately reduced to 1s and 0s) that instruct computers to perform their most elementary operations one at a time. Machine languages are machine dependent (a particular machine language can be used on only one type of computer). Such languages are cumbersome for humans. For example, here’s a section of an early machine-language program that adds overtime pay to base pay and stores the result in gross pay:
+1300042774
+1400593419
+1200274027
Programming in machine language was simply too slow and tedious for most programmers. Instead of using the strings of numbers that computers could directly understand, programmers began using English-like abbreviations to represent elementary operations. These abbreviations formed the basis of assembly languages. Translator programs called assemblers were developed to convert early assembly-language programs to machine language at computer speeds. The following section of an assembly-language program also adds overtime pay to base pay and stores the result in gross pay:
load basepay
add overpay
store grosspay
Although such code is clearer to humans, it’s incomprehensible to computers until translated to machine language. Computer usage increased rapidly with the advent of assembly languages, but programmers still had to use many instructions to accomplish even the simplest tasks. To speed the programming process, high-level languages were developed in which single statements could be written to accomplish substantial tasks. Translator programs called compilers convert high-level language programs into machine language. High-level languages allow you to write instructions that look almost like everyday English and contain commonly used mathematical notations. A payroll program written in a high-level language might contain a single statement such as
grossPay = basePay + overTimePay
Will future programmers probably warn people not to use anything other than natural language just as most programmers today warn people not to use assembler?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
