In the past I have analyzed SP content and found only about 16% of the patches were related to security. The others were performance, bug fix, and feature release.
Patent Law does not pay out like other legal specialties. Boom. Done.
PS: Does Captain Nerdburger have the social skills to interact with lesser humans and effectively part them from their money? Or will he be squirrelled away in some IT giant's back office combing through abstracts?
Is the concept of "Fair Use" as defined by the Supreme Court (time shifting, media shifting, etc...) being eroded. What are the important battles to stem this erosion?
This is not going to be solved by OSS because the hardware they are using is not open. If you write "Fetch (car 005)" and the hardware is expecting "8qu4rjfo08uodsijfa;" then you don't exactly get car #5. I would assume that the license created by the vendor covers the API that speaks to the robots. Since that API will remain "secret" then no amount of super-double-XML-AJAX tomfoolery is going to bridge the gap between the user and the hardware.
I call "OSS enthusiasm stretch"
Slashdot Mirror
In the past I have analyzed SP content and found only about 16% of the patches were related to security. The others were performance, bug fix, and feature release.
Because, we know that the internets are not a truck and trucks have lights. This is really getting confusing. Congress, please send help!
Patent Law does not pay out like other legal specialties.
Boom.
Done.
PS: Does Captain Nerdburger have the social skills to interact with lesser humans and effectively part them from their money? Or will he be squirrelled away in some IT giant's back office combing through abstracts?
Is the concept of "Fair Use" as defined by the Supreme Court (time shifting, media shifting, etc...) being eroded. What are the important battles to stem this erosion?
This is not going to be solved by OSS because the hardware they are using is not open. If you write "Fetch (car 005)" and the hardware is expecting "8qu4rjfo08uodsijfa;" then you don't exactly get car #5. I would assume that the license created by the vendor covers the API that speaks to the robots. Since that API will remain "secret" then no amount of super-double-XML-AJAX tomfoolery is going to bridge the gap between the user and the hardware. I call "OSS enthusiasm stretch"
I'd bet on this incumbent.