4 ms·
You're not wrong, but I think with lua the fragmentation problem is pushed out to the app developers who embed lua in their various games and applications. Do t
by TheZenPsycho 13y ago
You're not wrong, but I think with lua the fragmentation problem is pushed out to the app developers who embed lua in their various games and applications. Do the developers of lua concern themselves much with this? I suppose slightly, but mostly in the form of documenting what's different and how to convert old code to new code. The lua philosophy seems to be that a simpler/smaller implementation trumps backwards compatibility.
- Aldo_MX 13y agoYou are also right, but when a project has small adoption, usually the users are people that feel identified with and like the project. But suddenly the project becomes a product, and the product gets adoption (every time more). The users will use your product because of different reasons (ex. it's what other people use / it's what can solve better X problem / it's what I got recommended / etc.), the users that like and feel identified with the project become a small niche in comparison with the people that need the product. The users become the ones that shape the product, you have to balance between: Feature A. Which is what you want to do for the project. Feature B. Which people are telling you they need for the product. Will you develop exclusively "Feature A"s, because you are following a philosophy? Think for a moment what would had happened if Microsoft had adopted Lua for IE3 instead of reverse engineering Netscape's JavaScript (assuming that IE would have still won the 90's Browser Wars thanks to Lua). Are there flying cars in that parallel universe? Is Lua uglier than today's JavaScript? Has Douglas Crockford written Lua: The Good Parts yet? :)