On Tue, 02 Jan 2007 15:29:03 -0800, Walter Bright <newshound@digitalmars.com> wrote:

>I know you all are early adopters of D, and that's a special breed different from the vast majority of programmers. But still, it would be
>  useful (in writing documentation) to know what language was your
>primary tool before coming to D. I also know that many of you are handy with multiple diverse languages, I just want to know the primary one.
>
>Asm?
>C++?
>C?
>None (D's your first language)?
>Java?
>C#?
>Python?
>Lisp?
>Ruby?
>Delphi?
>Perl?
>Cobol? <g>

C# has been my primary language for 3 years (of pain). Hope i'll never
have to use it after Tango (or whatever the D standard library will
be) is released.

> But still, it would be useful (in writing documentation) to know whatlanguage was your primary tool before coming to D

C++

Christian

Sean Kelly wrote:
> Chris Nicholson-Sauls wrote:
>> Don Clugston wrote:
>>> Walter Bright wrote:
>>>> Chris Nicholson-Sauls wrote:
>>>>> Actually I think "Rudy" is a cute name for it.  Although it might lead to "Rudolph" jokes... so be it.  We'll just make its mascot a reindeer and be done with it.
>>>>
>>>> "Rudy" is perfect.
>>>
>>> "Rubidium" was another one that comes to mind.
>>
>> I thought of that, as it sticks with the gemstone idiom of Ruby at large (it even sounds like the words "Ruby" + "idiom", heh).. but just couldn't escape the novelty of "Rudy." Sounds like a case for a poll.
> 
> I read it as "Ruby Diem," which is kind of a nice play on words too :-)
> 
> 
> Sean

Either one is catchy, the product is more important though, i.e., *someone write the bindings*.

Max Samukha wrote:
> On Tue, 02 Jan 2007 15:29:03 -0800, Walter Bright
> <newshound@digitalmars.com> wrote:
> 
>> I know you all are early adopters of D, and that's a special breed different from the vast majority of programmers. But still, it would be  useful (in writing documentation) to know what language was your primary tool before coming to D. I also know that many of you are handy with multiple diverse languages, I just want to know the primary one.
>>
>> Asm?
>> C++?
>> C?
>> None (D's your first language)?
>> Java?
>> C#?
>> Python?
>> Lisp?
>> Ruby?
>> Delphi?
>> Perl?
>> Cobol? <g>
> 
> C# has been my primary language for 3 years (of pain). Hope i'll never
> have to use it after Tango (or whatever the D standard library will
> be) is released.

I hear that.

Walter Bright wrote:

> I know you all are early adopters of D, and that's a special breed
> different from the vast majority of programmers. But still, it would be
>   useful (in writing documentation) to know what language was your
> primary tool before coming to D. I also know that many of you are handy
> with multiple diverse languages, I just want to know the primary one.

It's fluctuating between Java and D. A couple of years back it was C/C++.

-- 
Lars Ivar Igesund
blog at http://larsivi.net
DSource & #D: larsivi

== Quote from Walter Bright (newshound@digitalmars.com)'s article
> Pablo Ripolles wrote:
> > little C but lots of Fortran 90/95 and Python, essentially for scientific computing and visualization (numerical simulation)
> I'm glad to see Fortran represented here!

C was the first language I started with, I just played a bit with it.

I must say that I am mainly into the research and development of "good" and "stable" designs for PDE solvers (Fluid Mechanics/CFD, Solid Mechanics/CSM,...). In this context performance is critical.  It's so critical that the general tendency is to let design related goals (maintainability, extendability,...) completely aside.  I am sick of the often seen, unbearable, inflexible and old fashioned "simulation codes" that sadly tend to become "legacy codes"... if ever producing some legacy I choose legacy design.

Donald Knuth once stated "Premature optimization is the root of all evil".

The classical expectation that at the lower levels (leafs) of the "calling tree" you barely need abstraction and therefore anything might be implemented (without twisting design) using elementary language constructs just fails.

In this state of mind my journey has been:

Fortran 77 -> Fortran 90/95 -> Fortran 2003? (still waiting for acceptable
implementation) -> Python (Multiparadigm, abstract enough and brilliant ascetics
but too slow) -> D (Multiparadigm, abstract enough and FAST!)

PyD becomes crucial for the _late optimizations_ of my legacy Python designs.

Why not C++? I was reluctantly about to stick my heat into it when I discovered :D

== Quote from bls (killing__Zoe@web.de)'s article
> Fortran rules, allways good to see a language without having any features
> (difficult things like recursion. ..Allways good to keep this stuff away
> from math !)
> is able to survive.

Fortran 90/95 has recursion.

C/C++

Regards,
--
Tom;

== Quote from Walter Bright (newshound@digitalmars.com)'s article
> I know you all are early adopters of D, and that's a special breed
> different from the vast majority of programmers. But still, it would be
>   useful (in writing documentation) to know what language was your
> primary tool before coming to D. I also know that many of you are handy
> with multiple diverse languages, I just want to know the primary one.
> Asm?
> C++?
> C?
> None (D's your first language)?
> Java?
> C#?
> Python?
> Lisp?
> Ruby?
> Delphi?
> Perl?
> Cobol? <g>

Walter Bright wrote:
> [...]  I also know that many of you are handy
> with multiple diverse languages, I just want to know the primary one.

Java (2003-today)

but in the pat it was:
C++ (1995-2002)
C   (1992-1994)
Turbo Pascal (1985-1991)

Ciao

Walter Bright wrote:

> I know you all are early adopters of D, and that's a special
> breed different from the vast majority of programmers. But
> still, it would be
>   useful (in writing documentation) to know what language was
>   your
> primary tool before coming to D. I also know that many of you
> are handy with multiple diverse languages, I just want to know
> the primary one.

1989 BASIC on the C64 ;-) when I got that at the age of 7

Turbo Pascal on my mother's 286 (that was about 1991 IIRC)

Oberon on the Amiga (never had an own Amiga though, I had always
to ask my frieds to use theirs)

ASM of course (x86, M68k, ARM, AVR)

C/C++ (Borland C++ and MSVC++ *yuck*)

Java - never used it seriously though. When I was seriously interested it was slow like a tombstone and nowadays I prefer for the Java-like Tasks

Perl
Python
Ruby

CLisp is a must to make your XEmacs purr.

And Lua is my language of chioce when it comes to embedd scriptability into my programs.

I have also looked into Erlang, OCaml, Clean and Haskell, but not compiled a single line of code written by me, though some software on my system is written in those.

Wolfgang Draxinger
-- 
E-Mail address works, Jabber: hexarith@jabber.org, ICQ: 134682867