- Regarding Eclipse plugin: I did without it as well, and instead opted to put together a simple language module for TextWrangler to at least get some syntax highlighting.
As Enterr noted, requiring developers to develop specifically for the TV as opposed to just dumping exising mobile apps onto our platform creates a better user experience.
.... on the other hand there are a lot of great mobile apps that naturally work well or are easily ported in a remote/tv friendly way to a TV device (ie FireTV) but will never be developed for a TV only platform (ie Roku).
"Chris Adamson@SubFurther" wrote:
Third-party Roku apps are written in BrightScript, a simple language that is based on Visual Basic. That’s going to freak a few people out, but I see the value of it to Roku:
Because then Roku might be obligated to keep up with the evolution of those languages, even if those developments are meant for domains (Rails, the DOM) that are irrelevant to Roku. Owning their own language is smart. That’s why Apple controls Objective-C, Microsoft has C#, and Google f’ing stole Java. (Be honest, they did, and you know it.) BrightScript can have exactly what Roku needs in it and nothing more.
- Why not a compiled language, like Java or some C derivative?
Apparently, Roku’s special friends get that, but if you’re just writing a content browser that throws to a player, do you need the hassle, or even the performance?
- But dude, really, Visual freakin’ Basic?
Do you know how many professional programmers started on VB? Not my cup of tea, either, but why not co-opt the talent that’s out there? Chances are, it was comfortable to the guys and girls implementing it on Roku too.