Nevermind

[Rick Langschultz]

Since I heard of reactos, i have always considered it one day  
replacing my Windows 2000 and XP boxes. Because ReactOS was going to  
be an open-source alternative to the Windows NT API I felt that it  
had and has serious potential to hinder or greatly replace Microsoft  
Windows. I have suggested several ideas both through IRC (freenode)  
and email messages how the computing world does things. I understand  
that ReactOS is still in pre-production, and planning for the next  
release is greatly important to the community development and testing  
of the operating system, however I fail to grasp the concept behind  
the hindrance of ideas being passed the the development community.  
Some development plans I have talked about were:
     1 - A 64 bit journaling file system with a SQL-like back-end.
          Lookout WinFS; there that plan went down the drain.
     2 - Implementing an instant messenger server for developers and  
users to talk on, realtime, without IRC.
          Maybe not quite MSN Messenger, but why not? iChat even  
uses .mac.
     3 - Implementing an OpenLDAP back-end to the website.
         Active Directory has nothing on you... Plan knocked out again.

i would rather stick with something close minded like closed source  
software than having no ideas be recognized at all.
I only suggest things like this because Microsoft will always be  
releasing newer software that will leave reactos in the dust if they  
not heed the advice of all, not just me, their developers, testers,  
and users.

Why not; right? why envision something and it fail to be realized,  
waste of time if i ever knew it...

Rick Langschultz
rlangschultz(a)cox.net (Home)
rlangschultz(a)ellemaespa.com (Work)
rlangschultz(a)email.uophx.edu (School)

[Ge van Geldorp]

>   From: Rick Langschultz
>  
>       2 - Implementing an instant messenger server for 
>  developers and users to talk on, realtime, without IRC.
>            Maybe not quite MSN Messenger, but why not? iChat 
>  even uses .mac. 
Why reinvent the wheel? I'd say IRC works pretty well for us. We've got
enough stuff to implement already.

>        3 - Implementing an OpenLDAP back-end to the
> website.
>           Active Directory has nothing on you... Plan knocked 
>  out again. 
Personally I liked the idea (and I still do). It isn't implemented at this
point 'cause there was already a prototype for the new site that didn't
include it. That doesn't mean it is never going to be implemented.
However, using OpenLDAP for the website doesn't have much to do with ReactOS
/ Active Directory, the website is running on a Linux machine.

Ge van Geldorp.

[Brandon Turner]

Lack of developers being able to work on ROS full time is pretty much 
the main cause.  These ideas are great, and one day I would hope to have 
them developed.  But we lack man power to do such things.  I am a full 
time student and work 20 hours a week for my university.  I know most 
others also have very busy lives.  The best part about open source is 
that anyone can work on it.  So if you have the motivation that you 
expect us to have please feel free to start develpoment on any of these 
ideas and let us know how far along you get.  Thanks!

Brandon

Rick Langschultz wrote:

>   Since I heard of reactos, i have always considered it
> one day  
>  replacing my Windows 2000 and XP boxes. Because ReactOS was going to  
>  be an open-source alternative to the Windows NT API I felt that it  
>  had and has serious potential to hinder or greatly replace Microsoft  
>  Windows. I have suggested several ideas both through IRC (freenode)  
>  and email messages how the computing world does things. I understand  
>  that ReactOS is still in pre-production, and planning for the next  
>  release is greatly important to the community development and testing  
>  of the operating system, *however I fail to grasp the concept behind  
>  the hindrance of ideas being passed the the development community*.  
>  Some development plans I have talked about were:
>      1 - A 64 bit journaling file system with a SQL-like back-end.
>           Lookout WinFS; there that plan went down the drain.
>      2 - Implementing an instant messenger server for developers and  
>  users to talk on, realtime, without IRC.
>           Maybe not quite MSN Messenger, but why not? iChat even  uses 
>  .mac.
>      3 - Implementing an OpenLDAP back-end to the website.
>          Active Directory has nothing on you... Plan knocked out again.
>
>  i would rather stick with something close minded like closed source  
>  software than having no ideas be recognized at all.
>  I only suggest things like this because Microsoft will always be  
>  releasing newer software that will leave reactos in the dust if they  
>  not heed the advice of all, not just me, their developers, testers,  
>  and users.
>
>  Why not; right? why envision something and it fail to be realized,  
>  waste of time if i ever knew it...
>
>  Rick Langschultz
>  rlangschultz(a)cox.net (Home)
>  rlangschultz(a)ellemaespa.com (Work)
>  rlangschultz(a)email.uophx.edu (School)
>
>
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>
>

