LOVE should stop ignoring serious developers
Posted: Thu Feb 16, 2023 9:16 am
I have been seeing LOVE ignoring serious developers for a long time now.
Many people including me have come to roadblocks and asked about the issues & feature to fix them & they have been denied because of wierd reasons like the feature would not be "LOVE"ly.
For example,
I had hit a roadblock last time about implementing vectors efficiently :-
viewtopic.php?f=3&t=94270&p=253245sid=f ... 91#p253245
FFI is the way to go only if you have JIT. Without JIT, FFI is orders of magnitude slower (its much worse than tables).
Guess what?, they removed JIT from Android, iOS doesn't even support it anyways. And because of their ARM problems, its not even supported in M-series macs & any other Windows laptops that may come in future (ARM is the future of laptops).
I have seen several threads asking for an effecient vector library to be built-in to LOVE but the people just shun it.
Now people will say that its a language problem?!, Its not! pretty much every other game engine or library comes with vector stuff built-in.
Its a basic necessity for games.
Another example,
Lets say I'm building a text editor inspired by rxi/lite then also I'm better off not even building it (Thats why rxi avoided LOVE). There is no data structure for efficiency. In C we have mutable strings for efficient string manipulation. I can't expect lua to grabage collect everytime someone types an alphabet on the editor!
Again people will shun it saying its a language problem ?!, Maybe it is!, BUT ITS IS very much manageable by exposing a memory aligned array like C (holding same datatype throughout, torch does something like that). Im pretty sure gamdevs need arrays for general computing and some AI too. Atleast we can have the basic & efficient Array? No?
I understand JIT is a language problem.
But what is LOVE doing to fill the holes with JIT OFF, for gamedevs?
I would conclude saying that the community hardly cares about the actual requirements of a serious game & that's limiting people & also severally limiting games and apps to be "built with LOVE".
Many people including me have come to roadblocks and asked about the issues & feature to fix them & they have been denied because of wierd reasons like the feature would not be "LOVE"ly.
For example,
I had hit a roadblock last time about implementing vectors efficiently :-
viewtopic.php?f=3&t=94270&p=253245sid=f ... 91#p253245
FFI is the way to go only if you have JIT. Without JIT, FFI is orders of magnitude slower (its much worse than tables).
Guess what?, they removed JIT from Android, iOS doesn't even support it anyways. And because of their ARM problems, its not even supported in M-series macs & any other Windows laptops that may come in future (ARM is the future of laptops).
I have seen several threads asking for an effecient vector library to be built-in to LOVE but the people just shun it.
Now people will say that its a language problem?!, Its not! pretty much every other game engine or library comes with vector stuff built-in.
Its a basic necessity for games.
Another example,
Lets say I'm building a text editor inspired by rxi/lite then also I'm better off not even building it (Thats why rxi avoided LOVE). There is no data structure for efficiency. In C we have mutable strings for efficient string manipulation. I can't expect lua to grabage collect everytime someone types an alphabet on the editor!
Again people will shun it saying its a language problem ?!, Maybe it is!, BUT ITS IS very much manageable by exposing a memory aligned array like C (holding same datatype throughout, torch does something like that). Im pretty sure gamdevs need arrays for general computing and some AI too. Atleast we can have the basic & efficient Array? No?
I understand JIT is a language problem.
But what is LOVE doing to fill the holes with JIT OFF, for gamedevs?
I would conclude saying that the community hardly cares about the actual requirements of a serious game & that's limiting people & also severally limiting games and apps to be "built with LOVE".