Thanks!

Press as usual likes flashy topics, so of course everyone edited the  
news text as he liked, but I like it. ReactOS needed some kick, it  
was quite sad to see some kind of stagnation (even though everyone  
did their best, it's just lack of human resources for specific tasks).

If we make arwinss (or however it's going to be branded) succeed  
quickly, it's the best ever road to switch to beta with huge apps  
support, and put resources into more interesting things like real  
hardware bringing up, file systems support, and finally, after so  
many years, actually start using our OS. It would be fantastic to  
notice "ReactOS" in general web/whatever statistics sum ups.

On Jan 19, 2010, at 10:03 PM, Gregor Schneider wrote:

>
> Now that I understand the driver concept behind arwinss I think  
> that arwinss is the right approach for the project.
> Looking at the current development approach win32 user and kernel  
> components will not be finished anytime soon and will probably  
> never work 100%. We're just missing specialised developers to  
> achieve that.
> Furthermore mixing Wine and ReactOS codes on function level like  
> done in those components complicates matters dramatically and  
> consumes energies that could be used in better ways.
>
> Summing that up: I like the idea, should indeed be a big push for  
> application compability.
> Actually I'm surprised we don't see a big controversial discussion  
> around this idea like everyone expected.
>
> Concerning the picture on page 25 of the presentation: I remember  
> having seen the start menu side bar cropped like this before in  
> some of my tests. Was it StretchDIBits, or rather StretchBlt? I'll  
> find out.
>
> Best regards,
> Gregor Schneider
>
> P.S: Quite interesting how the press judged this announcement:  
> "ReactOS about to restart" is what I read today on a german  
> technology news page.


_______________________________________________
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Reply via email to