March 2021
Mo Tu We Th Fr Sa Su
<< >>


Haxe Meeting

Posted on May 12 2011

The Haxe Meeting 2011 was a real success ! Very nice, talented and passionated people, great talks (thanks to all the wonderful speakers !) and perfect community interaction / networking.

This year we were still able to fit all together into the same restaurant, but I guess with increasing Haxe success and awareness, next year will be hard ;)

As for the main announcements :

  • Haxe/C# and Haxe/Java are on a good way (thanks to Cauê Waneck !)
  • Features preview for Haxe 3.0 (check my talk or my slides)
  • Haxe got a new logo (thanks to PowerFlasher)


See you next year !

  • totor
    May 13, 2011 at 00:46

    Thank you for setting up the haxecon and sharing all the informations to those who couldn't come. (i hope next year)

    I would LOVE though to have the videos in another format like mp4 podcast because my internet connection is too slow to wacht the webcast.

  • Christopher
    May 13, 2011 at 23:14

    It was really an awesome experience to be there! Once again thanks Nicolas for organizing it and looking forward to the next one :-)

  • Jun 27, 2011 at 19:06

    To bad I could not come to France (Actually, there is a lot of things happening there that I want to go to).

    This comment is actually not for this post, but rather this one (about Node.JS) but I got this message thrown in my face:
    You can't comment on an old post (spam protection)
    You could have told that before I wrote a long comment ×-(

    Anyway, here's what I wrote:

    I would not say that Node.JS is doing anything wrong, it just does things in another way.

    I will not lie, I might be a bit biased towards the Node.JS approch, infact; I like it very strongly. Perhaps because I have practiacally grown up with event-driven programming, Asyncronus coding style and JavaScript.

    I think that the real question is wether or not Node.JS suits your needs or not. Depending on your application it might be a perfect match (You does not have any long-running code, or you are able to factor out your code in an appropiate manner to avoid long-running code). Like serving a map with Node.JS and having Mapnik (C++) rendering it.

    You should not forget that V8 is blazing fast, something like 16x faster than PHP on a single-core 32bit x86 CPU running Ubuntu Linux. I does not know how good it compares towards NekoVM/HaXe - but I guess the difference is not that much. Also there is one process running all the time soo all the common resources can stay in memory (if there is enought of it) insted of say PHP where the whole application must be loaded off disc interpreted, and do its initializing sequence wheras in V8 all the JS is already compiled to machine code for every subseqent request. Yes, there is stuff like bytecode caching, memcache and stuff to PHP as well - but it is not that easy to setup as just installing Node.JS (and from my own experience - a lot of PHP hosting services suck, but they are relatively cheap).

    As another way to look at it, Node.JS is practically forcing you to write applications in a such way so that you can scale horizontally easily (Buying more cheap machines) instead of vertically (Buying one larger high-costly machine). So that is one way to look at its ‘achilles heel’ like a strenght. Or maybe one should use Erlang instead ;) But from what I can tell, Erlang does not solve the mundane medeling of processes/threads problem that you wish to avoid.

    I would guess it all boild down to choosing the right tool for your needs, based upon taste & preferences and not to say the least; your needs for your project at hand. I do not know what kind of secret data you you are processing for your games, but I could guess that it is to veryfy the playsers score and progress so that they don't cheat - if so, the you could send out that for processing to three other random players and have them perform the same computation and check the result of that. Just an Idea I had.

    However I find myself partically fond of using Node.JS for writing commandline tools, and small utilities that run in the browser. No need for clumpsy setup of apache, modding /etc/host file et.c.

    @Julian Kennedy: I use to say that old Systems doesn't rust - but they aren't fast either :)

Name : Email : Website : Message :