Java's development cycle

[Walter Bright]

dsimcha wrote:
> Most programs have some subproblems that are pretty run-of-the-mill and should
> just be solved in the most expedient way possible, and others that require more
> thought, either to make them generic enough or fast enough.  Mixing languages in
> one project is generally a pain, especially if you want to do so on a fine-grained
> level.  Therefore, the thing D gets right that few if any other languages do is
> that it has a "keep it simple, stupid" layer for the run-of-the-mill subproblems
> and a ridiculously complex but powerful boot-with-a-gun-built-in layer for the
> more challenging ones, *in one language*.  The simple layer includes builtin
> arrays, builtin associative arrays, garbage collection, the ~= operator, good
> string handling, and a reasonably powerful standard lib, at least if you're using
> either Tango or the D2 version of Phobos.  The complex layer includes templates,
> manual memory management, unions, casting, operator overloading, and inline assembler.

I probably shouldn't admit it, but one of my inspirations for the kiss 
subproblem was BASIC. Nobody did the keep simple programs simple better 
than BASIC. The string handling in BASIC in particular - strings are 
just an endless misery in C.