Is AsyncGetToFile truly Async if you have to wait on a port?
I have been developing for roku for several months now and one thing still boggles my mind.
Why name a method AsyncGetToFile if it is truly not Asynchronous? If i have to create a message port and put a wait timer on it for a message to appear then this is not Asynchronous at all. Why didn't the developers at roku think that it would be a good idea to allow image loading straight to an object and then it would appear whenever it was loaded? Am I completely lost or does the Roku Development team not know the meaning of the word Asynchronous. I develop for applications with iOS, Android, C#, and Java and never have run into a programming language that is as horrible as brightscript.
If anyone has a truly Asynchronous way to download images, please enlighten me.
Why name a method AsyncGetToFile if it is truly not Asynchronous? If i have to create a message port and put a wait timer on it for a message to appear then this is not Asynchronous at all. Why didn't the developers at roku think that it would be a good idea to allow image loading straight to an object and then it would appear whenever it was loaded? Am I completely lost or does the Roku Development team not know the meaning of the word Asynchronous. I develop for applications with iOS, Android, C#, and Java and never have run into a programming language that is as horrible as brightscript.
If anyone has a truly Asynchronous way to download images, please enlighten me.
"as horrible" as B/S. You'd find some languages that are less horrible yet many that are more horrible. Looking for exact match in "horribleness" is like comparing float/doubles for == equality. Somewhat more seriously, B/S i pretty decent language, i would's cluster it somewhere with Perl and Tcl. And as subjective opinions go, i'd say Java the Hutt is much more horrible
