1 |
I would say writing a game with a scripting language is not possible. |
2 |
Or is there any? Are our machines today powerful enough for that? |
3 |
|
4 |
Java totally sucks! The licence of sun is horrible! And its awfully slow. |
5 |
|
6 |
So I am running short in options... |
7 |
|
8 |
|
9 |
Am Mittwoch, 24. August 2005 14:22 schrieb Matan Peled: |
10 |
> Markus Döbele wrote: |
11 |
> > The code I think is not the problem. But I think it is still a lot of |
12 |
> > work. By the way I don't like C too much (we had a C Version once and |
13 |
> > only encountered problems all the time :-( Buffer overflows and all this |
14 |
> > nice stuff is a big problem of this language!) |
15 |
> > |
16 |
> > Maybe a C Fan is reading this and likes to do it. |
17 |
> > |
18 |
> > I started as a Assembler Programmer on the Atari ST (68000 Rulez!!!) |
19 |
> > But all this is too much effort. Purebasic has a very syntax and for a |
20 |
> > basic dialect a very good performance. |
21 |
> |
22 |
> Well, the code IS the problem. As you see, Nick Rout has already made an |
23 |
> ebuild, but the code is a real problem. |
24 |
> |
25 |
> Lets deal with the most obvious problem with not being able to compile your |
26 |
> sourcecode - Archs different than x86. PureBasic seems to be able to |
27 |
> compile for Windows, AmigaOS, and Linux/x86. What about Linux/PPC (Linux on |
28 |
> Apple) users? Theres quite a few of them. They can't run your game without |
29 |
> an emulator... |
30 |
> |
31 |
> Yes, is pretty low-level, and you have to take care of your own memory... |
32 |
> But coming from an assembler you should be used to this, right? |
33 |
> |
34 |
> Anyway, I can perfectly understand your aversion from C... |
35 |
> |
36 |
> The "best" languages to write a cross-platform application with are (I'm |
37 |
> probably going to get flamed missing some, but anyway) C, C++, Java, |
38 |
> Python, and Perl. |
39 |
> |
40 |
> Ruling out C (you don't like it), C++ (Too much like C, and we don't need |
41 |
> OO anyway), Java (Too bloody slow), we are left with the interpreted |
42 |
> languages, Python and Perl. |
43 |
> |
44 |
> I would suggest Python, as it has a very nice syntax and is quite easy to |
45 |
> pick up. Its slower than asm/c, but it may be faster than you expect. |
46 |
> |
47 |
> Overall, I suggest using C and SDL, coupled with a good debugger (gdb is |
48 |
> good, and I hear valgrind is bloody awesome for memory related issues), but |
49 |
> if you decide you don't want it, Python is good too. |
50 |
> |
51 |
> Binary packages are fine, but generally considered to be evil. |
52 |
> |
53 |
> -- |
54 |
> [Name ] :: [Matan I. Peled ] |
55 |
> [Location ] :: [Israel ] |
56 |
> [Public Key] :: [0xD6F42CA5 ] |
57 |
> [Keyserver ] :: [keyserver.kjsl.com] |
58 |
> encrypted/signed plain text preferred |
59 |
|
60 |
-- |
61 |
gentoo-user@g.o mailing list |