ayende, is it wise to yet add another tool to _the stack_ ? i mean for
beginners it is hard to manage the stack setup (castle, nhibernate,
nhlinq, nhcontrib, fluentnhibernate, rhinotools, to name a few). if
they are now confronted with some more tools (git, maybe rake, or
maybe psake) i will understand, if this guys say to them self. "well,
i need to do a couple of "hard" things and spend maybe some days just
to get started, why not just fire up vs and setup a new application
with entity framework etc."

i think this is a major problem for this excellent oss products, that
developers need to take a big step before they even can start to use
this products.



On 31 Aug., 16:39, Ayende Rahien <[email protected]> wrote:
> Yes, and yes.I was in Sweden for a set of workshops, but I intend to work on
> those today.
> I am still testing the git thingie, no decision yet, although so far I like
> it.
>
> On Mon, Aug 31, 2009 at 2:50 PM, Jason Meckley <[email protected]>wrote:
>
>
>
>
>
> > Oren, after reading your posts on:
> >http://ayende.com/Blog/archive/2009/08/30/the-complexity-of-unity.aspx
> >http://ayende.com/Blog/archive/2009/08/30/on-psake.aspx
>
> > and then the post about memory leaks
> >http://ayende.com/Blog/archive/2009/08/31/how-i-found-a-memory-leak.aspx
>
> > Can we assume that the next released/published/updated version of
> > Rhino will come after the restructuring and new deployment scripts are
> > completed? Sounds like the source/binaries will be available on git-
> > hub instead of svn/sourcesafe too.
>
> > Looking forward to the restructuring.- Zitierten Text ausblenden -
>
> - Zitierten Text anzeigen -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Rhino Tools Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rhino-tools-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to