warning (!) OFFTOPIC ahead (!)
^
^^
sve ima svoje...
meni samo nedostaju vremena kada su se pojavljivala stvari 5 godina ispred svoga vremena;
danas je sve evolucija ili puko asimiliranje ekstravagandnih tehnologija od strane x86 kolektiva...!
tracak nade je u ARM sferi i pogotovo AMD CND inicijativi.
ali nije sve tako crno
- ono sto je mene impresiralo ovih dana (izuzev ovog razbacivanja GHz i TBs
) je .... ..... ..... zaboravio sam kako se zove framework koji su koristili za razvoj "Legends of Grimrock"
link - u svakom slucaju kód za igru mozete menjati i u realnom vremenu se interpreteraju sve izmene! (...dok ne userete motku
) (ne mogu da pronadjem link, morali bi da prekopate njihov blog)
---
EDIT: lol! evo ga link!
http://www.grimrock.net/2012/07/25/making-of-grimrock-rapid-programming/
Making of Grimrock: Rapid Programming
"First a bit of background. I’ve been programming for more than 20 years, starting from Basic on the venerable C64, moving on to AMOS, 68000 assembly and C on the Amiga, and after that I’ve been programming mostly in C++ for the past 10 years or so. I’ve also tried other programming languages such as Scheme, Java, D, Objective-C and Python (although very briefly). Today games are written mostly in C++ because it has very good performance but more importantly in my opinion because it is the de facto standard, in other words almost all libraries and tools (especially on the consoles) are geared towards C++ development.
A typical game development workflow when working with C++ is something like this:
1. Design and write code in IDE (IDE being basically a glorified text editor)
2. Compile code (compilation turns the source code into machine executable sequence of instructions)
3. Run the game and wait for it to load
4. Test your changes (play the game to the spot where you have made your changes or load a saved game if you’re lucky and the save game is still compatible with your code changes)
5. Go back to step 1
....
In game development, especially when tuning game play, the code changes you make in step 1 are often very quick to make and development speed can become bottlenecked by redundant steps 2-5.
...
The single best thing about Lua for us is that code can be compiled dynamically while the game is running. This is such a major difference to working with C++ that most jaded C++ programmers can’t even grasp the full implications of this. At least I couldn’t before giving Lua a go.
Basically with Lua all the unnecessary steps 2-5 vanish completely. No more waiting for code to compile; the dynamic compilation step is lightning fast in Lua. No more waiting for the game to launch because the game is running all the time. No need to play the game to the right spot because you’re there all the time!"
---
sorry ako je ovo trolovanje teme, ali svako moze lako da preskoci ovaj post jer na pocetku stoji OFFTOPIC
