Computer Pioneer Bob Bemer Dies 348
tpconcannon writes "Bob Bemer, the man who helped introduce the backslash as well as the escape key to computing, has passed away at his home at the age of 78. He also helped develop ASCII during the 60's at IBM. More interesting is that he predicted the Y2K bug all the way back in 1971!"
He was 84, not 78 (Score:5, Informative)
Math is fun (Score:4, Interesting)
Re:Math is fun (Score:4, Funny)
Re:Math is fun (Score:5, Funny)
Re:Math is fun (Score:3, Funny)
It's a Y2K bug..
Re:Math is fun (Score:4, Insightful)
Re:Math is fun (Score:3, Funny)
Re:Math is fun (Score:3, Interesting)
Re:He was 84, not 78 (Score:5, Insightful)
Re:He was 84, not 78 (Score:4, Funny)
what better time for a Real Programmers list?
http://www.cs.williams.edu/~terescoj/humor/realpr
Riddle for ya! (Score:3, Funny)
"But, that will break in 2000!"
Correct response is:
a) "Oh my god!!! You're a genius! I never would have thought of that if I didn't have you here to think of these things!"
b) "Yeah, I know, but who gives a shit? No one's going to be using this software in 29 years anyway."
Re:He was 84, not 78 (Score:5, Informative)
Regardless, Mr. Bemer was a true pioneer and champion of the early computer age. He may not have been as famous as some of the bigger guys, but his contributions were significant and still relevant even today.
In other news, another great computer pioneer, Herman Heine Goldstine, also died [kansascity.com]. Goldstine helped influence the goverment to fund development of ENIAC.
Re:He was 84, not 78 (Score:3, Funny)
IMTO/.
Re:He was 84, not 78 (Score:4, Funny)
So one might say (Score:5, Funny)
Re:So one might say (Score:5, Funny)
Re:So one might say (Score:2, Informative)
Re:So one might say (Score:3, Funny)
/ sigh
Man, its no wonder we have trouble getting a date.
Re:So one might say (Score:5, Funny)
Re:So one might say (Score:5, Funny)
RTFA
He just escaped.
Re:So one might say (Score:2, Informative)
82 73 80 (Score:5, Funny)
Re:82 73 80 (Score:5, Insightful)
0x52 0x49 0x50
Re:82 73 80 (Score:3, Funny)
108 51 51 116
Wow, even I thought that was lame.
Re:82 73 80 (Score:3, Insightful)
Hey there, sonny, even folks my age, and I'm over a generation younger than Bob Bemer, say 122 111 120. The modernizers may say 52 49 50, but Real Programmers certainly don't say 82 73 80.
For the lazy: (Score:5, Interesting)
His website (Score:5, Informative)
Re:His website (Score:5, Informative)
That Y2K thingy... (Score:5, Insightful)
Re:That Y2K thingy... (Score:4, Informative)
Re:That Y2K thingy... (Score:3, Insightful)
note that Y2K was real! (Score:3, Interesting)
Yahoo and Microsoft hit their all-time highs during the week of Y2K, and never recovered since.
Anyone who says the Y2K problem wasn't real, hasn't been following tech stocks.
Re:note that Y2K was real! (Score:4, Interesting)
not sure why the link didn't show in the last posting.
Re:That Y2K thingy... (Score:4, Interesting)
we are now rather spoilt with storage space/bandwidth/etc
Re:That Y2K thingy... (Score:5, Informative)
Re:That Y2K thingy... (Score:5, Interesting)
Text and BCD formats were popular because they were efficient. Binary (integer) formats for date and time required complex conversions for I/O. There was no such thing as the microprocessor. Multiplication and division were usually very slow operations. Many computers implemented them in software, not hardware. The hardware for them was often an expensive option, not a standard part of the CPU. BCD could be converted to/from your favorite character code with simple hardwired logic.
I predicted Y2K in '70. Nobody heard me either. (Score:5, Interesting)
I was already predicting it no later than '70. Didn't have the cute three-symbol acronym - I was calling it "The Great Bimillenial Computer Date Disaster."
(I was resuscitating a batch processing system in '70 that wouldn't start - turned out to be a 'sanity check' on the date entry. But if I recall correctly I'd been predicting it even before then.)
Nobody listened to ME, either.
(In fact, in the early '80s, while I was consulting, I tried to convince the customer to let me specify date entry in a way that wouldn't blow up in 2000, and was directly ordered not to spend time doing so - because the design life of the system was only 15 years. B-(
I guess I can feel a bit better if Bemer couldn't get the message across either. (Sigh.)
Re:That Y2K thingy... (Score:2, Funny)
Re:That Y2K thingy... (Score:5, Interesting)
I see two reasons why code wasn't designed for four-digit years in the 70s:
1. No one thought that their code would still be in use in 20-30 years.
2. It would be inefficient to waste a byte of space per entry. Storage space and memory were both very limited until fairly recently.
Re:That Y2K thingy... (Score:3, Interesting)
My only guess is that this was in systems where you would need to be displaying the last two numbers, so displaying 0-27 for 100-127 would obviously cause a problem. However, it would seem simple to just add your year variable to a constant of 1900 and display
Re:That Y2K thingy... (Score:4, Informative)
Re:That Y2K thingy... (Score:3, Insightful)
Because that's not the way the year was stored. In my current COBOL job I store the date as 8 character bytes (YYYYMMDD). I have converted programs from back in the day which were 6 character bytes (YYMMDD). This makes it simpler to read and write flat files
Re:That Y2K thingy... (Score:3, Insightful)
Re:That Y2K thingy... (Score:5, Insightful)
I'm sorry, but that's just not true. Y2K went smoothly very much because everybody made sure it did. Many, many very real issues were discovered and addressed. I've seen plenty of the dry runs done, and the results were quite depressing, to say the least.
After checking everything over, I had my networks and clientelle upgraded where necessary, and only one relatively unimportant system went down. (and it came up fine the next morning)
Don't think that just because nothing major happened, that nothing major WOULD HAVE happened... lots of good people made sure it went OK.
Re:That Y2K thingy... (Score:3, Interesting)
Re:That Y2K thingy... (Score:5, Insightful)
I'm sure that all the programmers who worked 20 hours a day to fix many of the problems, and the governments worldwide who allocated billions to fund plans to fix these problems would be thrilled to hear you say that Y2K "just wasn't that big a deal".
Yes, the problems were blown out of proportion by some people (Gary North, for example), but ignoring the real issues that did exist at the time is just as stupid. I don't think it would have been apocalyptic if these issues weren't addressed as they were, but it would certainly be a huge headache, especially in the financial and business sectors. The amount of private contracts [freezope.org] that I and a lot of people that I know got for converting legacy DOS apps to Windows or Linux (the two most common) would probably surprise you. A lot of them didn't even have the source code, so complete re-writes were neccessary.
Ah. A true geek. Or nerd. Or maybe plain cool? (Score:5, Interesting)
In Memory Of A True Geek
Re:Ah. A true geek. Or nerd. Or maybe plain cool? (Score:2)
Ok, too much Gibson.
Re:Ah. A true geek. Or nerd. Or maybe plain cool? (Score:5, Interesting)
He replied, "Type faster."
KFG
I think we all know who invented what (Score:2, Funny)
Some cool stuff can be found here (Score:5, Informative)
And the google cache [64.233.167.104] for the impending slashdotting
Among the more interesting tidbits is that he coined the word COBOL
Re:Some cool stuff can be found here (Score:4, Funny)
Hey well nobody's perfect...
Re:Some cool stuff can be found here (Score:5, Interesting)
about managers in computer industry [bobbemer.com] (it reminds me of my bosses) and
when it's to cheap for the government [bobbemer.com].
And talking about ASCII, and (dead) keys, now I know that the ALT Key was pattented by IBM... who (apparently) lost [bobbemer.com] a patent litigation on this issue.
Worth reading!
Sounds Like... (Score:5, Insightful)
Re:Sounds Like... (Score:5, Informative)
Hmm... Why?
It's a perfectly sensible combination since you shouldn't be able to hit the keys accidentally, and are therefore separated from each other.
But you probably blurted it out because you thought it was a Microsoft innovation.
Sad News .... Bob Bemer, dead at 84 (Score:5, Funny)
The AP reported he was 84, and Wikipedia [wikipedia.org] confirms that he was born in 1920.
In any case, I'd like to commemorate Mr. Bemer with the traditional Slashdot version of a Viking funeral:
I just heard some sad news on talk radio - COBOL standardizer/Father of ASCII Bob Bemer was found dead in his Texas home this morning. There weren't any more details. I'm sure everyone in the Slashdot community will miss him - even if you didn't enjoy his character set, there's no denying his contributions to popular culture. Truly an American icon.
Re:Sad News .... Bob Bemer, dead at 84 (Score:4, Funny)
Making ASCII art pr0n possible?
ahhh "esc" (Score:4, Funny)
Re:ahhh "esc" (Score:2)
Re:ahhh "esc" (Score:2, Funny)
Re:ahhh "esc" (Score:2, Interesting)
When living in Arizona, he had "ASCII" on his vanity licence plate.
ASCII (Score:5, Interesting)
RIP (Score:3, Insightful)
ASCII Art Tributes? (Score:3, Interesting)
Nice editing of the article... (Score:4, Interesting)
"has died after a battle with cancer. He was 84."
2nd paragraph contradicts the first...
Re:Nice editing of the article... (Score:4, Funny)
The article was written in base 10 and 6/7ths.
Y10k bug (Score:5, Funny)
Re:Y10k bug (Score:3, Interesting)
Disclaimer: Y2K was nothing but overblown crap reported on by the uninformed media, and I would not want to be in any way associated with it. I just found it funny that PPC Mac's handle such huge dates.
Maybe he participated on this site (Score:5, Interesting)
As recently as a month ago, "He was on the computer every day," Teeler said Wednesday. "He is a man who literally worked just about every day until he died. He felt at home sitting in front of a (computer) screen."
Do you people think he knew about Slashdot? Maybe he actually had an account and got involved with the story discussions. For all you know, he may have been a regular comment and story submitter on this site and nobody will notice his disappearance. Just a thought.
Re:Maybe he participated on this site (Score:3, Funny)
Goodbye Bob (Score:5, Insightful)
from my (limited) COBOL days-
CLOSE mName-# BobBemer
Thanks Bob.
Re:Goodbye Bob (Score:3, Insightful)
Predicted, but did anyone care? (Score:3, Interesting)
Well, it was! Now, what happens when the number of seconds since 1970 rolls over the maximum digit for an int?
It figures (Score:5, Funny)
It figures that his age across the year 2000 would end up being miscalculated by someone ... or something.
His Exact words on Y2K !! (Score:5, Informative)
He wrote this in his article "Time and the Computer" way back in the 70's.
interesting indeed... (Score:3, Insightful)
which has not happened.
Backslash (Score:2)
Had the pleasure to chat with him (Score:5, Interesting)
Yes, It was always a pleasure to chat with him (Score:4, Interesting)
I exchanged e-mail with him a few times in the last few years, and I had a chance to acknowledge the inspiration [miser-theory.info] he was for me while he was still around. I don't know that he was around here. When I last exchanged e-mail with him he was frustrated about what it took to maintain his web site. Your contact was more recent. What do you think?
I guess he was a geek at heart. I had produced a fast decimal-to-binary algorithm for a machine that didn't have a built-in converter but addressed in binary and calculated in decimal (makes subscripting hard). He was the only one of his organization that worked it over and took more cycles out of it, and then I took out more using his ideas. He thanked me for giving him a chance to play. He also worried about improving programming languages, establishing software forensics, and making software engineering an activity that exploited reusable piece parts, anticipating components by a good 30 years. He funded Peter Landin and Bill Burge's work on Functional Programming in the US. He also understood about small details, like character sets and escape techniques. With regard to his people, he didn't believe in burning out developers and he thought there was a lot of life to be had outside of the office. I'm pleased to learn that he was active to the end. I'll never forget him. -- Dennis E. Hamilton
Asshats.. (Score:3, Insightful)
It's escape CHARACTER, not key (Score:5, Informative)
he defined the concept of using a special character to "escape" from one character set to another, and proposed to use the backslash for this (which hadn't existed in character sets until then).
the escape key has nothing to do with this!
thanks, slashdot editors, for misinforming people
I worked with Bob for a number of years (Score:5, Interesting)
When Bob's article on the Y2K problem appeared in 1971, I was surprised that nothing had been done. Of course, disk storage space was still quite pricey. I thought that Bob's article would stir things up.
When Y2K finally publicly surfaced in 1998 or 1999, I was stunned that not a damned thing had been done since Bob's definitive 1971 article on the topic.
Last year when I was proofing a local guru friend's in-process book ("The Healthy PC" by Carey Holzman, Osborne-McGraw Hill), we fell into a dispute (which I lost, of course) about his belief that Y2K should be described as a bug (because that's the way it was presented to the public) rather than a temporary disk space-saving convenience which had lived much too long.
I got in touch with Bob Bemer, with whom I had worked in the 1970s and 1980s, about what had actually gone down. He was very gracious and sent me a URL for a definitive newspaper article on Y2K:
http://www.bobbemer.com/weingart.htm
Bob was a very gracious person, as someone else observed, and both pleasant and impressive to work with; I knew somewhat of what he had accomplished.
Well that's depressing... (Score:4, Funny)
ASCII art tribute (Score:5, Interesting)
Hats off to a truly great man.
In a related story (Score:3, Funny)
I actually knew him slightly (Score:3, Interesting)
He was a true geek. He was very focused on whatever he was working on. So non-geeks thought he was difficult.
He was living near Phoenix then and his license plate was ESCAPE. I wondered what the police thougt about that. Perhaps thats why he changed it to ASCII.
R. I. P.
(this all happened over 20 years ago so I may have some details wrong)
Re:The Y2K Bug? (Score:5, Informative)
Re:The Y2K Bug? (Score:5, Interesting)
Our programmers spent an enormous amount of time updating code which certainly wouldn't have worked after the date change. A lot of applications the University relies on would have failed had that work not been done.
Hoax? I don't think so.
More recently, OpenAFS experienced a January 10, 2004 bug (when UNIX time reached 2^30). The election mechanism broke, so servers stopped synchronizing databases, which meant that no new volumes, users or groups could be created. It turned out to be a wrong bitmask in one place, so it was easily fixed.
Y2K would have been far, far worse than this if the problem had not been pointed out ahead of time.
Re:What Y2K bug? (Score:5, Insightful)
Re:What Y2K bug? (Score:2)
My dad works at a nuclear power plant, where prior to Y2K a lot of semi-critical work was still being performed by IBM PC (Intel 8086) machines. The things never did die, but some of them had to be replaced and new software had to be written, and quite a few programmers made it across the new year w
Re:What Y2K bug? (Score:3, Informative)
Nice troll... (Score:5, Interesting)
Second, a lot did, in fact, happen. A hell of a lot of code out there failed when rollover occurred. Nothing critical happened because that code was known to be critical and was thoroughly tested prior to the rollover.
Third, Russia and other countries are not full of fools, you know. They spent quite a lot doing Y2K related changes also. You're making unwarrented assumptions.
I grant you that the media frenzy was stupid, but that's the media. At one point I saw some media jack-off claiming that elevators would plummet to the ground, killing those trapped inside and causing major property damage and so forth. Let's be freakin' realistic. Nothing as silly as that would happen because embedded systems like that don't often depend on the frickin' date to work properly. The real risks were in financial software, for the most part. Stuff that did depend on date. And most of it was fixed before the problem happened.
Thus nothing happened because that was the desired outcome, and the reason we spent so much money in the first place. If something major had occurred, you'd have a real reason to bitch about the money that was spent, wouldn't you?
Re:What Y2K bug? (Score:4, Interesting)
Most of the problem code got fixed (particularly for critical systems) during the years leading up to 2000, so that's why it seems like nothing happened.
I personally had Y2K problems with reports that were generated by a couple of old Foxpro programs that were being used at my company. We had migrated to new software because we new about the Y2K problems with the old software. Sure enough, as of the morning of Jan 1, 2000, we could no longer print historical data out if the old system because it thought the date was 1900. I worked around the issue by rebuilding the reports in Crystal Reports which had a pivot year function.
Re:Y2K Prediction (Score:5, Insightful)
Well... not exactly. In 1971 (or in 1981 for that matter), computers didn't have a lot of memory. Writing code with 2-digit years could save what was then a lot of memory, and I'd bet that most of the programmers figured that their software would either be obsolete or re-written by the time 2000 came around. For the most part, they were right.
Re:Y2K Prediction (Score:5, Insightful)
And using 2 digit years was a perfectly acceptable solution for the time.
The only serious mistake they made was not in using 2 digit years, but in failing to create sufficient abstraction around the concept of a date that it was not possible to change the underlying implementation of a date without being forced to rewrite the software which was dependant on it. Data conversion would probably still have been required, but that could have been automated.
Of course, if they had done this in the first place. COBOL programmers wouldn't have been able to demand nearly as much of a salary as they did in the late 90's. Hmm... I smell a conspiracy. :)
Re:Y2K Prediction (Score:3, Informative)
Re:Rest in Peace - You were a true Pioneer (Score:3, Funny)
Re:Backslash (Score:2)
'Course, that's the OS X user in me talking.
Re:Slashdot (Score:3, Insightful)
Re:Not that backslash (Score:3, Informative)
Windows was descended from MS-DOS which was a clone of CP/M which was inspired by some old DEC operating systems that reserved the forward slash for command-line options.