Personally I dislilke Java very much, but your arguments seem rather, 'childish'.
Java being a higher level language (compared to the likes of C/C++) is very well known and relatively easy to pick up. OP's project being open source, I think they've made a good decision (whether it is the right one appears to be irrelevantly debatable).
It is true that Java applications and the JVM itself take up quite a bit of memory during runtime, but unless a person's aiming to run this project on anything other than a desktop or similar hardware 50mb is of no concern. Where did this 50mb come from anyway.
You said "probably", which suggests that you either don't know or are uncertain whether your potential version of the project written in Go would have a better memory footage. Don't forget Go is also garbage collected which could well lead to unpredictable memory footage and runtime performance just like any garbage collected language.
And why wait for things to get fleshed out and not start now? @
alyphen and @
SkyHunter have done an amazing job so far of setting up the ground work with the packet analysis. Between Java and Go, there is no direct mapping anyway.
I'm all for doing this in whatever the heck language everyone prefer, the more people throwing their hands at this the merrier. Personally I will write one in C++. So instead of being ultra defensive and attack the project, why don't you just say "Java sucks big time, I will write one in Go". Let's all be nice to each other
Java is not a game engine. I don't think I will ask why LUA would work better...
Click to expand...