Re: lua-l Digest, Vol 5, Issue 135

[KHMan <keinhong@...>]

On 12/28/2010 3:09 AM, Shamun toha md wrote:
> [snip]
> But the LACK of LUA seems very frustrating related to third party
> libraries. Because LUA it self is a language it has nothing to do
> with other libraries. But third party libraries seal or trade
> marks are very confusing!!! which mention "MurgaLUA or XYZ powered
> by LUA", after trying with those, when you reach to some advanced
> level it shows libraries are not working nor anyone is
> responsible, which is very frustrating for example: ProteaAudio
> for Lua binding, its a nightmare, no body is available for this.
> With ZEND Framework you have someone responsible for each
> Adapters, which is good for further development or discussion.

As others have said, poor research can be very unhealthy to your 
project. I was looking at Flight Gear just now and they were 
having a problem with an unsupported clone named Flight Gear Pro 
that just wants to grab people's money. If you do things on the 
Internet without proper checking, well, you will get burned very 
quickly.

So quit complaining about this and that. You cannot blame anyone 
else for your own poor research. It's a project management issue 
-- your project management issue.

Only you can get your project done. No third party has any duty to 
provide free resources for your convenience. If you got dependable 
software for free, then thank those who shared it with the world.

THERE IS NOTHING this community can do about third party libraries 
or aggregating libraries. NOBODY is going to aggregate all those 
libraries (for free), fix all the bugs (for free) and give 
everything to you (for free) so that you can happily do rapid 
development. If we had the time and manpower resources, someone 
might have done all this by now, but no, there isn't.

Very, very few of us would have confused the proteaAudio Lua 
bindings as official stuff. EVEN WITH OFFICIAL SOURCES there are 
no warranties or guarantees that anything Open Source will work. 
Open Source source code just means it's shared, it doesn't mean 
you can depend on anything. If anything blows up, it's not their 
fault -- it's your fault. Be very careful what you choose to 
depend upon.

Any third party libraries you CHOOSE TO DEPEND UPON entail risk 
and careful decision making. Very few projects go around giving 
away very high quality software indefinitely. Lots of small 
projects or libraries are one-or-two person projects. Big projects 
like Zend run a business -- some people PAY for quality and 
dependability and the large community as a whole benefit from the 
large ecosystem. You got it for free but it DID NOT HAPPEN AS A 
WHOLE FOR FREE. There were lots of resources and lots of people.

So you had problems with the ProteaAudio binding. It's a small 
project so there is risk, but you are given the source code so 
that you can make your own fixes. That's a big point of sharing 
source code, but in order to partake in it, you must have the 
skills to take control of the sources and your destiny. Yes, it's 
nice to do rapid development and whip up a cool app in a short 
time. But if you do not have the skills or resources to do more 
serious development, then you should have only gone for utterly 
mature and dependable components.

Jumping from a springboard into a pool with eyes closed, arms and 
legs flailing, and limited diving experience can get you pretty 
badly injured indeed.

[capitalization for emphasis, sorry if it pains anybody's eyes]

--
Cheers,
Kein-Hong Man (esq.)
Kuala Lumpur, Malaysia