[javascript-dev] Re: Re: Re: jit.displays - supported in JS ?

Sorry. Although I agree with you in principle, and imagine that  
there's a programming language out there which does what you want,  
you are overlooking the 20-year development of MaxMSP, the need for  
backward compatibility, and the notion that we've probably considered  
most of your suggestions at various points, as well. And that it gets  
a little boring to keep reading the same email from you over and over  
again.

Mattijs: How about now?

C74: No, not yet.

Mattijs: ... How about now?

C74: No, not yet.

Mattijs: Hm... *sniff* how about now?

C74: <expletive deleted>


So, come on Mattjis, please give it a little bit of a rest. We're  
working continuously on making the absolute most bestest MaxMSP we  
can imagine, and we know that you're going to love what we've come up  
with. Nevertheless, there are a few things that Max will likely never  
be. Through-and-through consistent is probably one of them.

There are very specific technical reasons why Jitter objects are  
suitable for JS instantiation, while other objects are not. If you've  
programmed any Max or MSP objects in C, you probably already know  
what these are. The day when all Max objects share a common interface  
may come, but until that time, some things will require futzing. But  
isn't it amazing what you can do, even given all the restrictions and  
workarounds?

So, quit yer griping and get back to work! Next time you're in  
Berlin, I'll treat you to a cold beverage to celebrate everything you  
can't have today.

jb

Am 19.06.2007 um 11:42 schrieb Mattijs Kneppers:

>
> Quote: Jeremy Bernstein wrote on Mon, 18 June 2007 22:32
> ----------------------------------------------------
>> I get that. I really do.
>>
>> But that's religion, in my opinion. Max needs to be about being
>> practical sometimes. Be practical, check out how fast you solved the
>> problem, hide the patchcords. Celebrate with a cold beverage.
>>
>> jb
>>
>
> Dear Cycling '74,
>
> Wondering.. is this the moment to construct a solid, smooth but  
> urgent 4 or 5 alinea's message? Because.. what you say is not true.  
> Or shall I write a letter (on paper, in an envelope, with a stamp)  
> to the cycling office in which I explain this? Because this could  
> be quite valuable information. Or should I simply come over to San  
> Francisco and bring my laptop? Because then you would certainly be  
> convinced.
>
> Ok. I chose for the last option.
>
> But before I arrive, let me make a two-sentence summary of what I  
> am going to tell you.
>
> "When a project gets larger than 10 different subpatchers that have  
> to communicate in an intricate way, max patching becomes  
> programming. In programming, you must utilize every single method  
> to make your code more transparent."
>
> See you in SF. ;)
>
> Mattijs
> --
> SmadSteck - http://www.smadsteck.nl
> Hard- and software for interactive audiovisual sampling
> _______________________________________________
> javascript-dev mailing list
> javascript-dev at cycling74.com
> http://www.cycling74.com/mailman/listinfo/javascript-dev