Last question: How will this work if me and my friends want to sell our game? You might be asking why professionals are using a tool like craftstudio to push out a game.
My friends aren't programmers. I'd rather them trying to figure out craftstudio than teach them opengl/webgl/direct3d.
Everything you build with CraftStudio is yours, entirely (as long as you're using only assets that you own the rights too, obviously) - See http://craftstud.io/terms for details. I wouldn't want to ruin a good platform by providing unfair terms.
Do you think we as a community should be pushing for a potential rewrite of MRI to get rid of the GIL? I feel as if the GIL is what is limiting true ruby performance.
It also seems like Matz and ruby core team don't really give a shit about performance.
It is very possible to achieve a high level of performance on an interpreted language!!
I don't think that it's true that the core developers don't care about performance at all.
There's an argument that removing the GIL would require a lot of effort for little gain (and in some cases decreased performance). It's just not a priority for them.
Of course, every use case is different (sometimes very different), but I haven't ever hit a problem that has caused me to curse the GIL.
Most people seem to flock to the reference implementation of a language rather than alternatives. Which is why most people use CRuby even though JRuby is faster.
Guido should just take it like a man and accept a pull request to merge PyPy's JIT interpreter into CPython.
