Using D

[Paulo Pinto via Digitalmars-d]

On 25.08.2014 13:53, Russel Winder via Digitalmars-d wrote:
> On Mon, 2014-08-25 at 09:01 +0000, Chris via Digitalmars-d wrote:
> […]
>> The main thing that put me off Java was not so much the fact that
>> you're restricted to OOP and that it's verbose etc., but that it
>> caused all sorts of problems when shipping the actual programs.
>> "Write once run everywhere" is a myth, if you ask me. D is much
>> closer to that than Java. In the end we encountered so many
>> problems that I dumped Java for cross platform development (and
>> for development in general). Nobody in the Java world ever talks
>> about this, but cross platform doesn't really work (apart from
>> running simple programs).
> […]
>
> Java is not really an object-oriented programming language. OK it has
> classes, inheritance, and method calls, but it is not founded on message
> passing. For example:
>
> 	a + b
>
> is not a message in Java as it is in C++, Python, etc.

Since when does C++ does support message passing?

>
> Write Once Run Anywhere (WORA) has been a known fallacy since about
> 1995 ;-) Versions of things really are a bit of a
> dependency/configuration nightmare. Maven Central and Gradle help
> somewhat for the JVM, but then there is the shared library nightmare for
> all other platforms.
>

It is surely way better than the alternatives, specially if one 
remembers the chaos of writing portable code in C or C++ back when Java 
apperead.


On those days I was writing "portable" code across UNIX systems and 
discovering that POSIX isn't as portable as it gets sold by. The real 
fun was between the K&R C, ANSI C and pre-standard C++ support across 
compilers.

--
Paulo