Announcing the new Open Source IDE (you just can't code with it)!

[David Bovill]

On Thu, 2003-08-07 at 13:30, Robert Brenstein wrote:

> Since using 'do' one can relatively easily work around the 'set 
> script to' restriction (performance issues aside), we can only expect 
> further elimination of 'do' in standalones (do limit set to 0) in a 
> near future. It would be a logical followup to fully close that 
> loophole. This line of product development really scares me...

And then there are other ways of getting around the restrictions... not
to go into all of them on a public list (they are easy to figure out) -
blocking each one would require removing another feature.

> I had big and long-term plans for a number of MC-based 
> projects, but the recent developments really make me wonder whether I 
> bet on the right horse.
> 
> Robert Brenstein

Not a horse man myself. But I agree - I am committed to an open source
strategy and if the new licence restrictions prevent this being credible
I'm going to have to delete Revolution from the list of supported
languages and stop developing in it.

There is a question that just occured to me regarding the commitment to
"open source" the MC interface and Revolutions licencing restrictions...
how can you have both?

The whole idea of "open source" is that you have the freedom to examine
and use (therefore create / adapt) the code. Productivity restrictions
based around an improved IDE - OK, but inability to code full stop? Is
photoshop an "open source IDE" because you can create non-functional but
"open" interface designs with it?