[#20675] RCR: non-bang equivalent to []= — Tobias Reif <tobiasreif@...>

Hi,

49 messages 2001/09/01
[#20774] Re: RCR: non-bang equivalent to []= — Tobias Reif <tobiasreif@...> 2001/09/03

I wrote:

[#20778] Re: RCR: non-bang equivalent to []= — Kevin Smith <kevinbsmith@...> 2001/09/03

--- Tobias Reif <tobiasreif@pinkjuice.com> wrote:

[#20715] oreilly buch von matz - website online — markus jais <info@...>

hi

43 messages 2001/09/02
[#20717] Re: OReilly Ruby book has snail on cover — ptkwt@...1.aracnet.com (Phil Tomson) 2001/09/02

Actually, thanks for posting it here. I was trying to search OReilly's

[#20922] Re: OReilly Ruby book has snail on cover — Paul Brannan <pbrannan@...> 2001/09/05

On Mon, 3 Sep 2001, Phil Tomson wrote:

[#20768] Minor cgi.rb question — "Hal E. Fulton" <hal9000@...>

I don't have much experience with

25 messages 2001/09/03

[#20770] Calling member methods from C++ — jglueck@... (Bernhard Glk)

Some quetsions have been solved for me, but my message system does not

12 messages 2001/09/03

[#20976] destructor — Frank Sonnemans <ruby@...>

Does Ruby have a destructor as in C++?

25 messages 2001/09/07

[#21218] Ruby objects <-> XML: anyone working on this? — senderista@... (Tobin Baker)

Are there any Ruby analogs of these two Python modules (xml_pickle,

13 messages 2001/09/15

[#21296] nested require files need path internally — Bob Gustafson <bobgus@...>

Version: 1.64

29 messages 2001/09/18
[#21298] Re: nested require files need path internally — David Alan Black <dblack@...> 2001/09/18

Hello --

[#21302] Re: nested require files need path internally — Bob Gustafson <bobgus@...> 2001/09/18

On Tue, 18 Sep 2001, David Alan Black wrote:

[#21303] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/18

Hi,

[#21306] Re: nested require files need path internally — Lars Christensen <larsch@...> 2001/09/18

On Tue, 18 Sep 2001, Yukihiro Matsumoto wrote:

[#21307] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/18

Hi,

[#21331] Re: nested require files need path internally — Paul Brannan <pbrannan@...> 2001/09/18

> The big difference is C++ search done in compile time, Ruby search

[#21340] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/18

Hi,

[#21353] Re: nested require files need path internally — Paul Brannan <pbrannan@...> 2001/09/18

On Wed, 19 Sep 2001, Yukihiro Matsumoto wrote:

[#21366] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/19

Hi,

[#21368] Re: nested require files need path internally — "Julian Fitzell" <julian-ml@...4.com> 2001/09/19

On 19/09/2001 at 10:12 AM matz@ruby-lang.org wrote:

[#21376] Re: nested require files need path internally — matz@... (Yukihiro Matsumoto) 2001/09/19

Hi,

[#21406] Re: nested require files need path internally — Paul Brannan <pbrannan@...> 2001/09/19

On Wed, 19 Sep 2001, Yukihiro Matsumoto wrote:

[#21315] Suggestions for new CGI lib — anders@... (Anders Johannsen)

From the comp.lang.ruby thread "Minor cgi.rb question" (2001-09-03), I

21 messages 2001/09/18

[#21413] Ruby/objects book in style of The Little Lisper — Brian Marick <marick@...>

I fell in love with Lisp in the early 80's. Back then, I read a book called

36 messages 2001/09/19
[#21420] Re: Ruby/objects book in style of The Little Lisper — Christopher Sawtell <csawtell@...> 2001/09/20

On 20 Sep 2001 06:19:44 +0900, Brian Marick wrote:

[#21479] Re: Ruby/objects book in style of The Little Lisper — Kevin Smith <kevinbsmith@...> 2001/09/21

--- Christopher Sawtell <csawtell@paradise.net.nz> wrote:

[#21491] SV: Re: Ruby/objects book in style of The Little Lisper — "Mikkel Damsgaard" <mikkel_damsgaard@...> 2001/09/21

[#21494] Re: SV: Re: Ruby/objects book in style of The Little Lisper — Kevin Smith <kevinbsmith@...> 2001/09/21

--- Mikkel Damsgaard <mikkel_damsgaard@mailme.dk> wrote:

[#21510] Re: SV: Re: Ruby/objects book in style of The Little Lisper — Todd Gillespie <toddg@...> 2001/09/22

On Sat, 22 Sep 2001, Kevin Smith wrote:

[#21514] Re: SV: Re: Ruby/objects book in style of The Little Lisper — Kevin Smith <kevinbsmith@...> 2001/09/22

--- Todd Gillespie <toddg@mail.ma.utexas.edu> wrote:

[#21535] irb — Fabio <fabio.spelta@...>

Hello. :) I'm new here, and I have not found an archive of the previous

15 messages 2001/09/22

[#21616] opening a named pipe? — "Avdi B. Grimm" <avdi@...>

I'm having trouble reading from a named pipe in linux. basicly, I'm

12 messages 2001/09/24

[#21685] manipulating "immutable" objects such as Fixnum from within callbacks & al... — Guillaume Cottenceau <gc@...>

Hello,

15 messages 2001/09/25

[#21798] Ruby internal (guide to the source) — "Benoit Cerrina" <benoit.cerrina@...>

Hi,

22 messages 2001/09/28

[ruby-talk:21192] Re: ANNOUNCE: RIGS 0.1.0 - Ruby Interface to GNUstep

From: Laurent Julliard <Laurent.Julliard@...>
Date: 2001-09-14 08:25:18 UTC
List: ruby-talk #21192
"Avdi B.Grimm" wrote:
> 
> Anyone here want to talk about experiences programming in the
> NextStep/GNUStep/Cocoa environment? I've heard a lot of people raving about
> what a productive environment it was/is; but I've never seen any specifics or
> code samples.  I've heard that it's main strength is a terrific OO
> application framework. So, what's so wonderful about the API? How does it
> compare to other application frameworks like GNOME, KDE, or MFC?
> 
> always eager to try out something new and nifty (or old and nifty),
> 
> -Avdi Grimm

Let me tell you about my own experience.

Context: 4 months ago I knew nothing about Objective C and GNUstep. One
day I cam across the announcement of a new GNUstep release and decided
to go deeper into it.

The first thing that struck me as I was learning is that GNUstep as well
as the  Cocoa Framework from Apple are almost *exactly* identical to the
NeXTstep APIs that was defined something like 10 years ago! And a decade
is an eternity in the software industry. So I said to myself that if a
Framework (and its programming language - Objective C) came through
these 10 years untouched there must be something special about it. (As a
matter of fact I completely overlooked the NeXTstep/OpenStep/Rhapsody
saga in the 1990's. You can learn more at
http://users.bestweb.net/~tstephen/OpenStep/history/content.html)

4 months after here is what I have discovered

1) First of all, when you look at it, it is obvious that all the layers
of the Framework (the Display engine, Foundation Library and Application
Kit) were all (cleverly) designed a)from scratch and b)all at once and
they fit perfectly one with another. The entire edifice is extremelly
consistent. 

2) The Framework is written in Objective C (still is on Mac OS X). It is
a simple yet powerful OO language. It is much simpler than C++ and even
though it is a compiled language it shares many of the features found in
modern semi-compiled and interpreted OO language like Java, Ruby or
Python. Just to give you an example Objective C has some remarkable
introspection capabilities which makes it easy to bridge with Java or
Ruby (as I did in RIGS)

3) Although I'm not familiar with this aspect, I suspect that the
development tools coming with the Framework (Interface Builder and
Project Builder) are very powerful tools and I'm not sure that any other
tool on the market has reached this level of integration, ease of use
and power since then. Gorm and ProjectCenter are GNUstep equivalent
(work in progress).

4) Compared with GNOME, KDE, or MFC, the  NextStep/GNUStep/Cocoa
Framework is much, much simpler. I have been a Linux user for a decade
(since the beginning actually) and I could never convince myself to
invest enough time to master GNOME or KDE. Yet the
NextStep/GNUStep/Cocoa Framework offers all the libraries and modern
programming technics that a programmer would expect (included
distributed objects!). The learning curve is also very smooth. Reading
the 3 following documents is enough to understand and master 90% of the
Framework:

- Object-Oriented Programming and the Objective-C language (a must
read!)
http://developer.apple.com/techpubs/macosx/Cocoa/ObjectiveC/ObjC.pdf

- Foundation Library - Objective C API
http://developer.apple.com/techpubs/macosx/Cocoa/Reference/Foundation/ObjC_classic/FoundationTOC.html

- Application Kit - Objective C API
http://developer.apple.com/techpubs/macosx/Cocoa/Reference/ApplicationKit/ObjC_classic/AppKitTOC.html

5) All the Framework specifications are public and well documented (see
above)



Bottom line: the NextStep/GNUStep/Cocoa Framework is about consistency,
simplicity and a power.

Hope this helps and I also hope that this message will help establish
fruitful and sustained relationship between the GNUstep and Ruby
communities.

Laurent

In This Thread