|
|
|
|
|
by mpweiher
1661 days ago
|
|
> none of the tradeoffs of using a general purpose program language were discussed. Yep. And particularly the fundamental issue of so-called "general purpose" programming languages: They are *not*, in fact, general purpose.
What we call general purpose languages are, in fact, DSLs for the domain of algorithms. See ALGOL, the ALGOrithmic Language. But we think they are general purpose, because that's what we use, lacking other options. And this mistaken categorisation leads us to the incorrect conclusion that things that aren't handled well by these "GPLs" must therefore be handled by DSLs. Or Domain Specific Tooling.Which in turn leads to the problems described in the article, because it's all far too domain specific. The answer, IMHO, is to make languages that actually are general purpose and not just algorithm-DSLs. That can handle integration without being integration-DSLs. My stab at this is http://objective.st/ |
|