|Do people build things using little languages any more? email@example.com (Roger L Costello) (2022-07-04)|
|Re: Do people build things using little languages any more? firstname.lastname@example.org (Kaz Kylheku) (2022-07-05)|
|From:||Roger L Costello <email@example.com>|
|Date:||Mon, 4 Jul 2022 14:11:03 +0000|
|Injection-Info:||gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="29128"; mail-complaints-to="firstname.lastname@example.org"|
|Posted-Date:||04 Jul 2022 13:31:21 EDT|
I am reading the "Little Languages and Tools" book. (I can't remember who, on
this list, recommended the book, but whoever it was thank you! It is an
The first chapter was written by Jon Bentley. Incredible writer! The thing
that struck me most from reading his chapter is that writing little tools
(using little languages such as AWK, Lex, Yacc, pic (picture language),
scatter (scatter plot language), troff, sed) and then assembling them together
via pipes, e.g.,
scatter infile | pic | troff >outfile
is a powerful way to quickly get robust tools implemented.
My impression is that this style of development is no longer in vogue. Today's
developers want to use big languages like Java and Python and implement large,
To my way of thinking the old style of development is far superior.
But perhaps I am wrong. Perhaps today's developers are implementing
tools/applications using the old style. What say you? Do you use the old style
of implementing tools/applications?
Return to the
Search the comp.compilers archives again.