If you insist that security be applied at the application layer, you are insisting that all application programmers include security provisions in their software. And then, the security routines must go through peer review and analysis for at least a cursory inspection for vulnerabilities.
If you apply the security at the link layer, then you're securing a different thing. You're securing all communication across that link. There is an overwhelming desire to accomplish this in wireless transmission because of the inherent lack of control over the data path (since the transmission must be broadcast, anybody can communicate on the line).
Higher layer security is still necessary, but you need the lower layer security to avoid unwanted guests on the network.
I'm looking at the post, and I don't see any spelling errors or particularly noticable grammar flaws. Perhaps it could have been written more eloquently, but I don't believe it's the place of the editors to make every article pristine.
My first instinct is to say Python or Smalltalk, especially to teach OO concepts. The only reason one would want to teach in another language (IMHO) is to give the student a marketable skill.
I can write killer python code all day, but it's to no use to my team leader because he refuses to even look at it. I have to port everything to C++ before he'll even run it (unless I put it behind HTTP:)
Some have said that Java is not very mainstream, but if it's not, it's surely poised to be. I know at the national lab where I work, there is probably more Java development than C++. Java seems to be the language of choice around here.
Given that it's replacing C++ as the ubiquitous standard programming language, I think it's quite appropriate they're changing out the curriculum. I wouldn't like it either.
Personally, I'm very happy with the attitude that was taken in my early CS curriculum: it doesn't matter which language we choose, so here's one out of a hat; if you want to learn another language, then do so. I gained three valuable experiences from that.
- You can learn any language in about a week if your skills are right.
- Your skills can be honed on any language.
- A programmer with a diverse language set is much more versatile and powerful than without.
I say get them a good teacher and let the teacher decide the language. The language shouldn't even be a part of the course description.
Slashdot Mirror
If you cut it in half diagonally, it'll still be a 36". I suggest cutting it vertically.
It has to do with applicability.
If you insist that security be applied at the application layer, you are insisting that all application programmers include security provisions in their software. And then, the security routines must go through peer review and analysis for at least a cursory inspection for vulnerabilities.
If you apply the security at the link layer, then you're securing a different thing. You're securing all communication across that link. There is an overwhelming desire to accomplish this in wireless transmission because of the inherent lack of control over the data path (since the transmission must be broadcast, anybody can communicate on the line).
Higher layer security is still necessary, but you need the lower layer security to avoid unwanted guests on the network.
I'm looking at the post, and I don't see any spelling errors or particularly noticable grammar flaws. Perhaps it could have been written more eloquently, but I don't believe it's the place of the editors to make every article pristine.
My first instinct is to say Python or Smalltalk, especially to teach OO concepts. The only reason one would want to teach in another language (IMHO) is to give the student a marketable skill.
:)
I can write killer python code all day, but it's to no use to my team leader because he refuses to even look at it. I have to port everything to C++ before he'll even run it (unless I put it behind HTTP
Some have said that Java is not very mainstream, but if it's not, it's surely poised to be. I know at the national lab where I work, there is probably more Java development than C++. Java seems to be the language of choice around here.
Given that it's replacing C++ as the ubiquitous standard programming language, I think it's quite appropriate they're changing out the curriculum. I wouldn't like it either.
Personally, I'm very happy with the attitude that was taken in my early CS curriculum: it doesn't matter which language we choose, so here's one out of a hat; if you want to learn another language, then do so. I gained three valuable experiences from that.
- You can learn any language in about a week if your skills are right.
- Your skills can be honed on any language.
- A programmer with a diverse language set is much more versatile and powerful than without.
I say get them a good teacher and let the teacher decide the language. The language shouldn't even be a part of the course description.
Are you suggesting they mirror their database with mySQL, which doesn't even support transactions?