Should we start a common HAL design?
Would it be possible/desired to implement ABI compatible HAL?


William Lahti wrote:
> I think we need to put down our grenades-- I understand the need to
> express the frustration as I have on occasion as well (and furiously),
> but hopefully soon we can give up on the grenade lobbing and forgive
> any issues we've had in the past, not only for our own peace of mind
> but for the good of the idea (as opposed to the "tribal pride" model).
>
> As I've said, license issues *do* block us from sharing code
> specifically but code isn't the only thing that can be shared. Even if
> we never come to a point where we resolve our differences, we do need
> to come to a point where we can peacefully coexist, without tension
> between our project developers. This first phase of flaming was
> unavoidable given the circumstances.
>
> As Chad said, driver cross polination is very good example, and since
> drivers in SharpOS will be separated by a well-defined ABI, they can
> be classified as a separate work from our kernel, and thus be licensed
> in a different way. If we wanted to, we could collaborate on driver
> APIs, something which has never been covered by either the ECMA
> standards nor any non-standard .NET functionality which exists. But if
> we completely do nothing, like Bruce said, we will be duplicating a
> large amount of effort. And we still haven't really looked at our
> (possibly differing) driver visions and consolidated them and it's
> possible that such a solution is not practical, but things like this
> need to be talked about and now is a better time than ever to do it.
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers

Reply via email to