M$ also recently took credit for "developing" DHCP and mentions that you need their active directory to use dynamic DNS effectively. Check the exec summary at http://www.microsoft.com/techNet/showcase/w2kinfdd .asp Lets hope those engineers never discover RFC's or we'll never hear the end of the advances M$ is making.
You're correct in saying that JIT generated code can run faster, be more efficient, etc. The only real problem is that you still have the initial burden of compiling every time you want to run the code. This is not a trivial amount of the time spent waiting for JAVA (to use one example) to do it's thing. Compiling of the sort you're describing is hugely complex and in the medium to long term will outway any benefits you might see from efficiency improvements in the actual code. Cheers
Unfortunately, requiring a degree is also a good way to ensure you don't get some of the best people. If I had actually finished my degree (I'll use the example I know best;)) the information about programming and computers learned would now be about 15 years out of date. I think actual experience and ongoing professional development (courses, reading, conferences, etc) count for a lot more than 4 years at party central with a piece of paper. Amazingly enough, so does my employer;) Some of the best developers I know have either no degree or a non-engineering degree. Having said that, I guess you still need some way to figure out who is worth the trouble for those entry level positions.
Slashdot Mirror
M$ also recently took credit for "developing" DHCP and mentions that you need their active directory to use dynamic DNS effectively. Check the exec summary at http://www.microsoft.com/techNet/showcase/w2kinfdd .asp Lets hope those engineers never discover RFC's or we'll never hear the end of the advances M$ is making.
You're correct in saying that JIT generated code can run faster, be more efficient, etc. The only real problem is that you still have the initial burden of compiling every time you want to run the code. This is not a trivial amount of the time spent waiting for JAVA (to use one example) to do it's thing. Compiling of the sort you're describing is hugely complex and in the medium to long term will outway any benefits you might see from efficiency improvements in the actual code. Cheers
Unfortunately, requiring a degree is also a good way to ensure you don't get some of the best people. If I had actually finished my degree (I'll use the example I know best ;)) the information about programming and computers learned would now be about 15 years out of date. I think actual experience and ongoing professional development (courses, reading, conferences, etc) count for a lot more than 4 years at party central with a piece of paper. Amazingly enough, so does my employer ;) Some of the best developers I know have either no degree or a non-engineering degree. Having said that, I guess you still need some way to figure out who is worth the trouble for those entry level positions.
Too bad the people that fixed Hubble aren't the same one's in charge of the Mars Missions. It would be really nice for one of them to work.