support icon indicating copy to clipboard operation
support copied to clipboard

dev log #4 - trajectory - feedback

Open ruby0x1 opened this issue 8 years ago • 12 comments

Post your feedback and questions on luxe dev log # 4 - trajectory here

ruby0x1 avatar Apr 20 '17 23:04 ruby0x1

As usual a very interesting read! What is still a bit unclear to me is Haxe's role in this - will luxe move away from this entirely or partly?

DjPale avatar Apr 21 '17 06:04 DjPale

It looks like Haxe might fit in as a scripting language at this point. But then the question is: would it make any sense to carry Haxe around when there are other more lightweight scripting languages available?

tanis2000 avatar Apr 21 '17 09:04 tanis2000

Reading this post I'm also concerned about whether Haxe is ditched entirely in favour of C/C++. In my opinion, Haxe is one of the key advantages of Luxe and I would be very disappointed to see it go.

anissen avatar Apr 21 '17 09:04 anissen

Im not webgames guy, but I must to tip my hat on your long road that luxe (and snow and other framworks) did!

mikicho avatar Apr 21 '17 10:04 mikicho

I did not see this coming I have to say, but it kind of makes sense, especially with the web techs maturing. Really really want to know what's the plan for the scripting language though ;)

ghost avatar Apr 22 '17 10:04 ghost

For me as a JS developer, Haxe is the greatest feature of luxe. I am willing to learn C++ if there is no other choice, though.

igorhart avatar May 04 '17 08:05 igorhart

Keep in mind the difference between the core and the user code. You won't have to use c++. Also remember native targets still run on c++ now anyway, the only difference is the amount of layers and how much of the user has to run into or setup.

The post was referring to the core specifically, the benefits were mentioned in the dev logs as well that users having to deal with c++ is not a great thing - the goal was to remove that need (which we have). There's nothing to worry about, there.

I'll add more details soon but definitely I would not make the user code c++ 💨

ruby0x1 avatar May 04 '17 11:05 ruby0x1

Glad to hear that, looking forward to the next dev update 👍

igorhart avatar May 04 '17 12:05 igorhart

I'm waiting to see which scripting language you're going for :)

tanis2000 avatar May 04 '17 12:05 tanis2000

Same here ;)

ghost avatar May 04 '17 12:05 ghost

If really a new language is considered, I think "Kotlin" might be an awesome choice: It compiles to readable js code already, they are working on native target (trough LLVM), the language syntax is really nice, great IDE support and it is even backed by Google now. Looks like a great option.

matulkum avatar May 30 '17 07:05 matulkum

@matulkum thanks for the comment, though the post goes over the choices for the engine core. Kotlin is indeed interesting but not right for the use case mentioned :)

ruby0x1 avatar May 30 '17 15:05 ruby0x1