Dijkstra's Manuscripts Available Online 251
Bodrius writes "Salon has a short but interesting article called GOTO considered joyful, about E. W. Dijkstra's manuscripts, as published by the University of Texas, and their bloggish nature.
I'm not sure if the blog analogy is that accurate, but the articles are a must read for computer scientists and geeks in general." (Annoying but free click-through system for non-subscribers.)
Full Text (Subscribers Only Article) (Score:4, Informative)
On his proto-blog archive, the words and spirit of the late computer scientist Edsger Dijkstra live on, inspiring new generations of geeks.
- - - - - - - - - - - -
By Rachel Chalmers
July 9, 2003 | considered harmful: adj. [very common] Edsger W. Dijkstra's note in the March 1968 "Communications of the ACM," "Goto Statement Considered Harmful," fired the first salvo in the structured programming wars
That entry in Eric Raymond's edition of the Hacker's Dictionary was my first encounter with pioneering computer scientist Edsger Wybe Dijkstra, but thanks to the dedicated work of volunteers at the University of Texas at Austin, it was very far from my last. These volunteers maintain the massive and growing EWD archive. It's a tremendous and erudite proto-blog, the extraordinary record of an exemplary life, and it's one of my favorite places on the Web. A year after his death, a computer scientist who devoted himself to teaching people how to think is still on the podium, delivering gem after gem of insight.
Born in the Netherlands in 1930, Dijkstra was a witty and thoroughly engaging writer in his nonnative English ("I have learned to be very suspicious of ideas I cannot express well in both Dutch and English," he noted, late in life. "As nice as it is to have the union at one's disposal, it is wise to confine oneself to the intersection.")
Over a 40-year period that began in the early 1960s, Dijkstra wrote prolifically on timely and compelling topics: from his experience of the evolution of universities on both sides of the Atlantic from the post-WWII era to the beginning of the 21st century; to meditations on the science and art of teaching; to incredibly rich and detailed accounts of his own intellectual methods (don't miss EWD 666: "A problem solved in my head," which contains the endearing aperçu: "Goldbach's Conjecture -- I had never thought that I would ever use that!")
Like entries in a modern weblog, many of the informal pieces collected in the EWD archive were never published in any traditional sense. Instead they were copied (and later photocopied), numbered sequentially from EWD 0 (sadly lost to history) to EWD 1317 ("From van IJzeren's correspondence to my aunt & uncle," written a few months before his death in August 2002) and circulated from the greedy hands of one computer scientist to another like Eastern European samizdat or fourth-generation copies of the Lions books.
For years I have been dipping into this priceless archive (or at least its English language subset; is there a great Dutch-English translator out there who would do the world the incalculable favor of translating the rest?) and I have yet to scratch the surface of its treasures. But I continue to follow the trail; the archive is redolent of the spoor of Dijkstra's intellectual evolution, the physical evidence of a great mind thinking aloud. A fine, clear light shines through it all, the light of intelligence unmarred by any particular arrogance or egotism -- the set of personal qualities I tend to think of as integrity.
Dijkstra is at his iconoclastic best on, for example, academic hypocrisy:
"Today's mathematical culture suffers from a style of publication, in which the results and the reasoning justifying them are published quite explicitly but in which all the pondering is rigorously suppressed, as if the need to ponder were a vulgar infirmity about which we don't talk in civilized company."
Or the relationship between programming and mathematics:
"Programming is one of the most difficult branches of applied mathematics; the poorer mathematicians had better remain pure mathematicians."
Or the truth itself, however unpalatable:
"French science is poisoned by politics."
One particularly apposite piece (EWD 696) is titled "Written in
Re:Full Text (Subscribers Only Article) (Score:3, Funny)
aperçu (Score:3, Funny)
The Fish [altavista.com] says aperçu is a french word that means "outline." Stupid fucking Salon elitist fucktards.
I'm writing obscure french words in an english-language article, thereby ignoring the point of writing it in the first place! I exude a certain je ne sais quoi you cour de merd bourgoise can't approach!
Re:aperçu (Score:2, Funny)
lol
Re:aperçu (Score:2, Funny)
Re:aperçu (Score:3, Funny)
Re:Full Text (Subscribers Only Article) (Score:2)
Jeroen
Re:Full Text (Subscribers Only Article) (Score:2)
Well, obviously you havn't either. If you think Dijkstra is wrong, tell what the diffrence is and why he's wrong. Don't just spout off like an idiot.
Your logic is outstandingly poor (Score:5, Insightful)
That conclusion is not obvious. Given that the real world introduces complications that can be ignored in the world of pure mathematics, his (presumed) premise that "if applied is hard, the weaker might better stick with pure" makes logical sense.
(2) How come all the loser mathematicians who can't hack it end up becoming programmers?.
Both of your premises of "loser" and "can't hack it" are just some sort of pejorative that mean nothing in practice if you're trying to make a logical argument, and the "end up becoming programmers" is patently false. So the statement is just plain empty of value.
I've never had much respect for Dijkstra. I have even less now.
Well, as a personal statement of your dislike for someone, it requires no rational justification and hence cannot be faulted. Whether others will feel a consequent lack of respect for your own self as a result is hard to say, but it's pretty safe to assume that they won't be impressed by your ability to reason.
Re:Full Text (Subscribers Only Article) (Score:4, Insightful)
(2) How come all the loser mathematicians who can't hack it end up becoming programmers?.
Well I have something of an advantage here, having actually read the original notes rather than the article about them. Back in the late 1980s I spent an afternoon reading them. Dijkstra used to send the notes out to what he considered the major computer science labs. Since Oxford was run by Tony Hoare it was obviously on the list.
At the time some of the other students thought that this practice was somewhat pretentious, tending to imply a somewhat elevated self-opinion. Today of course everyone from the lowliest grad student shares far more mundane thoughts in their blogs.
What Dijkstra was actually doing in the article referred to was pointing out that there was nothing intrinsically superior about 'pure' mathematics. At the time computer science was regularly condescended to as an inferior for of mathematics.
Where Dijkstra was wrong is that comp sci is not a branch of mathematics at all, it is as my tutor Tony Hoare pointed out 'An engineering profession'. At the time this was first proposed the idea was somewhat controvertial, today almost every programmer regards themselves as an engineer.
I think that in fact we have to go a bit further and understand that the highest levels of programming are actually more akin to architecture. It combines art and engineering, just as engineering combines science and mathematics.
There are plenty of architects and engineers who could never make much progress in the pure sciences. But take the best architects and the best engineers and you will often find that not only were most capable of being top class scientists, in many cases they actually were.
Re:Full Text (Subscribers Only Article) (Score:2, Interesting)
I transferred from Architecture to Computer Science. People didn't understand how I could like both, and they really didn't understand it when I said they're very similar.
You understand it perfectly.
Re:Full Text (Subscribers Only Article) (Score:2)
I'm currently spending some free time on a VM compiler/ interpreter system, which I obviously like because of the interesting architectural choices you can make during the development process.
I'm also working on a Gothic cathedral though, but for some reasons nothing happens when I give the "make all" command...
It is and isn't Mathematics (Score:2, Interesting)
In each branch of comp sci, you'll find people who will tell you that the others "are not computer science", but IMHO they all are real and useful aspects of the discipline.
Re:Full Text (Subscribers Only Article) (Score:2, Interesting)
I'm just a computer programmer, which is more like a carpenter than anything. I build things that other people want, just because I know how to do it. I didn't need any special education or certification to do my job, just experience with the tools of my trade. I'm just like a guy with a hammer.
Re:Full Text (Subscribers Only Article) (Score:2)
Certainly most bad programmers think of themselves as engineers. The rest of us know that until we can calculate to 3sigfig the chance that our code will fail when used by x users we are not doing engineering.
I've been programming for 25 years and I'm proud to say that I'm not, and never will be, an engineer. Proud because I don't believe that the term CAN be applied to software and it is a foolish self-delusion to think it can.
It is fair
Re:Full Text (Subscribers Only Article) (Score:2)
I think that in practice your theory is disproved by the existence of The Monkees, Play and Hanson as counterexamples.
Re:Full Text (Subscribers Only Article) (Score:3, Insightful)
Oh, and have you ever really looked at a real algorithm? They are mathematics, pure and simple. Mathematics has everything to do with programming. Case in
Re:Full Text (Subscribers Only Article) (Score:2, Insightful)
Bio (Score:5, Informative)
Re:Bio (Score:2, Informative)
Compelling? (Score:3, Funny)
Oh wait......*
Re:Compelling? (Score:4, Insightful)
As a person only vaguely interested in CS I can say that I was more intrigued by the fact that he hand-wrote his documents, gave personal notes about what he was feeling at the time (my note [slashdot.org] about what pen-type he was using), which are all VERY interesting to me.
For me, these little things are far more interesting than what topics he happened to be discussing.
His "blog-like" notes are probably better to read than JoSchmoe049169666420's because they are coming from very well-known professor who was in touch with the CS academic community.
That's my worthless
Re:Compelling? (Score:4, Interesting)
Unless you've read a good number of his writings, it's hard to appreciate the way this guy thought.
He also had the neatest handwriting in the known universe. I recall getting one of his notes that seemed as immaculately neat as all the others - with a note at the end apologising for the quality of the handwriting as he'd written it with his other hand "because it could use some practice". He resented having to use a typewriter because he liked to invent new symbols. He always wrote code fragments in a programming language of his own invention for which no known compiler exists.
It may be that you could describe this as a 'blog' - it was disseminated by mail to people who he'd somehow run into or been associated with. I have no idea how many copies were sent out - but it must have been hundreds. The earliest ones were long before the advent of the Internet.
Whether it makes a suitable Salon story - I can't say.
Subscription not necessary (Score:4, Interesting)
Re:Subscription not necessary (Score:2, Insightful)
Re:Subscription not necessary (Score:2, Offtopic)
Re: Subscription not necessary (Score:3, Insightful)
Notice how I didn't respond to the trolling part? Good. Now, you don't either.
Re:Subscription not necessary (Score:5, Insightful)
> You could change the expiration on the temporary cookie they give you to get perminent access. Of course, this would be illegal.
I was winding myself up to sneer, but then I realized that this would be [circumventing] a technological measure that effectively controls access to a work protected under [Title 17] [warwick.ac.uk].
While we're at it, remember that "No person shall [...] offer to the public [or] provide [...] any technology [...] or part thereof that is primarily designed or produced for the purpose of circumventing a technological measure that effectively controls access to a work protected under [Title 17]."
Citizen, remain at your console while the Secret Service analyzes the case against you and decides your guilt and an appropriate punishment.
Can someone shed more light on his misc. info? (Score:5, Interesting)
Why did he do this? For his own personal notes on which pens were good (I guess important if you are frequently writing things).
Why did he use pens and not electronic formats? For a CS person that surprises me.
Re:Can someone shed more light on his misc. info? (Score:5, Insightful)
Re:Can someone shed more light on his misc. info? (Score:3, Insightful)
Re:Can someone shed more light on his misc. info? (Score:2)
Re:Can someone shed more light on his misc. info? (Score:2)
Re: Can someone shed more light on his misc. info? (Score:5, Interesting)
> Since CS is (or at least should be) learning how to apply known algorithms to problems and the development of new algorithms to solve problems, CS should be very similar to math, and computer scientists ought to seem fairly similar to mathematicians.
For researchers in the 'theory' and 'algorithms' sub-fields of CS, I'd say they are mathematicians. They work with axioms and theorems and stuff just like other mathematicians do.
Other CS researchers are empiricists instead, e.g. most of those who do data mining or statistical natural language processing. And of course there's lots of other stuff in between. (E.g., network researchers may start off with an algorithmic concept but then run simulations to demonstrate their algorithm's effectiveness.)
There's a family of jokes to the effect that PhDs in computer science don't know anything about computers or programming or whatever. In actuality the individual's engagement with computers/programming will vary very much with the sub-field he's in. These days a theorist will need to be able to use LaTeX to write papers and read e-mail to see the conference announcements, but doesn't need to program at all. OTOH someone doing experiments with genetic algorithms will probably write their own code for their experiments, and may even turn into a hardware geek by building beowulf clusters to run the massively CPU-intensive experiments on.
> Most early CS people, as I understand it, were math people with an interest in computers.
I think you can still find a lot of older CS professors with degrees in applied mathematics. Computers were around long before CS departments even existed.
Re:Can someone shed more light on his misc. info? (Score:5, Funny)
One of my profs said he was giving a speach at Dijkstra's school. He wanted to make sure Dijkstra didn't attend (apperently Dijkstra was an asshole), so he sent out the announcement via email only. This ensured that Dijkstra would never get the announcement, as he did have a computer.
Re:Can someone shed more light on his misc. info? (Score:2, Interesting)
This ensured that Dijkstra would never get the announcement, as he did have a computer.
How does having a computer ensure that you will not get email? All the professors at my school have said nothing but kind words about the man (although they have only mentioned him post-mortum). The professors that I am talking about also know the man and never mentioned cowering in fear of him, or trying to hide from him.
Re: Can someone shed more light on his misc. info? (Score:5, Interesting)
> One of my profs said he was giving a speach at Dijkstra's school. He wanted to make sure Dijkstra didn't attend (apperently Dijkstra was an asshole)
I don't know about 'asshole', but he certainly qualified as a curmudgeon. Famously, if he was at a talk and the speaker put up a slide that had more than one color in it, Djikstra would interrupt and ask what the different colors meant. (I actually had an opportunity to see him do that once.)
I have repeatedly heard rumors at second and third remove to the effect that at least some of the CS faculty at Texas found him "very divisive", but the rumors never told me what the context was. Decisions at faculty meetings, I would guess.
But it shouldn't surprise anyone on Slashdot to hear that some CS geniuses have a contrary streak.
I took a class from him at UT in '93 (Score:5, Interesting)
He was at UT when I did my master's in CS there, and he was certainly a character. When the speaker walked into the room and saw him on the front row, little beads of sweat would immediately begin to form.
I actually took a class from him, which had a vague Latin name he translated for us as "whatever I want to talk about". He was quirky and intimidating but friendly and engaging at the same time.
Some of the interesting things he did:
He took pictures of each of the students (I think there were 7 of us) to file away somewhere. I guess it helped him remember our names.
He used a different hand for writing on the chalkboard on alternate days. Lefty-days were sometimes a bit rough. He had broken his right wrist a year or so before, and wanted to ensure he could still function if it happened again.
The class had no tests and no homework, but featured an open-ended one-on-one "verbal final" at the end of the semester, either in his (large, corner, carpeted, blackboards-on-every-wall) office, or in his home.
The verbal final featured *me* with those little beads of sweat...
Re: Can someone shed more light on his misc. info? (Score:2)
Fair question. There's far too many people splashing colour around just because they can.
It's a curse that affects newspapers as well.
Re: Can someone shed more light on his misc. info? (Score:3, Informative)
> I've always thought the title of the GOTO paper was a master stroke. Anyone else would have called it "Why GOTO statements are bad" or "Structural problems caused by GOTO", and your reaction would be "That's his opinion" or "Gee, everyone knows that". He made it sound like it came from absolute authority, and if you disagreed, you were setting programming back.
Thing is, it wasn't his title [theregister.co.uk]; it was stuck on by Niklaus Wirth [wikipedia.org], inventor of Pascal, when he converted the paper to a "letter to the editor"
Re:Can someone shed more light on his misc. info? (Score:3, Funny)
Re:Can someone shed more light on his misc. info? (Score:5, Insightful)
Re:Can someone shed more light on his misc. info? (Score:3, Interesting)
This is going to be really off topic, but it might be of interest to you...
I'm a lefty and have a terribly messy handwriting. As I aspire to be a comic artist (and have done so for years
I've had, what? 20 years to develop a proper handwriting letter.
It took me less than a year
Re:Can someone shed more light on his misc. info? (Score:2)
"Messy" doesn't automatically say bad; certainly it's not usually a point in the person's favor, but it's not that simplistic. Similarly, "neat" doesn't say good; sometimes it says "careful", sometimes it says "anal".
It's another dimension to the communication, one much harder to fake. Certain lies are easy to write, but
Re:Can someone shed more light on his misc. info? (Score:3, Interesting)
IF he did track what pen he was using, I can think of one possible reason. It was mentioned that these were photocopied and re-photocopied to several generations. During that process it won't be readily apparent what pen he used
Re:Can someone shed more light on his misc. info? (Score:2)
so you write proofs straight in LaTeX? pfff yer right. Much easier to think on paper, try if you don't believe me.
GOTO is DYING (Score:2, Funny)
It is official; Salon.com confirms: GOTO is dying One more crippling bombshell hit the already beleaguered GOTO community when IDC confirmed that GOTO market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Salon.com survey which plainly states that GOTO has lost more market share, this news serves to reinforce what we've known all along. GOTO is collapsing in complete disarray, as fittingly exemplified by fail
Statement I don't agree on (Score:5, Insightful)
"Programming is one of the most difficult branches of applied mathematics; the poorer mathematicians had better remain pure mathematicians."
I do not agree with this. I mean, in pure mathematics there are not much to think about besides mathematics. Programming includes many other aspects, for example creativity. So if you are a poor mathematican but have other qualities that are needed for programming, you would have an easier time doing programming than pure mathemtaics I think.
Re:Statement I don't agree on (Score:2)
Pure mathematics does require creativity. If it didn't it could all be done by computer. But some times coming up with, say, an utterly logical, but new, proof requires a degree of inspiration that most people don't ever experience. I sometimes wish I had the attention span and discipline do be creative in that way.
Re:Statement I don't agree on (Score:2, Insightful)
I think too that good mathematicans very often make good programmers and the other way around. The problem I see with Dijkstra's statement is that he says (as I understand it) that poor mathematicans would do better pure mathematicans than they they would do programmers. However you see it, there is more mathematics in pure mathematics than there is in programming. And thus if you have other qualities needed in programming, but y
Re:Statement I don't agree on (Score:3, Insightful)
Perhaps he meant something along the lines of "if you're a poor mathematician, don't compound your poor choice of career by becoming a programmer instead, because programming is still math." I don't think he meant that pure mathematics is the easier course of study, only that programming isn't necessarilly easier either.
Re:Statement I don't agree on (Score:2)
I'd argue that he ment that programs have to function, and a comptuer is the ultimate test of a computers functionality. A poor mathamatition can make a few mistakes that get lost in complex details, and it could take years for his peers to find the mistakes.
Say for example there is a flaw in the proof of Fermets's last theorm. It is still well accepted, and it seems to fit, but somewhere some detail is wrong. I personally don't have the ability to find it, and few of those reading this do. Compare t
I'm not sure if the blog analogy is that accurate, (Score:5, Funny)
Salon.com (Score:4, Informative)
"Salon has a history of significant losses and expects to incur operating losses in the near future. For the year ended March 31, 2003, Salon had net losses attributable to common stockholders of $5.7 million and had an accumulated deficit of $82.3 million." -- SEC Annual Report
Re:Salon.com (Score:2)
I like Salon, though, and would regret its passing. At the very minimum it provides a good cartoon M-Th.
Wife swapping??? (Score:5, Funny)
Tom.
Re:Wife swapping??? (Score:5, Funny)
Now all we need is a p2p program for that, and we're set.
Re:Wife swapping??? (Score:2)
Re:Wife swapping??? (Score:2)
I'd hope from the "preview" you could tell the difference.
Oh the nightmares a preview would save.
Re:Wife swapping??? (Score:2)
Call for volunteers (Score:5, Interesting)
Slashdotters descended from Dijkstra (Score:5, Funny)
Also the Microsoft-like problems that he faces with IBM. His disdain is clearly shown by labelling IBM the devil!
Dijkstra - trolling since 1975 ;)
I'm impressed by anyone (Score:2, Insightful)
Subject (Score:4, Interesting)
One of the major points he made before he left, and somewhat adamantly at that, was that software is so poor in quality nowadays because developers don't really bother to come up with formal proofs of correctness for their programs.
There was some back and forth from the audience on this point, with people wondering wether it was feasible for large pieces of software (e.g. OS kernels) to be proven, because of their size and complexity. He didn't seem to think that it should really be a problem, and attributed the lack of correctness proofs to laziness on the part of programmers.
It was an interesting talk.
No point to this post, really.
-Laxitive
Re:Subject (Score:2, Interesting)
Ideally, kernels and other large portions of code are made up of smaller functions. If each function is proved correct, then all that should remain at the end is to verify that each link maintains integrity. Think of it as a recursive proof, if you will.
Re:Subject (Score:3)
software is so poor in quality nowadays because developers don't really bother to come up with formal proofs of correctness for their programs
Asides from it being perposterous to expect all the developers in the world to write formal proofs for their programs, this statement is at best a wild assumption. He is proposing that the lack of us
Re:Subject (Score:2, Insightful)
Forgive me if you find me rude, but offhand dismissal without cogent arguing really taxes my patience.
Asides from it being perposterous to expect all the developers in the world to write formal proofs for their programs,
Why would that be so, exactly? Dijkstra was especially vocal against this "can't do" attitude. I don't ask for a compelling argument, just for a reasonable one.
this statement is at best a wild assumption. He is proposing that the lack of use of a particular (his) potential solution
Re:Subject (Score:2, Insightful)
Evidence that Dijkstra was not particularly in touch with what most software nowadays is about. It's not that it's fundamentally impossible to prove a large program correct, i.e., prove that its postcondition follows from its precondition, but that for many programs, coming up
Suggested reading (Score:2, Interesting)
Favorite Quote (Score:4, Interesting)
E.W. Dijkstra: The end of Computing Science? [utexas.edu]
Austin, 19 November 2000
Pronounciation? (Score:2)
Re:Pronounciation? (Score:2)
Re:Pronounciation? (Score:2)
Re:Pronounciation? (Score:2)
Re:Is Dykstra still relevant today? (Score:3, Insightful)
Re:Is Dykstra still relevant today? (Score:2)
Play any computer games?
Re:Is Dykstra still relevant today? (Score:5, Insightful)
Re:Is Dykstra still relevant today? (Score:5, Informative)
Re:Is Dykstra still relevant today? (Score:2)
Re:Is Dykstra still relevant today? (Score:2)
Perl and C++ "legacy technology"? I guess I'm headed for tech support on the midnight shift ...
Re:Is Dykstra still relevant today? (Score:2)
Ever hear of OSPF (Score:4, Insightful)
Ummm... Not so much. (Score:5, Informative)
The Internet uses Border Gateway Protocol (BGPv4), which is a Path-Vector routing protocol. OSPF is a Link-State routing protocol.
OSPF is considered an IGP (Interior Gateway Protocol). It can be used within an autonomous system, but has no place in determining path selection for traffic between automonous systems.
As far as IGPs go, there's only one that would be capable of handling the routing table for the entire Internet, and it's not OSPF. IS-IS, Intermediate Syetem to Intermediate System, is another Link-State protocol developed by the OSI during the same period when OSPF was being developed.
They share a lot of similar features, and address all of the same shortcomings inherent to Distance-Vector routing protocols (RIP, IGRP). You can actually redistribute the full Internet routing table from BGP into IS-IS, and it will handle the strain.
Aside from the ability to handle astronomically large routing tables, IS-IS has one additional feature that sets it above OSPF: No requirement for a single backbone area (Area 0, in OSPF speak).
OSPF is not particularly well suited to "meshy" environments, due to the need for a single, clearly defined backbone area (In OSPF, all traffic between non-backbone areas must traverse Area 0). IS-IS alleviates this requirement. There can be multiple Inter-area paths, which can be very useful in a complex network.
Of course, the pool of IS-IS savvy network engineers is far smaller than that of the OSPF disciples, so you don't see it in use very often. The exception is in the service provider space. Big ISPs, and Backbone Carriers frequently utilize IS-IS when an IGP is called for, notably for it's ability to handle large routing tables.
(Don't get me wrong... I'm a fan of OSPF, but much like the programmer folks like to say, "It's just a tool in the toolbox." The savvy network engineer will utilize the Routing Protocol which best suits his requirements (In some cases he'll use more than one), just as the savvy programmer with utilize the programming language that best suits his requirements.)
In summary:
Re:Is Dykstra still relevant today? (Score:2, Interesting)
Also, C++ and, as one of your responders aptly noted, Perl a
Re:Is Dykstra still relevant today? (Score:3, Informative)
And in any case, what do think most of those applications on your computer were written in?
Algorithms? (Score:4, Insightful)
What comes to mind right at first is Dijkstra's Shortest Path Algorithm [tokushima-u.ac.jp]. And hey, look...that page has java programs. In fact, take a look at a Java applet [toronto.edu] to better understand the algorithm.
Re:Is Dykstra still relevant today? (Score:5, Insightful)
Dijkstra's work on writing programs so as to be confident in their correctness from the start is very relevant--how much do you think people would be willing to pay for an OS written that way?
Re:Is Dykstra still relevant today? (Score:5, Informative)
You have entirely missed the point.
If you know math and language theory the actual language you currently know does not matter. Language is a tool. You can learn to use a new tool in a matter of weeks if not days. Math is the knowledge on how to use all of the tools, not just the particular shiny one that has just been produced last week.
After learning 5 or 6, the next one comes in a matter of days. Been there, seen that, trying to do it.
This has not changed since Dykstra and ain't going to change. Ever. This is the fact known as the 5 times salary difference between the factory floor and the chief designer office.
It is a fact of life, it exists in all industries and it is here to stay.
Actually, Asimov has described this brilliantly in one of his novells. Read "Profession". It is thy best novell he ever wrote.
'Tif true, indeed, good fir! (Score:2)
Then, af thou haft shewn, I muft fue hif Aff off for Violation of Copieright. And thou art correct, fir, it if indeed my beft Novell.
Re:Is Dykstra still relevant today? (Score:2, Insightful)
Re:Is Dykstra still relevant today? (Score:5, Insightful)
I study CS @ Eindhoven University, where he came and teached a lot(his and his compatriots were good in programming methodology: http://www.win.tue.nl/pm/ - horrible looking webpage) Trust me, it shows. Most of the 'hardcore' faculty members were friends/exstudents/what have you, and work the way he did. Dijkstra (and the folks at my faculty) did not bother himself with implementations of programming languages. Nor with what function to call for what. They all strive to understand the nature of the problem, and from that they try to derive the solution.
That's a totally different approach to programming, which is a *lot* of work. However, it shows in areas where simplicity is key. There is a reason why Dijkstra used Semaphores (what do you think Java uses?). Or have you ever seen a good proof of Peterson's Algorithm? (I know Feijen and van Gasteren gave a generic derivation in 'On a Method of Multiprogramming', but that's just me having had to read it because it's part of my study there, of course. A book which delves into seemingly simplistic problems, but then gathers a framework which can tackle much bigger problems then you would expect.)
The problems for single-process computing are easy. For those of you who program in them, I'm not trying to critisize or anything (I personally know that it's still damn hard from time to time), but there are no synchronisation problems, for one. To ensure that these are all systematicly handled you'd really want to have a proof that nothing can go wrong. Java and exceptions? Fine, it's just a way to get away with bad programming. There are a lot of places where you simply cannot get away with dirty programming: you don't want your car to deadlock going at 90 MpH, now would you? You want to be absolutely positive that it will *never* happen. THat means having either done extensive testing (which you can only hope it was sufficient), or having formal proof that it cannot go wrong.
That is why Dijkstra held himself to the 'very hard problems'. The easy ones you can mess up with and still have not too much problems. The hard ones are problematic if they fail.
He did not believe in cluttered code. Everything should be there for a reason, should be proven to be there and exactly there for a reason.
To excel in Computer Programming you must be so smart as to be able to tackle the really hard problems. That means tackling problems on the problem field. You don't need languages for that, you need proof. Languages are but a tool for describing a solution and verifying your proof. Some languages describe easier then others, yes, but the solution is the same.
I can write a C to Haskell to C++ to Prolog to Java compiler. Pretty straightforward too. The languages are the same. You just don't want to see the spaghetti which comes out of a program once I'm through with it. And that's the reason why you use a specific language for a solving a problem: some languages simply are much easier to express the solution in.
However, that does NOT solve the problem, it merely makes it easier to program a solution understandibly.
Dijkstra was above all a scientist, and thus had to convince the scientific community of his ideas. This normally is done by using formal methods which describe both the problem as the solution in such a away that they can be easily understood.
That is still the holy grail for may solutions: how can they be written such that they can be understood more easily.
But I'm starting to rant here...
Re:Is Dykstra still relevant today? (Score:2)
Going from Prolog to Java, for example, requires one to implement backtracking, unification, etc...
Similarly, going from Haskell to C++ requires one to implement a fairly sophisticated static type inference system... unless your translation isn't go
Re:Is Dykstra still relevant today? (Score:2)
As a programmer here in the real world, my problems rarely involve with this "keeping up with the Jonese" mentality espoused by trade magazines. No, programming is a skill, and a propreitary language like C# is not one of the tools used, because clients for critical GIS software that helps predict and manage Schistosomaisis problems (among other uses) in Africa do not have an option to r
Re:Is Dykstra still relevant today? (Score:2, Interesting)
Re:OT: Relatives? (Score:2)
Re:OT: Relatives? (Score:2)
Re:Right up the /. reader's alley... (Score:2)
Re:Right up the /. reader's alley... (Score:2)
Well, the stated intention of these 1 credit hour language courses is a mix of resume filler and some niche offerings for various business and science majors. C Sharp, and in particular VB, are widely used and as such are potentially useful things to have on one's resume. Sure it's true that they might not offer some of the innovations of other languages like lisp, but on the other hand, the style of software development used in COM and
Re:Right up the /. reader's alley... (Score:2)
From what I understand, mono, which has nothing to do with microsoft, is coming along nicely. Also, if I'm not mistaken, MS gives a way a free command line compiler. Since I've never used it I'm not sure how free it is. As for having an Operating System to experiment on, the vast majority of Computer Science majors I've known are far far more comfortable with and have gre
Re:Right up the /. reader's alley... (Score:2)
You say that teaching proprietary tech is IT