In other words, his code decays MUCH faster than anyone elses. Glad he doesn't work for me. At "half the time", that means he's costing any project 50% more in his time/dollar worth. Ouch!
What he is saying is that if he is modifying a piece of code anyway, he'll see if the code he is changing could be improved. When revisiting code, you often see how it could be written differently in perhaps a cleaner way. Refactoring like this is a great way to incrementally improve your code base.
Actually, natural selection is *one* of the *processes* by which evolution is said to occur. By itself, all natural selection does is to select from the *existing* gene pool.
Doesn't that refer to the SSL certificate encryption key size? What they're talking about here is the key size for the OS's encryption mechanism. Two very different kettle of fish, there.
Yes, but previously (before policy changed) it was 40-bit. The point is that the US now allows exports of 128-bit encryption to all EU states + Australia, New Zealand and a few others.
let me start off by saying, that I have no formal degree of any kind. and I'm a principle engineer and have worked at quite a few famous network equipment companies.
Still, you should at least learn to spell your own job title:-)
I visited Pompeii and went up Vesuvius last year - highly recommended. But the amazing thing is the total disregard the Italians have for danger. Houses stretch a third of the way up the mountain slopes, and yet this volcano is incredibly active. Still smoking, it has had at least 2 major eruptions this century, and no doubt will erupt again in the next 50 years. And yet still they build.
There seems to be no discussion about the use of asynchronous I/O. I'm no Apache expert, but I would think that a single Apache process using a select() loop could serve many clients simultaneously. Current implementations of Java have to allocate a thread per connection, which is extremely inefficient. Granted, Java 1.4 introduces asynch I/O, but it is not a production release yet. But this will be a significant enhancement to Java once it is.
With the same novel, he also predicted the clarity and usability of Microsoft technical documentation, and did so before computers were ever invented...utterly amazing...
Computers were invented before 1961 (when C-22 was published), actually.
There are a lot of things kids should learn before learning how to program - if they ever do. Like reading, writing, mathematics, problem solving skills, social skills etc. I feel you are vastly overrating the importance of programming in a school's curriculum. For many, if not most students, programming is of little importance.
2. Teachers should learn to program and learn to teach how to program
Most teachers are too busy and too stressed to do anything other than survive. *IT teachers* should, I agree, know how to program and be able to teaching programming. But again, learning programming is simply not that important IMHO.
Networking is not the only reason to socialise - I meet up from time to time with many people I've worked with over the years - but in tough times knowing people can be invaluable. Why, the contract I have now is because I kept in touch with someone I worked with a few months ago.
1. It may force Sun to be more proactive on Java features such as parametrised types. Competition is good.
2. Many VB and C++ developers will move to C#. They will then be in an ideal position to transition to Java with little effort if they have a requirement for cross-platform apps.
My point (and that of others) is: an LDAP server is a valid store for XML data and so should be considered relevant to the question above. You were dismissing LDAP as merely a *protocol*.
It *is* just a protocol for accessing a datastore in a hierarchical manner. An LDAP server is just a translation layer that sits over a database - generally a relational one. And yes, an LDAP server is possibly a useful store for XML. But this doesn't imply anything about hierarchical databases.
Yes, the "P" in LDAP stands for protocol. You use it to talk to an LDAP server. The LDAP server *is* a database so the points are still valid
My point is that an LDAP server can be *any* database - and is quite likely to be a relational one, not a hierarchical one. LDAP is simply a hierarchical protocol.
Contrary to some of the comments I've read here, LDAP isn't an implementation of a database, it is a *protocol* for accessing directories. LDAP data could be stored in anything - a hierarchical database, a relational database, an object database or a flat file. Let's not confuse the issue under discussion.
A GPL-ed open source app [nographer.com] that I wrote has so far had >1200 downloads in 2 months, yet only six people have fed anything back (five of them were complementary). Admittedly this is on Windows, where maybe there are cultural differences.
Get used to it. This is typical. I've had 15,000 downloads of my Java FTP client, and now it is stable get around one email for each 200 downloads. Earlier versions got around one email per 50-100 downloads, but had some bugs and lacked some features.
Threading, thanks to NT's posix libraries, wasn't that much of a pain
Keep in mind that NT's posix libraries used to perform an order of magnitude worse than Win32 calls, e.g. select() vs WaitForMultipleObjects(). It's been a while since I've worked on Win32, but keep it in mind.
Apart from the useful advice offered re portable libraries, gcc etc, make sure you do *daily* builds on each target platform from day 1 of implementation. Don't rely on a big bang port in 12 months time.
Would you eat those funny packages they've pushing out of the planes? First, they are nothing like you've ever seen before. Second, how do you know if the enemy who just bombed you isn't trying to poison you?
If I was starving to death like most Afghans are, of course.
You know, I don't want to jump on any anti-Katz bandwagon, but this illustrates his worst propensities: grandiose generalizations with no backup. Look, if your column is only available on the web, dammit, how about using some of that new-fangled hypertext to provide us with a link or two?
To be fair, he's quoting from *Fast Food Nation*, which *does* provide backup. Go read it.
I'm an Aussie who's lived in London for a few years. The cameras everywhere do freak me out a little, and didn't help when I was mugged by a gang of youths in north London.
But what would scare me is if digital cameras with good recognition software was installed everywhere. Currently, the camera situation is a bit like scanning emails - too much film to search unless there is a pressing need to do so.
If some dude could search for my image on all of London's cameras just by clicking a mouse, then it gets too easy to abuse the situation. The more accessible and searchable information is, the more it has the potential to get abused.
In the UK, it's very hard to get a gun, even illegally, so the chances of the drug addict who's trying to nick my video having anything more dangerous than a knife are pretty low.
Don't bet on it. I was mugged in North London by a bunch of teenagers with a knife & a gun.
Slashdot Mirror
What he is saying is that if he is modifying a piece of code anyway, he'll see if the code he is changing could be improved. When revisiting code, you often see how it could be written differently in perhaps a cleaner way. Refactoring like this is a great way to incrementally improve your code base.
Actually, natural selection is *one* of the *processes* by which evolution is said to occur. By itself, all natural selection does is to select from the *existing* gene pool.
A quick case of natural selection - not necessarily evolution.
Yes, but previously (before policy changed) it was 40-bit. The point is that the US now allows exports of 128-bit encryption to all EU states + Australia, New Zealand and a few others.
My version of IE that I'm running here in the UK is 128-bit.
Still, you should at least learn to spell your own job title :-)
I visited Pompeii and went up Vesuvius last year - highly recommended. But the amazing thing is the total disregard the Italians have for danger. Houses stretch a third of the way up the mountain slopes, and yet this volcano is incredibly active. Still smoking, it has had at least 2 major eruptions this century, and no doubt will erupt again in the next 50 years. And yet still they build.
There seems to be no discussion about the use of asynchronous I/O. I'm no Apache expert, but I would think that a single Apache process using a select() loop could serve many clients simultaneously. Current implementations of Java have to allocate a thread per connection, which is extremely inefficient. Granted, Java 1.4 introduces asynch I/O, but it is not a production release yet. But this will be a significant enhancement to Java once it is.
Computers were invented before 1961 (when C-22 was published), actually.
There are a lot of things kids should learn before learning how to program - if they ever do. Like reading, writing, mathematics, problem solving skills, social skills etc. I feel you are vastly overrating the importance of programming in a school's curriculum. For many, if not most students, programming is of little importance.
2. Teachers should learn to program and learn to teach how to program
Most teachers are too busy and too stressed to do anything other than survive. *IT teachers* should, I agree, know how to program and be able to teaching programming. But again, learning programming is simply not that important IMHO.
Networking is not the only reason to socialise - I meet up from time to time with many people I've worked with over the years - but in tough times knowing people can be invaluable. Why, the contract I have now is because I kept in touch with someone I worked with a few months ago.
2. Many VB and C++ developers will move to C#. They will then be in an ideal position to transition to Java with little effort if they have a requirement for cross-platform apps.
It *is* just a protocol for accessing a datastore in a hierarchical manner. An LDAP server is just a translation layer that sits over a database - generally a relational one. And yes, an LDAP server is possibly a useful store for XML. But this doesn't imply anything about hierarchical databases.
My point is that an LDAP server can be *any* database - and is quite likely to be a relational one, not a hierarchical one. LDAP is simply a hierarchical protocol.
Contrary to some of the comments I've read here, LDAP isn't an implementation of a database, it is a *protocol* for accessing directories. LDAP data could be stored in anything - a hierarchical database, a relational database, an object database or a flat file. Let's not confuse the issue under discussion.
Get used to it. This is typical. I've had 15,000 downloads of my Java FTP client, and now it is stable get around one email for each 200 downloads. Earlier versions got around one email per 50-100 downloads, but had some bugs and lacked some features.
Keep in mind that NT's posix libraries used to perform an order of magnitude worse than Win32 calls, e.g. select() vs WaitForMultipleObjects(). It's been a while since I've worked on Win32, but keep it in mind.
Apart from the useful advice offered re portable libraries, gcc etc, make sure you do *daily* builds on each target platform from day 1 of implementation. Don't rely on a big bang port in 12 months time.
It happened a few hours ago and they have already ruled out terrorism? I don't think so ... how can they possibly know at the moment?
If I was starving to death like most Afghans are, of course.
To be fair, he's quoting from *Fast Food Nation*, which *does* provide backup. Go read it.
Many other reasonable answers include such things as garbage collection, checked exceptions, portability of binaries ...
But what would scare me is if digital cameras with good recognition software was installed everywhere. Currently, the camera situation is a bit like scanning emails - too much film to search unless there is a pressing need to do so.
If some dude could search for my image on all of London's cameras just by clicking a mouse, then it gets too easy to abuse the situation. The more accessible and searchable information is, the more it has the potential to get abused.
Don't bet on it. I was mugged in North London by a bunch of teenagers with a knife & a gun.
While interesting, *Philip and Alex's Guide to Web Publishing* doesn't tell me much about JSP.