1. 14
  1.  

  2. 3

    while I dig Forth and the sentiment here rings true philosophically, I would point to other long-lived languages such as perl as an example of a how it is possible to have portable code without the iron grip of a corporate dictator (granting, of course, that a benevolent overlord maintainer brings interestingly different quirks such as rigidity and slow pace of development).

    1. 2

      I wonder what’s been the driver in a rise in interest in forth stuff lately? (Or if that’s confirmation bias on my part)

      Also, I do see forth being around longer than Java, but only on the same token that we’ll also see some form of LISP be around longer: Forths are a language family with a very low barrier to implementation, perhaps the lowest of any programming language I’ve seen yet. LISPs are also still around for similar reasons. Both languages have such a small core that extending them is easy. (Sometimes too easy to build good network effects).

      But if we were to look at programming language families, just as the 21XX will have it’s version of Forth and Lisp, it will also have it’s version of Java, whether that’s Java, Go, Pascal or some other language that aims at the middle of programming instead of at the extremes.

      We will also likely never see the end of Fortran and Cobol.

      1. 1

        I wonder what the minimum viable set of extensions on Forth would be required to make it more palatable for C or ASM programmers than it currently is? Would such a thing still be forth?