What would be for you the top 3 things that we need to fix/improve
to make Haxe more popular ? (in order of decreasing importance)
- build a competitor for ExtJS/Flex that works cross platform.
- "Open source" - show how this is a strength related to how there's no way to simply "shut haxe down" (which is actually a quite common thought), and introduce the Haxe Foundation, also maybe offer through it a paying support plan for companies. This is important to show reliability. Make clear that actually investing in Haxe is investing on the future. Your code will be able to run on whatever is the next hype platform!
We could call this section either "Open source" or "Never gonna let you go!"
- "Open source" - show how this is a strength related to how there's no way to simply "shut haxe down" (which is actually a quite common thought), and introduce the Haxe Foundation, also maybe offer through it a paying support plan for companies. This is important to show reliability. Make clear that actually investing in Haxe is investing on the future. Your code will be able to run on whatever is the next hype platform!
I think this point ("you can't shut haxe down") could actually be a weakness unless you have an official, strong and opinionated group of maintainers. Which haxe doesn't really have for now.
A recurring question is about using SWCs and JS libraries. Flash and JS are all about libraries and interop (assimilate!) is what really allows people to switch to haxe.
- for JS there's a real need for a solution somewhat matching the simplicity of "get a JS lib, drop and use in the project" (porting JS libraries to haxe is NOT a solution imho).
What would be for you the top 3 things that we need to fix/improve
to make Haxe more popular ? (in order of decreasing importance)
What would be for you the top 3 things that we need to fix/improve
to make Haxe more popular ? (in order of decreasing importance)
1. Reduce barrier for JS developers
2. Overhaul Haxelib
It's already been mentioned that Haxelib is littered with undocumented, unsupported and sometimes misleading libraries.
It takes a lot of time for developers to sort through and find appropriate libraries – many people end up on the mailing list looking for support/clarification on a library, many developers end up reinventing their own solution to existing problems (out of ignorance or frustration). Furthermore, every library represents the idiosyncratic conventions of the individual developer – often this clashes with user's own conventions and other libraries (IMO a big factor in the 'reinvent the wheel' mentality)
This all ends up reinforcing a common negative perception of open source platforms – immature, fractured and unreliable ecosystem
Suggestions
3. Working with native should be as easy as possible.
I feel that it is important that 'leveraging native' is an integral part of Haxe's value proposition.
This is applicable across all targets - there is so much existing code out there in native languages that doesn't need to be reinvented/ported. Maintaining externs for large native APIs adds an overhead when those APIs are constantly evolving.
I agree with Philippe's suggestions around reducing barriers around leveraging existing javascript – while strictly typed externs are easy to make (once you know how), to newcomers it feels like a big hoop to jump through just to work with native.
Anything we can do to make this more automated, or more forgiving is a good thing.
Some ideas around this:
I guess we are on a nice road to increase the contributors. We've been
discussing GitHub at some point but I still think that might make too
many people keep their own fork with their own changes, which is not the
best for a common language which require more stability.
What would be for you the top 3 things that we need to fix/improve
to make Haxe more popular ? (in order of decreasing importance)Hi all,My top three are:1. Reduce barriers for JS developers to get on board2. Overhaul Haxelib (popularity/featured libs, best practise guidelines, specific platform/haxe version compliance)3. Make working with native code as seamless (and friendly as possible)
This is indeed very important. So far Haxe can make... everything. And trying to be everything is a good way to become nothing :)1.position haxe
is this really for multiplatform? or a safe platform like .net or java?
who are our competitors? who are our target groups
find the strategy
The question I have here, is what would be the exact impact of such decisions ? For instance let's say we decide that building a crossplatform IDE is the best strategical move. Who actually write it ? Does companies give some time or money for it ? Do we have enough people involved for it right now ?
so I would like the decision makers set the priorities for a year. And
define projects.
I'm not convinced by a crossplatform haxe IDE project:
Well that's why I think the strategy is to capture immediate needs: mobile and Flash>JS Flashers/Flexers reconversion.But in both cases what would be the ROI for companies to invest?
...
What would be for you the top 3 things that we need to fix/improve
to make Haxe more popular ? (in order of decreasing importance)
Hi all,
Welcome to [haxenext] group, a place where we will discuss how to bring
Haxe to the next level.
As I explained in my invitation this is an open group, feel free to
invite anybody interested in helping in making Haxe grow and become more
popular. We are especially looking for people investing in Haxe with a
long-term vision.
In order to get started I have a simple question to ask you :
What would be for you the top 3 things that we need to fix/improve
to make Haxe more popular ? (in order of decreasing importance)
Please be very precise while answering this question. For instance
"improving the website" is bit too much abstract.
You're welcome also to provide an actual action-plan proposal that we
could follow in order to make it happen.
Based on your answers we will discuss what needs to be done first, and how.
Thank you !
Nicolas
Hi all,
Welcome to [haxenext] group, a place where we will discuss how to bring
Haxe to the next level.
As I explained in my invitation this is an open group, feel free to
invite anybody interested in helping in making Haxe grow and become more
popular. We are especially looking for people investing in Haxe with a
long-term vision.
In order to get started I have a simple question to ask you :
What would be for you the top 3 things that we need to fix/improve
to make Haxe more popular ? (in order of decreasing importance)
Please be very precise while answering this question. For instance
"improving the website" is bit too much abstract.
You're welcome also to provide an actual action-plan proposal that we
could follow in order to make it happen.
Based on your answers we will discuss what needs to be done first, and how.
Thank you !
Nicolas
Hi all,
Welcome to [haxenext] group, a place where we will discuss how to bring
Haxe to the next level.
As I explained in my invitation this is an open group, feel free to
invite anybody interested in helping in making Haxe grow and become more
popular. We are especially looking for people investing in Haxe with a
long-term vision.
In order to get started I have a simple question to ask you :
What would be for you the top 3 things that we need to fix/improve
to make Haxe more popular ? (in order of decreasing importance)
In order to get started I have a simple question to ask you :
What would be for you the top 3 things that we need to fix/improve
As a Linux user I would love to see an IDE which is usable. (Maybe somthing like could9, it would be cross platform and could be written in Haxe; again this could be a community project.)