6 ms·
> how I don't have to worry about it fading like the next programming fad. I'm not sure I understand this bit. What other programming language has "faded" and
by oblio 9y ago
> how I don't have to worry about it fading like the next programming fad.
I'm not sure I understand this bit. What other programming language has "faded" and how has it "faded"? At least since the more mature age of software, which I'd say started around '95 or so (so 20+ years).
- vesak 9y agoPascal, perl, ASP, every ML, Fortran, Cobol, Eiffel, Modula, all "4GL" languages.
- kamaal 9y agoNone of them have faded. Cobol? Seriously, there are probably more Cobol programmers than there are Python programmers. And C? Most of the world runs on C, and its irreplaceable language in a non desktop computer. And you will be surprised how much Perl code is written everyday. The root comment is talking about the fad of the year, the kind of a language web devs use as flavor of the year. The current ones are Javascript frameworks. In this case the 'fade' is just the web framework, that probably has less mind share and open source dev contributions.
- vesak 9y agoYeah, when I wrote the comment, I kinda guessed that people would point out the zombie-like state of living for these languages. That's only barely being alive, though, and very much faded. (I did have C in there but edited it out. I don't think that's a dead language yet.)
- AnimalMuppet 9y agoBut isn't Lisp almost as zombie-like as Perl or COBOL? (4GL I'll probably give you...)
- vesak 9y agoWell, yes :) And 4GL languages are actively being used to create new business, so who knows what's dead and what's not. Perhaps the whole programming field is just a bunch of undead things. Sometimes a bunch of living things stumble upon the field, but they're soon infected...
- deleted 9y ago[deleted]
- jhomedall 9y agoThere are several implementations of Common Lisp that are still being actively developed. Because Common Lisp is so easily extended, the ossification of the standard is actually a good thing. The stability of the standard means that code written 30 years ago will still work today. Feature updates aren't required, because any desired feature can be implemented in macros and imported as a library.
- oblio 9y agoIf by ASP you mean classic Visual Basic, I'll grant you that. And Pascal. But ML, Eiffel and Modula were never mainstream. And Perl, Fortran, Cobol probably still have more programmers out there than Common Lisp has :)
- deleted 9y ago[deleted]
- pjmlp 9y agoModula-2 had a good developer community in Amiga and MS-DOS systems, at least across a few European countries.
- deepaksurti 9y agoAnd the fewer CL programmers will run circles around P, F, C programmers :-)
- jabl 9y agoSo, why don't they? ;) Why is viaweb and ITA trotted out decade after decade? If CL is so awesome why isn't the world filled with awesome stuff implemented in CL? (To be clear, IMHO it's a huge shame that more powerful languages like CL or Haskell aren't more popular)
- nickpsecurity 9y agoBecause they won't put in the effort to just pull up and post the customer lists of companies selling LISP commercially. ;) http://www.lispworks.com/success-stories/index.html http://www.lispworks.com/success-stories/index.html https://franz.com/success/ https://franz.com/success/ The companies that use LISP don't talk about it much. I'm not saying secret weapon or anything either. I'm saying they seem to be among the set that just identifies something good for the business, buys/builds it, and solves business problems. They don't write articles about their programming language. What I will say is the small number of case studies on those two companies have much more interesting software than what's advertised for many stacks. The kinds of things people use it for corroborates the LISP advocates' claim it's a favorite for hardest, constantly-changing problems. It's more remarkable with Allegro since they charge royalties on top of the licensing with customers still buying their stuff.
- pjmlp 9y agoAdding a few more to the list, Algol, PL/I, PL/S, NEWP, BLISS, Mesa, PL/8, xBASE, RPG, PL/M, NewtonScript, Modula-2+, Modula-3, Component Pascal, Oberon, Oberon-2, Active Oberon, Zonnon, StarLisp, StarC, Concurrent Pascal, Concurrent C, Forth
- segmondy 9y agoPerl, ML, Fortran, Cobol has not faded. You might not like them, you might not use them. But there are tons of them out there and being used in the real world and production systems.
- ams6110 9y agoI think it's fair to say those languages have "faded" I would also say Python 2 has "faded" or started to. Faded doesn't mean it isn't used anymore. It mean it's retreated into a niche, and is no longer on the short list for new development, and no longer interesting to most developers.
- oblio 9y agoYour average Python 2 programmers “becomes” a Python 3 programmers after 8 hours of practice. I find your argument invalid :) Also, Python 2 sees and will probably see more production use than Lisp for at least a few more years :)
- venuur 9y agoFortran is still going strong with Fortran 2008. And even better, it’s backwards compatible still with Fortran 77.
- reikonomusha 9y agoCritically, though, it's not the same Fortran. Fortran 2008 is VERY different from FORTRAN 77.
- deleted 9y ago[deleted]
- venuur 9y agoVery good point! I find the structure of modern Fortran very clear (although somewhat verbose compared to same python).
- TheRealKing 9y agocheck out the new impressive built-in parallel features in Fortran 2018 here: https://goo.gl/ZbH4t7 https://goo.gl/ZbH4t7 GFortran 8.1 has already implemented the majority of it, and Intel is already adding the new features to their new Intel Fortran 2019. I don't know of any other mainstream language at the moment, that has native shared- and distributed-memory parallelism capabilities based on one-sided communications without recourse to the complex ugly out-of-language MPI library calls.
- drmeister 9y agoI say this with a perspective of watching it happen over forty years. I'll get all kinds of heck if I start saying this or that language has faded. But many languages have changed over time, sometimes in breaking ways, as their developers work to make them more expressive and add features. Code that is written one year often doesn't work a few years later - that's a kind of fading as specific reference implementations fade away and code written in them needs to be updated or it rots. Common Lisp doesn't have this problem - and it has many features that other languages have added over time, often in less comprehensive ways. For example C++11 lambdas are not as expressive and powerful as Common Lisp first class functions, and I joke that C++ template programming is to Common Lisp macros what IRS tax forms are to poetry. Note: Clasp includes a lot of C++ template programming and C++ lambda code that I enjoyed writing and I am so grateful that C++11 added variadic templates. New language features can be added to Common Lisp by the programmer with macros, and for the really adventurous, they can be made efficient by augmenting the Common Lisp compiler. Common Lisp compilers are almost always written in Common Lisp and available and accessible. This is why Clasp uses a new and understandable Common Lisp compiler "Cleavir" (developed by Robert Strandh) and LLVM, which is a great C++ library for generating native code on a variety of processors. Cleavir will be an excellent platform for efficiently implementing new dynamic programming language features.
- oblio 9y agoThing is, except for CS theory evolving, the programming language environment from 30 years ago is in my opinion irrelevant from a maturity perspective. The number of practitioners was probably 1 million or so worldwide, now there’s probably 20-40+ million programmers worldwide. We didn’t have widespread internet access, barely a handful of Open Source communities, compilers were generally commercial and extremely expensive, companies behind technologies were extremely volatile, etc. While that made for very nice war stories, it also meant that you’d have the “ship” sinking under you completely. Now a tech still stays around to some degree. A C developer from 1990 could still be a C dev in 2018. A Java dev from 1998 could still be a C dev in 2018. And a programmer in your average mainstream language in 2018 could reasonably expect to be working in the same language in 2018. Especially if that language has enterprise traction (Cobol, Java, C#, Javascript, SQL, etc.). Also, languages are a lot more similar to each other than they used to be, in terms of expressiveness and power. Lisp was a “lightsaber” to the “stones” of the 80’s, now it’s at most a slightly more powerful “machine-gun”, at best. And regarding language evolution itself, everything evolves. Or did Common Lisp programmers generally write unit tests, have integration test harnesses, use package repos, etc. back in 1995? I somehow doubt that :)
- drmeister 9y agoOther examples... C++ template programming necessarily followed a very different style than it does since variadic template were introduced with C++11. There were books written before C++11 wherein much of them was obsoleted by variadic templates. You do not want to let students get hold of those books and think the old way was the way things have to be done. Compare how boost::python was (is? I haven't dug into it recently) written compared to pybind11 - night and day differences in readability thanks to variadic templates. That's not a dig at boost::python - it was written with the C++ they had back then and it had to use Lisp-like list comprehension with tedious replicated boilerplate code to unpack argument lists. Then there are raw pointers in C++ - we aren't supposed to use raw pointers anymore. We are supposed to use references and std::unique_ptr<x> and std::shared_ptr<y> and this thing called "move semantics". That stuff sucks for directed graphs and so I switched to compacting, tracing garbage collection for Cando. C++ is being developed in a way that it retains backward compatibility with existing code - thank goodness for that! But there are styles of programming even for something as staid and venerable as C++ that, while supported, should pass silently into the long, dark night. Then you have a language like Python that made sensible but breaking changes between versions 2.x and 3.x. Wow - look at the problems that is still causing. I love Python but I won't do anything with it that I can't rip out root and branch with more than a few weeks work. I say that even though Clasp's build system is completely implemented using the very excellent Python based build system 'waf'. Then you have Javascript - it seems to change every time I blink. That doesn't mean I will stop using it for our web based Jupyter notebook user interface. Javascript is the only game in that town. I just close my eyes and hold on tight and try not to scream. Common Lisp isn't like any of those, it grew out of a lot of very careful thinking and was specified around 1984 darn near perfect. There are some warts (logical pathnames - I'm looking at you) but even its warts are better thought out than some other languages features. Better implementations and more and better libraries come along - but the language has the same expressiveness, power and permanence it has always had.