On Friday 09 July 2004 00:17, zuzu wrote:
>
> not for me.  corba, and to a much lesser extent xml-rpc, seem complex
> for complexity sake, to satisfy "enterprise level job security" or
> something.  find me a person who can implement corba themselves and
> i'll concede this argument.  even gnome only implements a subset of
> corba for their orbs.

For developers using CORBA or XML-RPC, it's pretty simple.  You have to use 
good libraries of course, not implement client/server code from scratch.

> > I think the freedom isn't the only culprit; it's the sheer length of time
> > C++ has been around, and how many programmers it attracted early on when
> > programming itself as a discipline was still a very mystic activity.
> > Nowadays, there are loads of design patterns to use as examples, so when
> > a bunch of new programmers jumps on a new language, like Ruby, it's a lot
> > easier to get them all cohesively communicating and using "approved"
> > design patterns.
>
> if you concede "approved design patterns", then i'm not sure why we're
> arguing. i happen to feel that actor / flow-based style would be a positive
> evolution in the "approved design patterns" of ruby.

I don't think we're arguing, just exchanging ideas.  Just because this is the 
Ruby ML doesn't mean every contentious exchange has to be an "argument."  =)

I haven't found much to read on Actor/Flow-Based programming.  I only saw one 
brief page on it, but I couldn't figure out how it was different from 
event-based client/server programming, which is, to say the least, some of 
trickiest programming around.

> > I actually think Ruby gives you the ability to use MORE paradigms than
> > C++ can, at least effectively.  I felt far more boxed in with C++ than
> > with Ruby.
>
> which then essentially is my argument.  by moving forward with "one
> pretty good way", more people will be able to achive more real
> productivity with less work.  aka "less is more".

I disagree; more is more.  It's good to cut away the really useless stuff that 
causes more problems than it solves, like multiple inheritance, but there are 
a heck of a lot of patterns that work, and I don't want to program in a 
language that forces me towards one pattern.

	Sean O'Dell