I’m not sure why java and python are at the top of the list according to github metrics. There is something about timing, momentum, and wacky CTOs. But what should we really be programming in? I’m not a fan of uncle bob even though I seem to refer to him but we are in the perfect time and place to rediscover programming languages past, present and future.
I’ve been advocating for variations of tcl. The syntax is plain and simple. Parsers have been around for a very long time and easily support limited resource systems.
However, for this article I’m more interested in the enterprise. Sure there are some businesses that would benefit from my disaster proposal and are willing to throw hardware at the performance challenges… but what language is best for the enterprise or SOHO such that the upfront cost on infrastructure and training would be offset by reliability, shelf life, disaster recovery… would it be worth it? And what would it be?
a DSL by any other name
One serious challenge is that programmers are highly opinionated. You would not be able to hire a group of programmers to implement the company’s business in the target language unless it was a career choice. But if the implementation was simple enough you could train others without the skills.
Looks like I’m coming full circle again.