I'm not playing dumb. I do actual work. I produce programs
that people use. I live in the real world.
You still seem, to me, to be avoiding giving substantive answers, hence I ask if
you are playing dumb or you truly cannot see that a from-the-ground-up
development of a new language targeting a big chunk of the space in which C++ is
now used, can be easily had. When I posed that to you, you went on your spiel
about "all the expressivity of C++", which is a non-substantive response IMO.
As I sais above, I actually work at programming, producing
programs that people use.
But the design of a programming language is outside of your thinking ability?
Nothing wrong with that--not everyone is cut out to do that kind of thing.
Perhaps you are more of a programmer which works under the direction of others
who tell you what to program, how to program it and what language to use?
Imaginary languages which haven't (or
even can't) be implemented don't interest me.
To each there own, of course, but that is what I do (save for your attempted
slam using 'imaginary' and 'can't be implemented).
Especially when
the only definition of them is "better than X".
That's easy to say when the language being compared-to is C++, because it's
warts have been so heavily discussed for so long. But I think your track is that
anything that deviates from anything other than C++ simply cannot be better. Now
THAT is, to me, simply not worth discussing--I think they call that "fanboyism".
The bottom of things is that I have to produce a working program
by the end of next month.
It's not my problem. Good luck with that.
The bottom of things it that I have actual experience in doing
so, and that I've heard a lot of promesses, but that unless I
can see the results, they're just hot air.
What promises are those?
I understand that you are a programmer and have a job to do. I, OTOH, I don't
care to develop the software I want to develop program until I have a language
worthwhile to program with (if something is worth doing, it's worth doing right,
IMO), and since there is not one of those available, I'm developing one. I think
it is noteworthy that I didn't start out developing a language--the need for a
language comes from software I plan on developing with the language.
Where are the specifications of this language?
I have enough of them to have decided that it is worthwhile to develop that
language, and that's exactly what I'm doing, and it's getting easier all the
time as my language implementation skills mount.
Where is the
concrete user experience, to prove that it is easy to use?
Why do you keep harping about "existing languages" when I've said a zillion
times already that I'm in the process of implementing one from scratch?
That might be a good idea. Walter did it with D, and while I
don't think it's better than C++, there are some good ideas in
it.
I think there probably are, and certainly I know some of those things, but none
come to my mind at the moment that are remarkable. I do keep notes about it
though (as well as other languages).
And above all, I _can_ compare it, because I can use both,
and see the results.
To me, C++ and D are characteristically the same, save for the fact that D seems
to me to be "not ready for prime time". It probably needs a committee process to
robusticize it but that seems unfathomably difficult (to me). So, C++ "wins"
easily in my book when the two are compared.
[...]
C++ is superior
for large, stable applications which need to be maintained over
time.
Superior to inferior existing languages,
It's hard to compare it with something that doesn't exist.
Apparently for you it is. For me it is not.
OK. Since you obviously want to play the idiot, and not
understand politely worded English: it's impossible to compare
C++ (or Java, or C# or D) with a language which doesn't exist.
For me it's ridiculously easy, because I have a lot of the language design
solidly known and can do that comparison. But that isn't even required--one can
(apparently you can't or refuse to or feign that "it is impossible", etc.) take
a moment (or 10 years!) and compare, contrast, evaluate language features and
analyze combinations of them, etc. So, I really don't understand your seeming
lack of ability to do so. Are you ever in a role where you get to design what
you are assigned to program? Surely you've created a program from scratch at one
time or another, yes? What if your next gig was to develop a programming
language in which large scale projects could be developed at significant savings
compared to doing them with C++? To me, it seems like you'd balk "impossible,
can't be done, so I'm not even going to try". And you may be saying, when you
balk that, that YOU can't do that, but that hardly means that someone else also
can't. Hmm?
Because to compare, you have to actually develop programs in
each, and when it comes to developing programs, inexistance is a
killer defect.
Well, if you want to persist in taking a stance as "an evaluator of programming
languages" or "programmer", OK. You can't drive home a 2014 Corvette today
either, but next year you will be able to. Same thing. Engineering takes time.
Everything you keep on saying, and I KNOW you must know this stuff, makes me
question if you are "playing dumb" or are truly incapable of grasping the
(simple) concepts.
So now we have to invent adages, rather than present real
arguments.
It's a standard answer when someone throws out "experience" rather than
substance. Let's "call a spade a spade": you can't develop a programming
language "better" than C++, and apparently can't even conceive of such, while
some others, including myself, find that very non-taxing (save for the amount of
time and effort required). Who knows, you truly may be so into C++ that you
simply cannot step out from it long enough to even ENTERTAIN the thought of
there ever being something else. That's my take on it upon observation thus far.
COBOL was _not_ invented by people working ins someone else's
company. Nor was Pascal, nor Prolog, nor Lisp, for that matter.
It turns out that, globally, working in someone else's company
(and having concrete users) seems to be an advantage.
That was an aside--I should have left out that info.