Hey, thats normal. I mean, where do you get a usable documentation. My personal top canidates:
Unusable Documentation: Symbian/S60 (and what is a hbufc anyway?) Winamp Maki (TODO since years) Alsa (complete documentation of all classnames. Wow)
Best documentation: Java Ogre
Working with external companies since a couple of years I can tell you that I never got a usable documentation. After all, why should they risk the maintenance contract going to their competitiors.
Hi,
I am completly against Python to start programming. The syntax is not hard, but Python gives you nearly no information where to search for an error.
Perl with pragma strict gives more information but again, who wants to start with Perl?
C is good but you can't write C without pointers and there is a lot that you can do wrong when using pointers.
I would propose Java or Java Script. Java is good, clear, visual and you can write RoboCode.
Java Script can be used together with Html to create flashy web-sites and you can find a ton of examples on the web.
I loved Jagged Alliance 1 so I had to buy the next release. The game changed my life in two ways:
This was the last game I bought. It had so many bugs that even the patches couldn't solve. I will never buy a regular game again (unless I get the source code!)
I will never say a word agains children protection. I can still remember the scene. Three team members were hiding in a small wooden shack and waiting for the bad guys to come in (they were just some agressive farmers looking who's makeing troubles).
So they came in and I shoot them with the pump guns from point blank. Bam Bam, both dead.
Then I started thinking. How many guys do I have to kill to win the game? Is the evil dictator really worse than me?
I tried to get to a wounded enemy with my first aid kits but I never managed. There was no way to disable the enemys in a less-than-final way. No tear-gas, no rubber bullets.
I think that minors have to be protected against such kind of games.
On the contrary. This paper is most practical.
Just use this mechanism and you can find thousands of errors in an already tested system.
What impressed me most was something like this. if( complex statement );
do=that;
Notice the semicolon! This kind of errors are very hard to spot and they can stay in the code forever.
I will propose to use a code-checker like this in our software to improve the quality.
Yes.
Dune is a good read but Herbert has problems justifying his world.
Why no Computer/Roboter/... Some strange revolution.. hu??
Only a few writers really manage to stage a belivable world. David Brin, e.g. not only with his uplift series, but also with most of his other books.
Even when he writes space opera it is belivable.
Then the short stories of George R. R. Martin. Space Opera too, but also no Deux et machina needed like in so many other books (Asimov included).
William Gibson does also a very good job at describing Science as everyday tool.
What happens if you can enhance your body?
Not only use it for your favorite Super-Stormtrooper, but also for fun, profit and of cause sex.
Hi,
I have some experience with larger codebases and I don't think that the tools are the problem.
I think most likely the problem is with the project management.
The politic would be simmilar to the one used in my firm: "Change only to fix bugs. Change only your parts."
This leads to a codebase that works. But it also leads to a maintenance nightmare as only code is added but older code cannot be reviewed.
Keep in mind: in a code review you change working code to make it simpler, more understandable and easier to handle.
The only solution to this is a BIG change where every developer has to touch every file. In this way he can change all the little things he always wanted to change but never was allowed to.
In the end every change will lead to a multitude of new bugs, but I think re-implementing a big chunk of your system would be worse as it will lead to a big chunk of untested code.
For references look at other re-implementations and then think about the time it took. Windows NT (4 years?) Netscape (3 years) Mac OS (how long?)...
So again. You need the rights to change old code and then start doing it.
No.
Don't do this.
After listening a term to a course called patent law for engineers I learned one thing: You need a lawyer.
He not only knows how to write the patent to get maximum effect (you can do a lot of things wrong there) but can help you getting the patent right the first time.
If the patent is really worth it, the costs are irrelevant.
On the other hand, if you just want to do it for your own sake go ahead.
Wrong.
Phone companies have an extremly strong market power. Just look at the number of phones sold. Then compare to the number of palms sold.
Did you know that the Noka Communicator is the most sold Organizer?
This is the market power and this is why all newer phones will get one of the following features.
1. MP3
2. Camera
3. Java
The newer phones are getting better and better. Who needs a Gameboy if he has a java phone with colour screen? You can download applications (say games), new levels, even play with others.
My opinion is that J2ME will be the future. Who knows, maybe we will sometimes get a phone where you can switch the whole UI because it is all implemented in Java.
Slashdot Mirror
Hey, thats normal.
I mean, where do you get a usable documentation. My personal top canidates:
Unusable Documentation:
Symbian/S60 (and what is a hbufc anyway?)
Winamp Maki (TODO since years)
Alsa (complete documentation of all classnames. Wow)
Best documentation:
Java
Ogre
Working with external companies since a couple of years I can tell you that I never got a usable documentation. After all, why should they risk the maintenance contract going to their competitiors.
Hi, I am completly against Python to start programming. The syntax is not hard, but Python gives you nearly no information where to search for an error.
Perl with pragma strict gives more information but again, who wants to start with Perl?
C is good but you can't write C without pointers and there is a lot that you can do wrong when using pointers.
I would propose Java or Java Script. Java is good, clear, visual and you can write RoboCode.
Java Script can be used together with Html to create flashy web-sites and you can find a ton of examples on the web.
I loved Jagged Alliance 1 so I had to buy the next release. The game changed my life in two ways:
This was the last game I bought. It had so many bugs that even the patches couldn't solve. I will never buy a regular game again (unless I get the source code!)
I will never say a word agains children protection. I can still remember the scene. Three team members were hiding in a small wooden shack and waiting for the bad guys to come in (they were just some agressive farmers looking who's makeing troubles). So they came in and I shoot them with the pump guns from point blank. Bam Bam, both dead.
Then I started thinking. How many guys do I have to kill to win the game? Is the evil dictator really worse than me?
I tried to get to a wounded enemy with my first aid kits but I never managed. There was no way to disable the enemys in a less-than-final way. No tear-gas, no rubber bullets.
I think that minors have to be protected against such kind of games.
On the contrary. This paper is most practical.
Just use this mechanism and you can find thousands of errors in an already tested system.
What impressed me most was something like this.
if( complex statement );
do=that;
Notice the semicolon! This kind of errors are very hard to spot and they can stay in the code forever.
I will propose to use a code-checker like this in our software to improve the quality.
Yes. Dune is a good read but Herbert has problems justifying his world.
Why no Computer/Roboter/... Some strange revolution.. hu??
Only a few writers really manage to stage a belivable world. David Brin, e.g. not only with his uplift series, but also with most of his other books. Even when he writes space opera it is belivable.
Then the short stories of George R. R. Martin. Space Opera too, but also no Deux et machina needed like in so many other books (Asimov included).
William Gibson does also a very good job at describing Science as everyday tool. What happens if you can enhance your body? Not only use it for your favorite Super-Stormtrooper, but also for fun, profit and of cause sex.
Hi,
I have some experience with larger codebases and I don't think that the tools are the problem.
I think most likely the problem is with the project management.
The politic would be simmilar to the one used in my firm: "Change only to fix bugs. Change only your parts."
This leads to a codebase that works. But it also leads to a maintenance nightmare as only code is added but older code cannot be reviewed.
Keep in mind: in a code review you change working code to make it simpler, more understandable and easier to handle.
The only solution to this is a BIG change where every developer has to touch every file. In this way he can change all the little things he always wanted to change but never was allowed to.
In the end every change will lead to a multitude of new bugs, but I think re-implementing a big chunk of your system would be worse as it will lead to a big chunk of untested code.
For references look at other re-implementations and then think about the time it took. Windows NT (4 years?) Netscape (3 years) Mac OS (how long?)... So again. You need the rights to change old code and then start doing it.
No.
Don't do this.
After listening a term to a course called patent law for engineers I learned one thing: You need a lawyer.
He not only knows how to write the patent to get maximum effect (you can do a lot of things wrong there) but can help you getting the patent right the first time.
If the patent is really worth it, the costs are irrelevant.
On the other hand, if you just want to do it for your own sake go ahead.
Wrong.
Phone companies have an extremly strong market power. Just look at the number of phones sold. Then compare to the number of palms sold.
Did you know that the Noka Communicator is the most sold Organizer?
This is the market power and this is why all newer phones will get one of the following features.
1. MP3
2. Camera
3. Java
The newer phones are getting better and better. Who needs a Gameboy if he has a java phone with colour screen? You can download applications (say games), new levels, even play with others.
My opinion is that J2ME will be the future. Who knows, maybe we will sometimes get a phone where you can switch the whole UI because it is all implemented in Java.