This topic contains 4 replies, has 4 voices, and was last updated by 
Xaron
2 years, 2 months ago.
-
Posts
-
hi, been out of programming for a while , thought i might get back into it again. so thw question is as stated in topic.
IS monkey2 a workable game programming tool yet. or should i stick with monkey X Studio for a while yet ?
Monkey2 is still in WIP but is stable. You’ll have more trouble learning it because the big lack for now is the docs and other tutorials.
Also for mobile and HTML5 it works but it is more complicated than Monkey-x because you’ll have to open the projects in androidNDK/x-code. And I’m not sure you can run an IOS project in the simulator so you’ll may be need a iMobile and an Apple dev account to run IOS code (must be veryfied).
I never compiled to HTML5 thru emscriptem but I saw some people having trouble with the emsciptem configuration. With monkey-x the HTML5 target is the easiest one to get running (and is free as well as desktop targets). It has also the fastest compilation time.So if you want direct result for mobile or html5 production Monkey-x is still better I think. If you want better performance for android, mx2 is theoretically faster as it uses the NDK and not Java.
If you want to program for fun, mx2 has more programming features but some modules are not complete. (no easy custom shaders with mx2’s mojo(planned not immediately), in monkey-x’s mojo2 they are available for example.)
The fact that mx2 is in WIP is fun in some ways but can be boring if you want to get things done fast.
Monkey-x is a mature language and works very well. There seems to be not too much people on the monkey-x forum but you’ll have answers fast I think. People who are used to it doesn’t need to ask questions anymore..
If you use Monkey-x with mojo2 and strict mode you’ll be able to switch to mx2 very easily, even port code if using functionalities available in mx2.
Monkey-x Studio is coming with ignition-x and therefore is using mojo1 so it won’t be easy to switch to mx2.
I’d rather buy the Pyro framework instead of ignitionX if you want a complete framework with examples. This way you can switch to mx2 easier because you’ll be using mojo2 and pyro2 exists for monkey2 free!
For the monkey-x IDE you have mollusk witch is osx compatible too (but not linux). Jugnle IDE seems to be a bit more advanced than mollusk but is windows only. You can use the original Ted IDE too (or use open source jentos IDE based on Ted but its a bit buggsy sometimes).
For the MX2 IDE you have Ted2,Ted2Go(fork),Ted21(fork) but non are as advanced as jungle or mollusk. Mollusk has some MX2 capabilities but I’m using ted2GO though I own mollusk (I should retry mollusk with mx2 some day)-Monkey-x Studio(ie: monkey-Pro, Jungle IDE, Ignition-x)=99$. (but switching to mx2 not easy)
-Monkey-Pro(39$)+mollusk(10$)+Pyro(65$)=114$ (good for switcing and good to stay monkey-x1 too!)
-Monkey2+Ted2+pyro2= patreon/donate what you want!Mx2 is a bit more strict, more strongly typed, but it’s basically the same syntax with a bit more possibilities.
Short answer: When you want to go mobile, use Monkey 1 for now. For desktop Monkey 2 is fine.
If you have been out of the programming scene for awhile I would recommend starting out on Monkey-X. Unless you are feeling brave and can workout what to do based on the code examples (included in Monkey 2), documentation (a bit thin ATM but improving) and posts on the forum here. It certainly would not hurt to check Monkey 2 out as it’s free to use.
There is a nice base of video tutorials here for Monkey-X you might find helpful in getting started.
Good luck.
Plus as soon as Monkey 2 is more mature it’s not a big deal to switch from Monkey X. Just use mojo2 with Monkey X instead of the older mojo which makes a later change to Monkey 2 even more easy.
You must be logged in to reply to this topic.