LiveCode Performance & Shortcomings Discussion
Posted: Sat Oct 26, 2013 5:36 pm
Hi all,
The subject of this post sounds very harsh, but I promise, my opinion is quite the opposite when it comes to LiveCode. However, I often ask myself:
"Why do so many people bother to submit themselves to daily *figurative* root canals by using Object Oriented Programming (OOP) languages such as Java/C++ when so much can be done quite simply in LiveCode"?
I understand there are limitations to ultra-high level languages (like LiveCode) in regards to what low level access to various features the developers of said language have created for us to use. For example, if the LiveCode development team hadn't written the bridge between the OS specific indication of a "touch" event on a phone, we would be forced to do it ourselves through coding in these OOP languages. However, nearest I can tell, the LiveCode folks have covered all the major things you need to tie into as a developer. Also, provided they did a good job with this, there really shouldn't be a notable performance disadvantage in using LiveCode to do something like array manipulation versus using an OOP language.
Is there something I'm missing here? I am all about choosing the right tool for the right job, but the more I use LiveCode, the more I realize people are really missing out on being productive when choosing to do the majority of things in OOP languages. With all of that said, I do enjoy Objective-C and the Cocoa framework from a academic perspective, because of it's elegant, consistent structure (when compared to .NET). But, at the end of the day, LiveCode all the way, for me (until I reach some sort of limit, at which point, I will write a bridge between this lower level thing and LiveCode) so my productivity can continue.
Now if only someone can write a bridge between LiveCode and browsers to replace learning HTML, CSS, and javascript for front-end web development...
Let the conversation commence!
Cheers,
Tom
The subject of this post sounds very harsh, but I promise, my opinion is quite the opposite when it comes to LiveCode. However, I often ask myself:
"Why do so many people bother to submit themselves to daily *figurative* root canals by using Object Oriented Programming (OOP) languages such as Java/C++ when so much can be done quite simply in LiveCode"?
I understand there are limitations to ultra-high level languages (like LiveCode) in regards to what low level access to various features the developers of said language have created for us to use. For example, if the LiveCode development team hadn't written the bridge between the OS specific indication of a "touch" event on a phone, we would be forced to do it ourselves through coding in these OOP languages. However, nearest I can tell, the LiveCode folks have covered all the major things you need to tie into as a developer. Also, provided they did a good job with this, there really shouldn't be a notable performance disadvantage in using LiveCode to do something like array manipulation versus using an OOP language.
Is there something I'm missing here? I am all about choosing the right tool for the right job, but the more I use LiveCode, the more I realize people are really missing out on being productive when choosing to do the majority of things in OOP languages. With all of that said, I do enjoy Objective-C and the Cocoa framework from a academic perspective, because of it's elegant, consistent structure (when compared to .NET). But, at the end of the day, LiveCode all the way, for me (until I reach some sort of limit, at which point, I will write a bridge between this lower level thing and LiveCode) so my productivity can continue.
Now if only someone can write a bridge between LiveCode and browsers to replace learning HTML, CSS, and javascript for front-end web development...
Let the conversation commence!
Cheers,
Tom