[OSC_dev] OSC for VBscript and JScript

[Daniel Holth]

Jamie Bullock wrote:
> On 10 Feb 2009, at 16:14, Jeff Glatt wrote:
>   
>>> Do we need another one?
>>>       
>> I don't know who "we" is, but for myself, I'm definitely up for
>> choices that do things in a truly different way. First of all,  
>> EasyOSC,
>> while originally very loosely based upon SimpleOSC, is actually a
>> very different API with different real-time performance and notably
>> different methodology to using its API. If it were just mostly the
>> same thing with a couple tweaks (like the majority of Linux distros),
>> then it would be a waste of time. Furthermore, what I'd be doing is
>> a Python extension library. I've yet to come across one of those for
>> OSC. So it would not be "another one". It would be the "first one".
>>     
>
> I guess my question is, what problem are you trying to solve that  
> isn't already addressed by the two existing implementations (pyliblo  
> and simpleOSC)?
>
> I'm just curious...
>
> Jamie
No need to spoil the fun. The beauty of OSC is that even if you don't 
decide to re-use an existing library, it's so simple that you won't 
waste a lot of time making your own. In fact, with all the existing 
libraries' emphasis on "Simple" and "Easy" OSC, I think there is a 
definite gap in the market for HardOSC, the OSC library that puts hair 
on your chest!

I won't be implementing it though because I don't personally have a use 
for it, so I would not have a chance to refine its API by eating my own 
dog food.

By the way, most of the packages in pypi are pure Python and don't 
contain any C code.

My 2c,

Daniel Holth