Kristen Nygaard, co-creator of Simula 67, dies 29
jejones writes "Kristen Nygaard, co-creator of Simula 67, a variant of Algol 60 designed for writing simulations that is considered to be the first object-oriented programming language, died of a heart attack on August 10, 2002 in Oslo, Norway.
An AP article, truly astonishing in its errors (e.g. "the programming language Simula...laid the basis for MS_DOS and the Internet"?!), can be found here."
Inventing the internet (Score:3, Funny)
Re:Inventing the internet (Score:2)
laughed out loud.
Comparison a stretch... (Score:3, Interesting)
First Dahl, then Dijkstra, now Nygaard. (Score:4, Interesting)
Are we now in a time where The Elder Ones are passing away?
Re:First Dahl, then Dijkstra, now Nygaard. (Score:1)
Re:First Dahl, then Dijkstra, now Nygaard. (Score:1)
The reference made was to the fantasy literature fenomenon where The Great First Ones
It is actually a quite precise reference as the inventive physicists and mathematicians, to whom we owe this keyboard on which we type, happen to be dying off. And for some reason the frequency of them dropping off seem to be a little higher nowadays.
But on the other hand, The Old Ones do not 'pass over' in the real world, they just make room for tomorrows dinosaurs. And the only way in which they are superior to us is that they get to wherever we are heading before us and get that last free window seat.
Knuth. (Score:2, Funny)
you wasted them playing that damn organ at the church. You see, I have sent you to earth to
research and finish MY book, I made you my coauthor and forgave you of all human responsibilies
like worship and prayer. If your mother was an israeli, you could have been my second son, you
know I have a thing or two for jewish chicks [must be the skirts]. But what have you done? you
spent more time writing TeX than I spent writing all my holly books (I could have finished earlier,
but I was busy automating a few things with emacs lisp, I got sick of assembler, God is a real
programmer, dontcha know?)
Now, don't give me no damn excuses, I will not extend your life another second (I can't, I used a
packed structure and I ran out of extra bits for the life field, I know premature optimization is
the root of all evil, but I have a HUGE "human life" database and I need to squeeze the last iota out of this machine)
So, yeah, go ahead and do stuff, umkay? I need to do some apoclypse and stuff and I need a few algos. Just get off that damn organ and write something, willya? and give a copy of it to a guy
called sinserve, he has slashdot ID 455889."
icon-based? (Score:2)
Is this dragging the "for" icon on top of the "database cursor" icon and filling in a SQL query after a right-click context menu?
Re:icon-based? (Score:2)
1. They meant the Icon programming language, see here [arizona.edu]
2. There are such things as graphical/icon programming languages. (After all, isn't that what a flowchart is?) The may make the most sense in simulations, where each box can be a type of transform, and you can connect them together in (presumably) interesting ways. Here's one link that might be interesting [berkeley.edu]. Or not.
Re:icon-based? (Score:1)
icon-based programming language: I think they might be trying and failing to describe the Smalltalk environment. The Smalltalk language certainly owed a lot to Simula.
MS-DOS reference: can't help but think someone was trying to add accuracy and something got lost in the translation (Mac OS and Windows owed lots to the PARC work involving Smalltalk, and Windows began life as a DOS shell, and, well, chop a few words until the meaning gets lost...)
Internet reference: again, looks like an indirect Smalltalk heritage deal, in that the browsers that popularized the medium owed a lot to those GUIs that owed a lot to Smalltalk that owed a lot to Simula....
not an obituary, but at least a mini-bio (Score:4, Informative)
Re:not an obituary, but at least a mini-bio (Score:1)
object-orientation's father (Score:2)
I'll let the late genius speak for himself, though: Kristen Nygaard [ifi.uio.no]'s home page.
Sigh. The man had class. (Score:2)
I remember when I discovered Simula 67 (aka "Algol with classes") on a DecSystem-10, I thought it was pretty cool. (Burroughs') Algol was my first programming lanaguage (APL my second, talk about opposites), so learning Simula was a snap. Unfortunately there wasn't much call for it.
Imagine my joy some ten years later when I heard about this new "C with classes" language that some guy named Stroustrup was working on. (Imagine my disgust at what C++ has become...)
He also kept Norway out of EU (Score:2)
Re:He also kept Norway out of EU (Score:2)
Re:He also kept Norway out of EU (Score:1)
Modeling Verus Simulating (Score:3, Interesting)
Here is an except about modeling versus simulating from my website:
"I disagree with the suggestion that business processes should be heavily modeled as real-world interactions. Viewing business applications as "simulations" can be problematic. Simulations are to reflect interactions of the "real world" in order to study the real world and improve its flow. Business applications are to achieve something by the best means possible using computers. These two goals are not necessarily the same, nor necessarily result in the same solution. A common example given of this disconnect is that if flight was modeled via real-world simulations of our actual experiences, then airplanes would have wings that flap.
Mirroring the real world and getting something done as efficiently as possible are different animals. Sometimes they overlap, but often they don't. The strength and weaknesses of computers are different than those of humans. Thus, to achieve the same task as simple and flexible as possible via computer requires different approaches than achieving it as a human with desks, paper, elevators, etc.
I don't really question OO's value in modeling interactions and behaviors of the real world. However, the best techniques for modeling the real world and for making better software are probably not the same in most cases.
I also notice that some software developers try to mirror the "real world" very closely in order to keep the customer comfortable by keeping alive archaic processes from the manual way of doing things. However, one may miss opportunities to improve or streamline the process if this is done. I am not saying that initial customer comfort is a bad thing, but perhaps the customer should be aware of the tradeoff being provided. Just be careful not offend them by implying that they won't be able to "handle the ideal process". These kinds of things often takes delicate diplomatic skills that frankly exceed my abilities.
Keep in mind, though, that the issue of the internal model (what the developer sees) and the external model (user interface) are generally independent. One can reflect or simulate the external world without having the other do the same."
(from: http://geocities.com/tablizer/model.htm)
In Memoriam page (Score:1)