[M3devel] merits/demerits of cm3ide

Jay K jay.krell at cornell.edu
Fri Mar 12 07:45:07 CET 2010


  > cm3ide 
  > more later


Being at the mercy of the rapidly changing web browsers is a very sharp double edged sword.

 


An IDE with no editor and no debugger..is not an IDE.
Maybe it is a source browser.

Maybe an IDE is not worth it.

  People are very slow to change editors.

  Debuggers are hard to write.

Probably better to try integrating with an actual IDE like VisualStudio or Eclipse.

 Or to have a decent enough language, library, build system, that the language doesn't

need such costly support. Maybe we do have such a think.

 


Hyperlinking the source is nice, but all I need is "find in files".
I can open the documentation from a file system browser, which
open it in a web browser. I should just be able to use online
documentation anyway, not local stuff.

 

 

Having the real compiler output enough information

such that writing other lanugage-aware tools, such

as hyperlinked source generation, is also good.

Too many systems have their IDE write another parser,

and no two parsers agree. However it is a tough problem,

because the compiler's job is different than a source

browser. For example, a compiler must reject incorrect

source, but a source browser should be lenient.

 


Relying on the browser is a cheap way to get a somewhat
decent somewhat portable very limited gui.
That's about it.

 


I don't think it is fixable.
It's just pretty much all wierd and wrong.

I was quite shocked the first time I used it, having

heard it described as an IDE.

 


 - Jay
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20100312/558c4fff/attachment-0002.html>


More information about the M3devel mailing list