Re: [MiNT] WCOWORK vs WINDOM for components

[Lonny Pursell <atari@bright.net>]

on 7/23/2005 8:31 PM, Joakim Högberg wrote:

>> Well... if you had have a look at windom, then you saw that windom already
>> propose a "frame" API that answers all your needs. With the windom "frame"
>> feature, you can develop an application that open a framed window, with QED
>> in
>> one frame and HW in the other. The mechanism is already here. The "long road"
>> target you plan for xaaes is something that already exist for years thanks to
>> windom. Developpers just have to use it !
> 
> One thing to keep in mind here! Not everyone is:
> 
> a) Coding in C
> b) Using Windom
> 
> I don't doubt it is a nice feature of Windom, but Windom ain't the only
> possible route to
> take when creating applications.

I also have no interest in windom or any other lib for that matter.
If these libs have bugs, then you are importing other peoples bugs.
Agreed it might be fine for some, but definitely not for everyone.

I also don't like the assumption that because a lib is already present that
OS dev needs to be stopped or changed to suit the lib.  That is just
backwards thinking.  It needs to go into the OS so we can keep the apps lean
and clean and not huge and bulky.   Also if it's in the OS, it makes it far
more easier for any language to access the features.

An example might be the socket calls, now that they have been moved into the
kernel, they are no longer limited to gcc coders.  Prior to that it pretty
much required gcc.

-- 
Lonny Pursell    http://www.bright.net/~gfabasic/