"If you were going to see a doctor and the doctor said, 'I've been really busy since I got out of medical school, and so I'm going to treat you with the techniques I learned back then,' you'd be rightly incensed."
This analogy is lousy. What I don't want to hear from a doctor is "I've poured all my time recently into slick presentations, so I can treat you only with the medical techniques I learned years ago in medical school, but I can explain them in a much less boring way than they were explained to me."
No, I don't want a device to tell me about the car in front of me. I'm pretty clear about the car in front of me. I want a device to tell the car behind me about the car behind me.
Seriously: something mounted in the back window like the flat red brake light, hooked up to a radar that measures distance to the next car behind. When something is too close for our distance, it starts flashing "Too close!". If they don't give space, or get closer, it flashes a bit more brightly and quickly after a few seconds.
After a few seconds more, it turns on the rear strobe.
It's a great start, but it would be nice if the generics were worked into more libraries - for example, in the Swing model classes, it would be nice to be able avoid casts by taking Integers out of a DefaultComboBoxModel<Integer>.
But hopefully it's just a matter of time (or of Beta 2).
If I remember correctly, the pizza compiler generates separate classes for the different primitive types. It needs a different class loader, but generates classes for an ordinary VM.
I'm pretty sure the prececpt of almost ALL academic ventures is that it goes into the open domain. Once a professor publishes a paper, it's made freely available for use provided that you make the correct citations.
Actually, it depends on the publisher of the journal/conference. Normally part of publishing is assigning copyright to the publisher. Usually the author keeps some rights, but not for unlimited distribution. It's almost never the case that published academic writing becomes public domain.
Most universities assign the right of student research and writing to themselves. Every now and then a story pops up about a research assistant who tries to patent something based on their work in a professor's lab; the university tends to lose those cases. It would be part of the university's contract with the assistant, or part of the registration agreement.
So chances are that most universities (at least in the US) are well within their rights to use this sort of a plagiarism-checking service.
Most of my group experiences involved maybe half of the group caring about their grade, and the other half being ok with a C. You then end up with an extremely unbalanced work load [...]
One strategy I used in a 13-week OS/compilers class was to make one project individual, and the second a group project. Although I'd take preferences for groups, to try to avoid this problem I didn't allow groups to have people with too big of a difference on their first projects. This took care of more of these difference-of-work-expectation problems than some other group formation approaches I'd tried before
This analogy is lousy. What I don't want to hear from a doctor is "I've poured all my time recently into slick presentations, so I can treat you only with the medical techniques I learned years ago in medical school, but I can explain them in a much less boring way than they were explained to me."
No, I don't want a device to tell me about the car in front of me. I'm pretty clear about the car in front of me. I want a device to tell the car behind me about the car behind me.
Seriously: something mounted in the back window like the flat red brake light, hooked up to a radar that measures distance to the next car behind. When something is too close for our distance, it starts flashing "Too close!". If they don't give space, or get closer, it flashes a bit more brightly and quickly after a few seconds.
After a few seconds more, it turns on the rear strobe.
[B]ut how do college radio stations operate? Do they get a break on pricing, etc?
Yes. Noncommercial stations (not just college) have a cheaper rate scheme.
There's another comment here suggesting that the royalties are why college radio plays more indie music. That's not true - it's a blanket rate.
It's a great start, but it would be nice if the generics were worked into more libraries - for example, in the Swing model classes, it would be nice to be able avoid casts by taking Integers out of a DefaultComboBoxModel<Integer> .
But hopefully it's just a matter of time (or of Beta 2).
Allowing primitive type arguments in generics would not necessarily require any changes to the VM or bytecode.
The Java 1.5 implementation of generics is substantially based on the Pizza compiler, which allowed primitive type arguments without requiring boxing (links: the pizza compiler, the GJ compiler it evolved into, some academic papers about the compilers).
If I remember correctly, the pizza compiler generates separate classes for the different primitive types. It needs a different class loader, but generates classes for an ordinary VM.
Actually, it depends on the publisher of the journal/conference. Normally part of publishing is assigning copyright to the publisher. Usually the author keeps some rights, but not for unlimited distribution. It's almost never the case that published academic writing becomes public domain.
Most universities assign the right of student research and writing to themselves. Every now and then a story pops up about a research assistant who tries to patent something based on their work in a professor's lab; the university tends to lose those cases. It would be part of the university's contract with the assistant, or part of the registration agreement.
So chances are that most universities (at least in the US) are well within their rights to use this sort of a plagiarism-checking service.
Spamagogo doesn't have quite the same setup, but it is good, and free for now.
Most of my group experiences involved maybe half of the group caring about their grade, and the other half being ok with a C. You then end up with an extremely unbalanced work load [...]
One strategy I used in a 13-week OS/compilers class was to make one project individual, and the second a group project. Although I'd take preferences for groups, to try to avoid this problem I didn't allow groups to have people with too big of a difference on their first projects. This took care of more of these difference-of-work-expectation problems than some other group formation approaches I'd tried before