4 ms·
I think it's an important distinction - it's "easy to use" as in you can put things on the screen, play sound, etc without having to read documentation or deal
by zamadatix 6y ago
I think it's an important distinction - it's "easy to use" as in you can put things on the screen, play sound, etc without having to read documentation or deal with boilerplate logic/steps longer than the custom code needed. It's not "easy to use" as in Unity where you want to have some complex physics apply to some premade models with certain rendering effects so you learn where to go to get each of those things and how to drop them in together and bam you have a significant portion of a game made for you.
I.e. if you're goal is to make a more advanced game with some polish no it's not great. On the other hand if your goal is to get some simple stuff to appear on the screen in the way you want and interact with it it's great.
- BoysenberryPi 6y agoI get what you're saying and I agree up to a point but I don't necessarily believe the distinction is necessary. LOVE2D is very "easy to use", easier than Raylib in my opinion, and probably has the most extension documentation I've seen for a game framework. https://love2d.org/wiki/Main_Page https://love2d.org/wiki/Main_Page
- anothernewdude 6y agoYeah, I liked it too, right up until I tried to run some games made in it and they wouldn't run because my runtime was too new.
- je42 6y agoi like about love2d that it doesn't prescribe certain way of setting up your code / pipeline. projects like defold / godot a pretty neat but they are more opionionated: they have a hierarchal structure.