Then where is this effort? Why is one developer wandering off on his
own? How about setting a 'win32k rewrite' as a goal for 0.4? That is,
if 0.3 ever makes it out the door...
Honestly, i think that devs should work towards the feature set we
planned for 0.3, however that is just me. Granted, there is no money
involved in this project, but not setting goals and randomly doing
rewrites is the fast way to code burnout, boredom, and lost interest.
Drowning yourself in an impossibly large project is nuts.
Richard
Alex Ionescu wrote:
yash wrote:
if you fix A, BCD will break. You will fix B,
only to see E and F
break,
if it really goes like that, you should keep rewriting the unit from
scratch, each time making a better design in respect to more and more
and more isolation and adding more and more and more abstraction
levels. you must use all your previous experience each time
redesigning the internals. also you must find ways to constantly
fuel yourself with more patience and motivation.
yash
Hi Yash,
You've nailed it. This is what win32k needs. A collaborative,
well-planned, well-designed rewrite.
Best regards,
Alex Ionescu
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.com
http://reactos.com:8080/mailman/listinfo/ros-dev