Hi,
On Mar 3, 4:08 pm, John Passaniti <
john.passan...@gmail.com> wrote:
>
> I think the guy is silly and I don't understand his motivation for
> posting here.
Presumably just boredom or comparison. It's too easy to assume the
worst, and I doubt he has an axe to grind.
> But it would be a mistake to ignore him. Yes, this is a Forth
> newsgroup. But I see nothing wrong with pointing out areas of Forth
> that some consider weak and expressing that perspective. I don't
> think there is any danger of Forth turning into Ruby.
Perhaps he should write a simple subset of Ruby in Forth? I know, not
an easy task, but if he likes it so much ....
> But gosh, maybe
> some of the folks here who think Forth walks on water might be
> intrigued by the brevity and expressiveness of Ruby and other
> languages, and think how the experience of other programmers in other
> languages might help Forth evolve.
"help Forth evolve" ... ugh. I'm not one of those who wants to add
everything and the kitchen sink to a language until it's
unrecognizable. I'm not implying you are either, just saying,
sometimes it's frustrating when things change too much or too many
dialects persist. Sometimes it feels like people are raving on and on
about their favorite thing, only to completely change it in the
process. Well, then what did you like about it in the first place?? It
always reminds me of that play, "I love you, you're perfect, now
change." Just silly.
> One of the most annoying things about comp.lang.forth to me is that
> people here tend to be pretty binary in their thinking. It's like
> there is no middle ground. Ruby-guy comes in here and the knee-jerk
> reaction is to say that Ruby isn't appropriate for all problems, much
> less the problems one typically uses Forth for. Well, duh. Wouldn't
> it be more interesting to not look at other languages (like Ruby) as
> some monolithic whole and instead look at specific features it offers
> and think how they might be useful in Forth?
Such as what? OOP? Regex? Generators? Threading? Unicode?
> Wouldn't it be a great
> demonstration of the flexibility of Forth that you could take
> essential features in a high-level object-oriented language like Ruby
> and not just recreate the functionality, but the brevity and
> expressiveness?
I don't think you'll win anybody over, but sure, go ahead and try.
> I see one other value of Ruby-guy's posts. Many times when people use
> the phrase "other languages" here, they don't really mean that. Far
> more often than not, when the phrase "other languages" is used, it's a
> placeholder for C. And sure, that makes some sense historically, at
> least in the embedded systems world. But a funny thing happened in
> the past THIRTY FREAKIN' YEARS. There is much more than just C out
> there.
C is still used very widely, maybe not exclusively, but it's still in
the top three. (
http://lang-index.sourceforge.net/ ) And that may be
due to the fact that other languages (Perl, Python, Ruby, Lua) are
written in it. Or maybe because tons of legacy code exists. Or maybe
because of heavy use by GNU, BSD and other POSIX places. Or maybe due
to popular "successors" like C++ or Objective C.
But let's not pretend that C hasn't evolved either. 1978 was when K&R1
was published, 1989 was the ANSI standard, 1994 was normative
amendment (or whatever), C99 was the updated standard, and now we even
have (finalized) C11 coming our way. So yeah, that's a lot of changes,
even for "standard" C.
> And in fact, many of the languages that are in common use
> today have many of the same capabilities that Forth programmers
> value. It's very easy to point out that C isn't interactive and
> extensible.
Not directly, no, but if Linux and GForth are written in C, does the
criticism still apply?
> But Ruby and a bunch of other languages are. It's very
> easy to point out that C has no concept of compilation at run-time.
> But plenty of languages these days do.
>
> Over the years, I've gotten increasingly bored with many in the
> comp.lang.forth community who think the year is still 1980. Value the
> past, learn from it, but don't live there.
1980 ... ah, a very good year. The year of the debut of Lilith
(Modula-2 machine). Also the (in)famous 8086 had just been invented
but not widely deployed yet. And I was less than a year old too. Heh,
so I can't pretend that things haven't changed. But I'm probably one
of the worse offenders to you as I still use DOS. ;-) I'm most
conservative because I just don't understand all these new-fangled
things. Also, I refuse to believe you need a 64-bit SMP machine just
to open/read/write/close a file.
It's true, things are evolving, whether we like it or not. I don't
think Forth is dead, and I don't think ANS '94 killed it (hi, Hugh). A
new standard will probably indeed happen eventually. I'd be surprised
if threading and Unicode weren't standardized (hopefully as an
optional appendices) in the next few years as "everybody else" seems
to assume them, even C11. Times are definitely different than they
were, even compared to 2007. But if things change too fast, nobody can
keep up, and who wants that? So you have to tread lightly.