Re: [ros-dev] Arwinss architecture

[Alexandru Lovin]

Hello,
I'm here to tell you about what the not-so-bright user thinks. I have been
in contact with them.

They say "well...ReactOS is Linux, right?"

Because it's open source. I don't know who, but the world as we see it glued
the idea of open-source to Linux. Any OS who is open source is somehow based
on Linux.

Of course some people know that can't be 100% true. But these people are the
users, the developers and the enthusiasts of these projects who are not
based on Linux. It doesn't matter how many newsletters you write saying it's
not Linux, or how many presentations at events you have, saying it's not
Linux but aims to be a completely compatible Windows clone.

This is a major "security hole" for ReactOS. The moment someone says
"well,
now we're based on Wine until we can finish a proper implementation of our
cloned-after-Windows subsystems," that's when these users will say "well,
that's still Linux so I'll take Vista/XP/whatever Windows version, thank you
very much." They know what Wine is (although many think it's an emulator)
and they know that's Linux. No one can change their minds.

Meanwhile, this change sounds very helpful and useful. But this is probably
why some developers are so against it.

Yes, maybe James Tabor is right - Download ReactOS Wine-based, Download
ReactOS Windows-based (but if you write that, everyone will jump and say you
copied Windows code after looking at the leaked sources). Release and Debug
for each.

I'm sorry about this, but it's the way the users were fooled. And these
people were Ubuntu users, very happy about it. One of them pointed out that
*gasp* YOU HAVE MORE DESKTOPS, JUST LIKE IN LINUX!!! He was, of course,
talking about the taskbar, where you can select which desktop you want to
use.

So, whatever the decision, BE CAREFUL!!!

2009/7/29 Javier Agustìn Fernàndez Arroyo <elhoir(a)gmail.com>

>   Personally i like the idea of being able to access
> remotely using an X
>  Server.. Could this feature be ported to current Win32k implementation after
>  Arwinss is deprecated?
>
>
>  On Wed, Jul 29, 2009 at 8:42 PM, King InuYasha <ngompa13(a)gmail.com> wrote:
>
> >   Makes sense. And once the real subsystems are
> > compatible and stable
> >  enough, then the arwinss branch could be relegated to an addon. An addon
> >  that could be used on both ReactOS and Windows. It's a stopgap solution, but
> >  one that would have uses after it is replaced.
> >
> >
> >  On Wed, Jul 29, 2009 at 1:10 PM, Ged <gedmurphy(a)gmail.com> wrote:
> >
> > >   Current win32 subsystem progress is too slow. We
> > > need something now
> > >  before
> > >  it's too late.
> > >  One of the main things that's holing us back and stopping new devs from
> > >  getting involved is out lack of compatibility and stability.
> > >
> > >  If we have a drop in replacement which is much more compatible and stable
> > >  then the current one, then I think it's wise to use that whilst the real
> > >  implementation is continued alongside.
> > >
> > >  Surely this will give you the freedom to get architecture done without
> > >  worrying about breaking things?
> > >
> > >  Ged.
> > >
> > >  -----Original Message-----
> > >  From: James Tabor [mailto:[e-mail]]
> > >  Sent: 29 July 2009 18:30
> > >  To: ReactOS Development List
> > >  Subject: Re: [ros-dev] Arwinss architecture
> > >
> > >   No, not even, not in the light of day, shall this ever be part of
> > >  trunk!
> > >
> > >  Separate project maybe, perhaps or will be a new project altogether!
> > >
> > >  Leave our trunk alone and keep working on ArWinSS where it is or make
> > >  it's own home on ReactOS.org.
> > >
> > >  I'm @ wk and had to comment on this,
> > >  James
> > >
> > >  On Wed, Jul 29, 2009 at 6:38 AM, Ged<gedmurphy(a)gmail.com> wrote:
> > > >   What people should also know is that if this
> > > > branch ever does make it 
> > >  into
> > > >   trunk it will only be used as a temporary
> > > > solution until the correct
> > > >  implementation is ready. This is by no means a permanent solution!
> > > >
> > > >  What it will do is act as a temp replacement which will hold things 
> > >  together
> > > >   and allow work on the real subsystem to
> > > > accelerate.
> > > >
> > > >
> > > >
> > > >  At the moment the current subsystem must be kept stable as it's our 
> > >  main
> > > >   component and needs to stay regression free
> > > > whilst rewriting major 
> > >  parts
> > >  to
> > > >   make it more compatible. Not an easy task!
> > > >
> > > >  If the Arwinss model can take over for a while it will gives the win32
> > > >  subsystem developers breathing space to rewrite / hack / break / fight 
> > >  /
> > > >   kill / molest and eventually improve the real
> > > > implementation without
> > > >  worrying about breaking reactos for everyone else.
> > > >
> > > >
> > > >
> > > >  In the long run this may be a great solution to improve the 
> > >  compatibility
> > > >   and stability of the real reactos win32
> > > > subsystem.
> > > >
> > > >
> > > >
> > > >  Ged.
> > > >
> > > >
> > > >  
> > >  _______________________________________________
> > >  Ros-dev mailing list
> > >  Ros-dev(a)reactos.org
> > >  http://www.reactos.org/mailman/listinfo/ros-dev
> > >
> > >
> > >  _______________________________________________
> > >  Ros-dev mailing list
> > >  Ros-dev(a)reactos.org
> > >  http://www.reactos.org/mailman/listinfo/ros-dev
> > >  
> >
> >  _______________________________________________
> >  Ros-dev mailing list
> >  Ros-dev(a)reactos.org
> >  http://www.reactos.org/mailman/listinfo/ros-dev
> >  
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.org
>  http://www.reactos.org/mailman/listinfo/ros-dev
>  


-- 
Alex Lovin - www.erasereality.3x.ro