Re: [SharpOS Developers] MOSA / AOT

[Bruce M. <ill...@gm...>]

Okay, before anyone starts marking their scents on the ground - (I'm
stopping you so I can get mine in there first) - my point isn't what looks
pretty or doesn't.

My point is, MOSA needs to agree on how to handle (and how much to handle)
differing paradigms. Grover, I'm glad you think you agree with me - but you
didn't actually address the blunt of my point. The point being, the MOSA
forums are almost as much of a ghost town as SharpOS is. It may be a
compiler you are writing to contribute to MOSA, but MOSA as a whole (which
in and of itself, is rather undefined), needs to have an infrastructure on
agreeing on standards by which opinions or guidance can be generated in
regards to *any* compiler, including this new one being written.

Calling it a MOSA compiler may not be accurate if it has to be branched four
ways from Sunday in order to work with each project. And maybe - maybe
*thats* exactly how "MOSA" wants to do it. But there just isn't a clear
enough definition of *what MOSA is* right now, for any of us to know how to
feel about each other's compilers. (After all, we are trying to eliminate
the "mine is bigger than yours" crap so that we can get along.)

MOSA needs a domain. MOSA needs a mailing list. MOSA needs *people*. Then, I
think, MOSA can sit down to create standards. There is so much to talk
about, that I think we need some clear, defined space to do it in, so we can
track what is going on.

When you guys first started talking about MOSA, I didn't think about code at
all. But code is an understandable extension of agreed-upon specifications.
Specifications that we need to take time, space, and conversation to figure
out. The MOSA AOT is fascinating and exciting, but conversations about it
are moot for now.