Maybe I don't watch as much TV as some, but where has the press coverage been in the UK? I haven't noticed any signifigant stories in the papers either. It's almost as if they want the thing to die a quiet death so they can sweep it under the carpet and move on.
You do have to wonder why anyone would buy such an ugly piece of kit that has no killer app games, tries to be a phone too (I have a phone already ta) and results in a huge number of horrible buttons.
When instead you could have a shiny silver GBA SP with fantastic games like Pokemon and Advance Tactics and Mario. mmmmmmmmmmm... Mario
a) Is this indicative of a high level strategy by NVidia's management, who's marketing department is pressuring them to have higher 3DMark2003 scores than ATI?
OR
b) Has some low level device driver programmer (intern?) looked to get some easy brownie points by "optimising" the drivers for 3dMark2003 in a slightly clunky way?
Either is quite interesting:) I've been a victim/perpetrator of both in the past.
Why not just rewrite the offending code?
on
SCO SCO SCO!
·
· Score: 3, Interesting
Please someone correct me if I'm missing something here.
But isn't there a very quick solution for Linux once SCO discloses which are the "hundreds of lines of code" which were taken from SCO's UNIX source code? Can't we just rewrite the source code to perform a similar function to what's already there, but with a brand new open source implementation?
As far as I know, it's the source code which is copyrighted, and NOT the algorithm. So once SCO discloses in court what the offending lines of source code are, can't we rewrite those lines, distribute a kernel patch, and hey presto, the code is open source again?
Adequate documentation of code isn't just a problem for open source projects - pretty much everywhere I've worked the documentation tends to be poor unless there is a strong contractual obligation otherwise.
If the documentation is for people contributing code to the project, Doxygen is great for generating documentation from your source code, which you can annotate with javadoc-style comments. Great for seeing how convoluted your inheritance trees are becoming.
If the documentation is for people who use the project, but aren't coders, then I'm a bit more stuck. Basing it around a markup language like HTML or LaTeX would make it easiest to convert into whatever document formats people require, and if it's in HTML you can just publish it on the web for lazy people like me who don't want to download the whole docs.
Slashdot Mirror
You do have to wonder why anyone would buy such an ugly piece of kit that has no killer app games, tries to be a phone too (I have a phone already ta) and results in a huge number of horrible buttons.
When instead you could have a shiny silver GBA SP with fantastic games like Pokemon and Advance Tactics and Mario. mmmmmmmmmmm ... Mario
a) Is this indicative of a high level strategy by NVidia's management, who's marketing department is pressuring them to have higher 3DMark2003 scores than ATI?
OR
b) Has some low level device driver programmer (intern?) looked to get some easy brownie points by "optimising" the drivers for 3dMark2003 in a slightly clunky way?
Either is quite interesting :) I've been a victim/perpetrator of both in the past.
But isn't there a very quick solution for Linux once SCO discloses which are the "hundreds of lines of code" which were taken from SCO's UNIX source code? Can't we just rewrite the source code to perform a similar function to what's already there, but with a brand new open source implementation?
As far as I know, it's the source code which is copyrighted, and NOT the algorithm. So once SCO discloses in court what the offending lines of source code are, can't we rewrite those lines, distribute a kernel patch, and hey presto, the code is open source again?
Adequate documentation of code isn't just a problem for open source projects - pretty much everywhere I've worked the documentation tends to be poor unless there is a strong contractual obligation otherwise.
If the documentation is for people contributing code to the project, Doxygen is great for generating documentation from your source code, which you can annotate with javadoc-style comments. Great for seeing how convoluted your inheritance trees are becoming.
If the documentation is for people who use the project, but aren't coders, then I'm a bit more stuck. Basing it around a markup language like HTML or LaTeX would make it easiest to convert into whatever document formats people require, and if it's in HTML you can just publish it on the web for lazy people like me who don't want to download the whole docs.
Matt