I would actually like to start the debate now, so we can get the emotional issues out of the way, and focus on actionable decisions in the limited face-to-face time. I believe if we can work out exactly what the issues are, then we can find *technical* solutions to make everyones life easier.
I would like to know why lime and openfl could not simply use NME for the native components. It seems adding a "nme/lime" source directory would make nme pretty much a superset of lime.
The original arguments of separate projects with an "openfl-tool" are now moot, since you run openfl with "lime" now. Why is this not "nme"?
Lime now combines the templates with the native code. It should also combine the tool too so that you do not need to do synchronized releases, and so in effect become the original nme.
I think the openfl flash*.hx could be auto-generated from the nme nme.*.hx files and therefore would never be out of sync, and all native bug fixes would go into nme .hx files.
To answer the reverse question, of why I don't abandon NME and move to lime/openfl, I feel that:
- openfl/lime are forks of the original code, made with out any real consultation, and the obligation is not on me to move.
- the split projects are technically wrong as far as synchronisation goes. The .hx files need to updated at the same time as the .cpp files
- Code/file/project layout is too unstable for me to work with. I hate breaking backwards compatibility, and I prefer files not to be in different places when I wake up in the morning.
- I prefer the nme name to openfl. Obviously, this is a question of taste, but I think a haxe conversion script can solve this issue to everyones satisfaction.
- I find the coding style very difficult to work with
Hugh
Since Hugh started the discussion and that sadly people don't seem to understand the reach of the choices that were made.
Motion-Twin official view :
This nme/openfl/lime story has just brought more confusion to the haxe users and the openfl fork made the situation worse than ever.
Disclaimer :
We totally understand why Hugh don't want to switch, why Joshua had to fork and why lime had to be created but the situation is much worse. A big problem of communication and little bit of misplaced pride, took over what once was the jewel of haxe power.The Cross Platform flash library.
Despite Hugh arguments, openfl is now much more interesting than nme since it has html5, openal, many fixes and tries to stick to flash spec.
BUT :
Now instead of a slow evolving lib (nme) we have 9 github projects that are interwinded ( hxcpp hxlibc nme openfl openfl-native openfl-html5 lime lime lime-native lime-tools), still slowly evolving, that are not really open source since having them fixed or contributing has a time lag of MONTHES…
Pragmatically, fixes are randomly applied and some new bugs are introduced faster that ancients are resolved.
The most stunning problem being :
- Oh there is a compiler bug/oddity
- Simon/NC fixes it on high level
- Hugh fixes on low level hcpp
- We wait Josh to merge into hxlibc
- We wait for the full lime/ openfl to mirror it
- We find a bug in the fix...repeat wash rince, the fix is several weeks to us.
Which makes a many ricochet for simple fixes...that is very frustrating.
Basically as a production structure we don't want to put our hands in this kind of thing. We just want to have our fixes available asap.
So brothers, You should all get your shit together. The situation is ridiculous.
Basically you provide :
- one cross platform cpp backend
- one cross platform build system
- one cross platform flash library parser/renderer
- one cross platform gl driver
Why not just simply provide these 4 project separated and well maintained without divergence ?
People who want gl do not want a flash capable lib nor a template build system etc...
So despite our great love to Hugh, Joshua, and Sven, Motion-Twin replies, "Come on lads you should really speak together like Raphael suggests because despite your technically awesome talents, your mis-communication are now harming the haxe world."
And yes, you can say you don't care about MT/Froggies advice but we are producing games everyday on a bigger scale with your tools and are actively listening what haxers think and we know a great bunch of them so our view is representative.
We are perfectly aware that this kind of discussion goes nowhere productive but since yall don't seem to talk each other, that should be said.
When openfl was born we were promised a industry grade process to fix/test/release games, we are far fetched from it.
Now some concrete proposals :
Opengl driver separated ( put under haxeFoundation supervision ? ).
It is not acceptable for issues about low level primitives to wait 8 monthes to be fixed because of one another agenda.
Hxlibc terminated and reinstated as a hxcpp fork :
If the need of such a fork is real, because it is unacceptable to need anyone merging Hugh fixes on an alienated code so that users can use them. Since openfl is a private company it has rights to privatise hxlibc, but we open source user being coerced into using it is just harmful, especially since it is not daily maintained.
Lime should use hxcpp by default :
Either we should not be coerced to use something we think is plainly a bad decision (albeit a reasonable choice ) Or it should be daily maintained
All in all Nme/Lime/Openfl should have a daily maintainer ( like what Simon does with the haxe foundation ) because current bug situation is just ridiculous.
The respective Lime / Openfl / Nme people should start working together not side by side.
In a near future, people will get tired of this petty war and everybody here involved will loose something (not us users obviously).
You should all now understand the reach or your acts. When you rename/fork/miscommunicate/stop talking/documenting, there are hundred haxers hurt and thousand of bucks of hard worker days burnt.
Please start getting in your user shoes for the greater good.
Thanks for reading, we understand you might think this is a rant but it is not at all.
We are doing fine by ourselves but are deeply worried that our common baby haxe does not have the cross platform abilities it deserves.
--
Motion Twin ( Indie game dev company, co-mother of Haxe )
--
To post to this group haxe...@googlegroups.com
http://groups.google.com/group/haxelang?hl=en
---
You received this message because you are subscribed to the Google Groups "Haxe" group.
For more options, visit https://groups.google.com/d/optout.
To be clear, I'm not advanced or senior enough in this community to have a valid opinion on how this should be resolved, but I feel can weigh in on one thing in what I think is a more or less objective manner:
For what it's worth, the NME name is very difficult to google:
http://www.google.com/search?q=nme
Compare this to OpenFL:
http://www.google.com/search?q=openfl
Since getting started is such a crucial thing for developers, I think being able to effectively google the core names of things is pretty important.
Obviously lime suffers from the same issue as OpenFL:
https://www.google.com/search?q=lime
--
Sadly I agree that NME is very confusing to a lot of people (sorry Hugh) and it seems I've only started seeing haxe "in the wild" since the popularization of OpenFL - even if this is simply a naming thing it seems to make a big difference.
I'd hate to see the amazing work done by anyone on these projects go to waste though. Good luck with the discussions.
Long time NME fan.
Sadly I agree that NME is very confusing to a lot of people (sorry Hugh) and it seems I've only started seeing haxe "in the wild" since the popularization of OpenFL - even if this is simply a naming thing it seems to make a big difference.
> I have to admit I was baffled when I that NME was continuing on it's own, I thought NME had "become" OpenFL. I think it can only be a bad thing that they both exist in the same space when collaboration would appear to make the most sense.From my point of view, this is exactly the same as someone taking the haxe source code (under the MIT license) and rebranding it "openc#" and wondering why Nicolas is not making contributions to it, even though it is "a much better name".
There are a number of great things that openfl is doing that nme is not. Eg, html5, community interaction and social media bandwidth.
I do not wish to duplicate these in nme. I do not wish for openfl to go away. I don't want anyones openfl code to stop working. I want some constructive software engineering solutions so we only need to maintain one EventListender.hx implementation and one OGLExports.cpp file.
Hugh