> Is it because they secretly realize they don't know C?
I will answer this: Yes, we realize that we don't know C. No, we do not keep it secret. If you are used to modern C++ with vector, string, *_cast, shared_ptr etc. it is not trivial to do things in pure C. I fear that I even will have to use malloc (*quakes in terror*) at some point if I use Objective-C. Also, in modern C++ everybody use the RAII idiom for all types of resources, while in Cocoa it seems to be standard to do manual reference counting - another difference that makes it more difficult.
However I did try it, and discovered that it was not that hard after all! At least for simple programs I had no trouble. But for more complex things I would probably have to go the Objective-C++ route. C is just too much effort for me.
What does that expression refer to, anyway: To the invention of bread (and of knives), or to the concept of pre-sliced (i.e. before you buy it) bread? I always found that expression a bit funny, especially since pre-sliced bread is (IMHO) a terrible idea! Makes the bread dry and tasteless...
Atgeirr
To me, the key thing to freeciv is network play. In fact, when I first played freeciv (around early '97 I think), there was no AI! Network play was the only thing. At this time, the only comparable commercial product was CivNet (Civ I multiplayer), which I have never tried. But freeciv would work over the internet, and being free, there was no problem setting up large games with many players.
A few years later, an AI was made for freeciv, and that AI kicked my butt without cheating! It was far, far better than the AIs of Civ I/II (and even Civ III, I think!), although it didn't handle all aspects of the game at the time. That AI tought me how to play the game!
So while the game design was not new, there were many small things that made freeciv a better game than the originals.
In Norway, it's called informatikk, which would translate to informatics or something like than. It may be that the two terms cover slightly different things, though.
> Is it because they secretly realize they don't know C?
I will answer this: Yes, we realize that we don't know C. No, we do not keep it secret. If you are used to modern C++ with vector, string, *_cast, shared_ptr etc. it is not trivial to do things in pure C. I fear that I even will have to use malloc (*quakes in terror*) at some point if I use Objective-C. Also, in modern C++ everybody use the RAII idiom for all types of resources, while in Cocoa it seems to be standard to do manual reference counting - another difference that makes it more difficult.
However I did try it, and discovered that it was not that hard after all! At least for simple programs I had no trouble. But for more complex things I would probably have to go the Objective-C++ route. C is just too much effort for me.
Atgeirr
What does that expression refer to, anyway: To the invention of bread (and of knives), or to the concept of pre-sliced (i.e. before you buy it) bread? I always found that expression a bit funny, especially since pre-sliced bread is (IMHO) a terrible idea! Makes the bread dry and tasteless... Atgeirr
To me, the key thing to freeciv is network play. In fact, when I first played freeciv (around early '97 I think), there was no AI! Network play was the only thing. At this time, the only comparable commercial product was CivNet (Civ I multiplayer), which I have never tried. But freeciv would work over the internet, and being free, there was no problem setting up large games with many players.
A few years later, an AI was made for freeciv, and that AI kicked my butt without cheating! It was far, far better than the AIs of Civ I/II (and even Civ III, I think!), although it didn't handle all aspects of the game at the time. That AI tought me how to play the game!
So while the game design was not new, there were many small things that made freeciv a better game than the originals.
Atgeirr
Quark 3.3? I still prefer 3.1... They changed some of the shortcuts I was accustomed to between those versions, so I prefer the old one.
In Norway, it's called informatikk, which would translate to informatics or something like than. It may be that the two terms cover slightly different things, though.