FUZE NEWS! March 2020 - First video in a new series!
Awesome stuff. ( ** spoilers below** )
Great to know that the array bug has been addressed! Really nice to know it's even a choice to use either by value or by reference. I think for new coders by value is intuitive, and for experience coders by reference is very useful, and the way it is solved is simple and clear. So great job!
I'm afraid that the
varkeyword will always be a debate among developers, but in my opinion it's a very valid keyword to use (even professionally, depending on the language). So I'm happy that it's in there.
Nice surprise to see that strings with newlines that are not escaped, are now supported by the editor. That's modern as well ;)
Overall, great job to all of you involved. I'm happy to work on my next idea for a game in Fuze. (I still need to start, so I won't reveal much yet, but I think my idea will be fun and more original than my previous games). I really hope for you guys that the player will be a success, but it deserves to be with all that free amazing content :P
Great stuff guys. I love the new help pages!
Thank you for the comments everybody. Really happy to hear these are popular changes and being received well. Great to see the excitement for the new language capabilities too :)
Both var and ref are great additions! They will make Fuze feel more like a “proper” language.
The folders in the media library will be super useful as well.
Wow, sounds like you dived really deep to get the best out of the language design for us. And now I have no apology any more to still use so many lazy global values, when there is call-by-reference. ;-) but the code will become more error prone. Good work, I am looking forward to this release, thank you!
Actually, I have a question regarding "ref". Is it restricted to a function parameter? Or can we also use it like a local variable, like
int myvar = 1 ref myself = myvar
Not very useful like this, but say we had structures within structures. Setting variable values with including the base structure names can be lengthy, so it could be like shortening it in both readability as well as perhaps code execution.
@Discostew ref will be only used in user-defined functions to specify how to pass parameters, not on a by-variable basis as you specify there.
This update sounds amazing, I can't wait!
This update is going to be really excited because it opens up more possibility for writing complex algorithms it is what I have been waiting and I am glad you guys are going to implement all of this . I beeen waiting for this so I can use the switch for machine learning using others people games so can not wait and thanks for all your hard work.
Great news! I'm curious to also use reverse farts in my games, thanks for the hints.
refare also game changers, since they'll address my initial WTF moments ... :+)
One question though: Do you think you could add a flag or a setter to enable the old behavior (similarly to
radiants()), so lazy peeps like me do only have to change one line in all their apps?
Alternatively defining a runtime version of fuze against which my game is supposed to run might be neat (
setRuntimeVersion(x)-> 1: no vars, 2: vars and refs and farts, not specified: newest??🤔)...
But thanks again for the great improvements, I like to see the engagement 🤟