[Casper Hornstrup]

>   -----Original Message-----
>  From: ros-dev-bounces(a)reactos.com [mailto:[e-mail]] On Behalf Of Rick
>  Langschultz
>  Sent: 29. august 2005 15:25
>  To: ReactOS Development List
>  Subject: [ros-dev] Nevermind
>  
>  Since I heard of reactos, i have always considered it one day
>  replacing my Windows 2000 and XP boxes. Because ReactOS was going to
>  be an open-source alternative to the Windows NT API I felt that it
>  had and has serious potential to hinder or greatly replace Microsoft
>  Windows. I have suggested several ideas both through IRC (freenode)
>  and email messages how the computing world does things. I understand
>  that ReactOS is still in pre-production, and planning for the next
>  release is greatly important to the community development and testing
>  of the operating system, however I fail to grasp the concept behind
>  the hindrance of ideas being passed the the development community. 
Which hindrance?

>   Some development plans I have talked about were:
>       1 - A 64 bit journaling file system with a SQL-like back-end.
>            Lookout WinFS; there that plan went down the drain.
>       2 - Implementing an instant messenger server for developers and
>  users to talk on, realtime, without IRC.
>            Maybe not quite MSN Messenger, but why not? iChat even
>  uses .mac.
>       3 - Implementing an OpenLDAP back-end to the website.
>           Active Directory has nothing on you... Plan knocked out again.
>  
>  i would rather stick with something close minded like closed source
>  software than having no ideas be recognized at all.
>  I only suggest things like this because Microsoft will always be
>  releasing newer software that will leave reactos in the dust if they
>  not heed the advice of all, not just me, their developers, testers,
>  and users.
>  
>  Why not; right? why envision something and it fail to be realized,
>  waste of time if i ever knew it... 
Most of the suggestions you make requires several man-years of work to be
implemented. If you want to make any of them happen, you need to do more
than describing them on a mailing list. First of all, you should prioritize
them after level of importance. How important is a WinFS like service when
there are no applications written to use it? Which problems would your
instant messenger server solve that couldn't be solved with existing
technologies? What problems would using OpenLDAP on the website solve?
Then when you have prioritized your ideas, pick the one at the top of the
list and do whatever is needed to implement it. There are several way to
do this:
1) Implement it yourself
2) Convince other developers to implement it
3) Pay other developers to implement it

What they all have in common is that you take the initiative to make it
happen.

Casper

[Michael B. Trausch]

Rick Langschultz wrote:
>   
>  Why not; right? why envision something and it fail to be realized, 
>  waste of time if i ever knew it...
>   
Well, I can tell you one thing, I wouldn't want a person with that
attitude even hanging around one of my projects.

The thing barely works at the moment.  Look at the ideas that you're
pushing and tell me how you think they would be implemented in the
source tree that they are working on right this moment.  The system is
in very heavy, active development.  What does this mean?  They need it
to work... and they need it to work right.  Features are great and all,
but if the basic system isn't there, why implement the features?  Pointless.

The second thing is this:  If you want it so badly, pick up a couple of
books, a good copy of the GNU Compiler Collection and appropriate
libraries, and get to work!  Open Source is great because when someone
wants a feature, they can implement it... they don't have to coerce
others to implement a feature or a bug fix like you do when you're
working with Microsoft Windows.  Think with your head, man.

I'm sure that they will work on performance related things and toys,
when the things *work*.  They're putting a lot of work into the system;
I know that the activity on the project has picked up a lot from what it
used to be about a year ago... the developers are working hard as they
can to try to make things really happen with this project.  And if I had
the time and the know-how, I'd be doing something, myself, other then
watching it run past me in my inbox.

Hopefully, if I ever get time to get the know-how to work on it, they'll
still need help ;-).

But the point is, don't complain, because if you don't want to implement
it yourself, then you don't want it badly enough.  This project isn't
about world domination (well, maybe it is, but it's free software, so,
I'll make the assumption that it's not).  It gives people a choice.  It
gives people a great resume piece, too.  When this system becomes the
little guy that tromped over the big bad fugly creature, the people that
are working on this project will have something that I probably won't
get -- a great chance at a great life with lots of vacation time and the
like, because these people will be in demand on the job market.

>  From a technical perspective, it would be stupid to
> implement such 
things right now, anyway.  It is harder to pinpoint a bug if
you're
working with two highly unstable things verses one.  React has a lot of
components in it that aren't tested well enough yet, and probably have
bugs.  It'd be better to hit a stable version and then add new features
to it like what you're suggesting.  It'd reduce the amount of time
required to implement said features, as well, becuase you wouldn't have
to go on as much or as long of a wild goose chase to find it.

So, then, all that having been said, go on, see ya later.  :-)

	- Mike

[TwoTailedFox]

Don't run before you can walk.

On 8/29/05, Michael B. Trausch <fd0man(a)gmail.com> wrote:
>   Rick Langschultz wrote:
> >  
> >  Why not; right? why envision something and it fail to be realized,
> >  waste of time if i ever knew it...
> >  
>  
>  Well, I can tell you one thing, I wouldn't want a person with that
>  attitude even hanging around one of my projects.
>  
>  The thing barely works at the moment.  Look at the ideas that you're
>  pushing and tell me how you think they would be implemented in the
>  source tree that they are working on right this moment.  The system is
>  in very heavy, active development.  What does this mean?  They need it
>  to work... and they need it to work right.  Features are great and all,
>  but if the basic system isn't there, why implement the features?  Pointless.
>  
>  The second thing is this:  If you want it so badly, pick up a couple of
>  books, a good copy of the GNU Compiler Collection and appropriate
>  libraries, and get to work!  Open Source is great because when someone
>  wants a feature, they can implement it... they don't have to coerce
>  others to implement a feature or a bug fix like you do when you're
>  working with Microsoft Windows.  Think with your head, man.
>  
>  I'm sure that they will work on performance related things and toys,
>  when the things *work*.  They're putting a lot of work into the system;
>  I know that the activity on the project has picked up a lot from what it
>  used to be about a year ago... the developers are working hard as they
>  can to try to make things really happen with this project.  And if I had
>  the time and the know-how, I'd be doing something, myself, other then
>  watching it run past me in my inbox.
>  
>  Hopefully, if I ever get time to get the know-how to work on it, they'll
>  still need help ;-).
>  
>  But the point is, don't complain, because if you don't want to implement
>  it yourself, then you don't want it badly enough.  This project isn't
>  about world domination (well, maybe it is, but it's free software, so,
>  I'll make the assumption that it's not).  It gives people a choice.  It
>  gives people a great resume piece, too.  When this system becomes the
>  little guy that tromped over the big bad fugly creature, the people that
>  are working on this project will have something that I probably won't
>  get -- a great chance at a great life with lots of vacation time and the
>  like, because these people will be in demand on the job market.
>  
> >  From a technical perspective, it would be stupid
> > to implement such 
>  things right now, anyway.  It is harder to pinpoint a bug if
> you're
>  working with two highly unstable things verses one.  React has a lot of
>  components in it that aren't tested well enough yet, and probably have
>  bugs.  It'd be better to hit a stable version and then add new features
>  to it like what you're suggesting.  It'd reduce the amount of time
>  required to implement said features, as well, becuase you wouldn't have
>  to go on as much or as long of a wild goose chase to find it.
>  
>  So, then, all that having been said, go on, see ya later.  :-)
>  
>          - Mike
>  
>  
>  _______________________________________________
>  Ros-dev mailing list
>  Ros-dev(a)reactos.com
>  http://reactos.com:8080/mailman/listinfo/ros-dev
>  
>  
>   

-- 
"I had a handle on life, but then it broke"