16 ms·
Ten influential programming languages (2020)
- 082349872349872 4y ago> That’s one reason I love studying history. To learn what we’ve lost and find it again.
- theCrowing 4y agoPascal gives me flashbacks to the 90s in Germany every Prof was into it.
- WaitWaitWha 4y agoI think Pascal's sun set because Borland killed it with Delphi. In my opinion, Borland was the 300lbs gorilla in the Pascal compiler arena, so when Borland decided to move push Delphi over Pascal, there was no interest in filling the Pascal hole. btw I wrote commercial products on Pascal that I thought was neat. A chat program that used IPX/SPX, a a fax server using DesqView, and MS Mail queues both inbound and outbound, reverse delta databases that stored all changes at field level, overcame the 640K memory barrier by using a TSR that swapped the data in/out on demand, and a proto-PXE server using my insanely fast copy program over IPX. That was the good old times.
- FpUser 4y agoI still use Delphi for my Windows desktop product and Lazarus for Linux desktop software
- justsomehnguy 4y agoI have a very fond memories of Delphi, but if I need something custom nowadays (think utils, not something SAP-like) I just write it in PowerShell.
- fm2606 4y agoPascal was the introductory computer language at my college in 1988. I don't remember much of it.
- alwillis 4y ago> Pascal was the introductory computer language at my college in 1988. I don't remember much of it. I took Pascal as a college freshman in 1982. And even though I haven't programmed in it seriously since then, it stuck with me. It didn't hurt that it was a minimal language designed for teaching computer science. For example, when I learned Pascal, there was no string type; you had to create an array of characters. I was checking out the Free Pascal website recently; although the language has been greatly expanded, Free Pascal source code still made sense to me.
- Jtsummers 4y agoPrior discussions: https://news.ycombinator.com/item?id=22690229 https://news.ycombinator.com/item?id=22690229 (289 comments; March 26, 2020) https://news.ycombinator.com/item?id=24602741 https://news.ycombinator.com/item?id=24602741 (13 comments; Sept 26, 2020) Some other submissions but with 0 or 1 comment.
- sys42590 4y agoLearning Standard ML made me a better programmer (back in the day)... It was all about specifying how input and results are related instead of giving instructions to the CPU on what to do.
- softwaredoug 4y agoDidn’t Pascal die due to some combination of C and Javas popularity and Borland team getting poached by Microsoft in the late 90s?
- analog31 4y agoWhen I was first exposed to C (perhaps in Byte Magazine), I was dead certain that Pascal would win out. I wonder if the minor optimizations achieved by programming closer to bare iron on early computers led to a minor performance advantage that outweighed the need for readable / maintainable code.
- nrdvana 4y agoC did compile to more efficient code than Pascal, but The Delphi compiler processed code 10x faster than the C compiler, and hit an amazing sweet spot for the 300Mhz workstations of the day, where you could iterate through edit/compile/run in Delphi just as fast as Visual Basic, and when you were done the program ran an order of magnitude faster than VB (and maybe 90% as fast as C). Also, because the language was easier to parse, the tooling was able to interact with your code way better than Borland's same product for C++ or any of Microsoft's products, so you were getting more accurate code completion and context-sensitive help and all that. I believe that Delphi was a vastly superior product to any of its contemporaries, and was killed purely by corporate forces.
- indymike 4y agoC and Pascal were both fast, but C allowed programmers to dynamically allocate and free memory without having to deal with 255 character limits and other limitations imposed by Pascal. It also allowed us to create some magnificent bugs, too.
- justsomehnguy 4y agoDepends on what is your opinion about Delphi and Embarcadero
- TigeriusKirk 4y agoMy sense was Delphi was replaced more by Visual Basic, though it's entirely possible that's based on my personal experience and didn't represent a larger trend.
- silisili 4y agoThe BASIC cause of death is written that it was seen as a lesser, kids language. That sentiment may be true to some extent, but fails to mention all of the problems of the BASIC language that made people look into alternatives, none of which were snobbiness. If that were a real reason, Python would have suffered a similar fate.
- forinti 4y agoBASIC was very practical for 8 bit machines. You didn't even need an editor, because you could just retype a line. It was also very straightforward for a complete novice (as most people were with those machines). In any another environment, it really doesn't make sense.
- alwillis 4y agoTrue. One feature that was missed about BASIC on those early computers: you’d turn on the Apple ][ and you were greeted by the BASIC prompt and you could just start typing your program. This was before floppy disks… you could load a program from cassette tape.
- timbit42 4y agoIn Atari BASIC and Commodore BASIC, you didn't even need to retype a line. You could cursor up and edit it right on the screen. This saved a ton of typing.
- analog31 4y agoBASIC illustrates the "one-screen problem," where a program becomes unreadable when it exceeds one screen, or perhaps one printed page. The one-screen problem is how I explain to beginners the value of things like subroutines with named arguments, local variables, and the like. Languages that survive, have to work for the size of programs that people want or need to write.
- deleted 4y ago[deleted]
- 4y ago
- ad404b8a372f2b9 4y agoOn that topic, there is a very good (and funny) talk by Bret Victor called "The Future of Programming" presented as if it were 1973. It gives an interesting tour of dead languages and the things we lost. https://www.youtube.com/watch?v=8pTEmbeENF4 https://www.youtube.com/watch?v=8pTEmbeENF4
- bepvte 4y agoThis is one of the best talks I've seen, do you have any other recommendations?
- mlajtos 4y agoStop Writing Dead Programs
- sakesun 4y ago+1 This talk explain me why I feel better with languages with more dynamic features.
- ad404b8a372f2b9 4y agoAll talks by Bret Victor are great, they are listed on his websites but they are more concerned with the future of programming than old languages: http://worrydream.com/ http://worrydream.com/ On the topic of language design, there is also this talk by Brian Kernighan which gives good practical advice if you're building a language and talks about his journey with awk: https://www.youtube.com/watch?v=Sg4U4r_AgJU https://www.youtube.com/watch?v=Sg4U4r_AgJU
- tincholio 4y ago"Simple made easy" [0] by Rich Hickey is a must-watch (even if you never touch Clojure) [0] https://www.youtube.com/watch?v=SxdOUGdseq4 https://www.youtube.com/watch?v=SxdOUGdseq4
- worik 4y agoWhere is C++ on that list?
- sicp-enjoyer 4y agoMost programs you use and internet infrastructure are written in C and C++. Furthermore, it's actively used to develop new software everyday by most large companies.
- adra 4y agoI'd say your first comment is very true and your second is very untrue. There will be sectors that will generally gravitate to c/c++, and a huge boatload that won't touch them with a ten foot pole. Corp languages are jvm based, .net based, js/ts, and maybe Go in some contexts now. None of the companies I've worked at in like 15 years has decided to create new c++ projects (clearly subjective view).
- tmtvl 4y agoBy what possible metric could you consider C++ "mostly dead"? I'm fairly sure that most, if not all AAA games nowadays are coded in C++, for example. Never mind such little known projects like GCC, Qt, and LLVM. It's not a language I care to use, but it's clearly still very healthy: widely used and regularly updated.
- FpUser 4y agoAnd then they woke up.
- latenightcoding 4y agoAs someone who still loves Perl I don't want to say Perl is mostly-dead, but it's dying and it influenced all popular scripting languages today.
- melling 4y agoIt’s been dying for 15 years. First slowly then “all of a sudden” What’s merlyn doing these days? His response to the early warnings that “Perl is dying “ was “more people use Perl now more than ever” The downfall of Perl should be a “case study”. Other communities should learn from the Perl community’s mistakes. Java also had many problems for quite some time but its frequent update cycle seems to have helped.
- thesuperbigfrog 4y ago>> What’s merlyn doing these days? It looks like he's still doing Perl: http://www.stonehenge.com/merlyn/ http://www.stonehenge.com/merlyn/ https://www.oreilly.com/library/view/learning-perl-8th/9781492094944/ https://www.oreilly.com/library/view/learning-perl-8th/97814...
- cardanome 4y agoPerl is nod dying but but in a process of metamorphosis with hope to one day turn into the beautiful butterfly that is Raku
- ThinkBeat 4y agoCobol is far from dead. It is not sexy and I dont know of any systems starting out today using it. But there are massive legacy systems till out there. At least a couple years ago Cobol programmers were in high demand. According to Microfocus [1 (2018)] over 2 million people worldwide are active full-time Cobol programmers, and it is running quite a few mission critical systems. >Companies involved in keeping COBOL-based systems working say that 95 percent of >ATM transactions pass through COBOL programs, 80 percent of in-person >transactions rely on them, and over 40 percent of banks still use COBOL as the >foundation of their systems.
- ithkuil 4y agoIt's not dead, ok. Can we say it's mostly dead? For example, is it more or less dead than perl?
- enduser 4y agoIs someone who is no longer having children but is still a major team player at their employer “mostly dead”?
- lolinder 4y agoSince we're talking about languages, a better question would be "is a language in which no new works are written but which has a large catalog of past works that are still studied by thousands of people 'mostly dead'?" Most would say yes.
- The_Colonel 4y ago> in which no new works are written There's a lot of new code written in most of these languages. It might be existing systems, but the code being written is new.
- enduser 4y agoThe many COBOL programmers are not being paid to study a dead language, they are being paid to adapt, evolve, and maintain living systems written in that language.
- cardanome 4y agoMost of these languages are neither dead nor dying. They are just niche. I just started learning APL this year. It is still actively developed and no you don't need a special keyboard. Plus we have unicode now which makes the special symbols a non-issue these days. Same with most of the other languages. There is Pharo and Squeak for Smalltalk, the pascal community has free pascal. Sure those communities might not be huge but they are not in acute danger of vanishing any time soon. And COBOL is still carrying the economy. Now some languages like ALGOL might actually be dying, sure. Natural languages are considered dead when they lose their last native speaker. Similarly when the last person being able to use a programming languages dies, we can consider that language dead. Which means that we have lots of languages that died at childbirth but once a programing language has managed to go over a certain popularity threshold, it is very hard to kill. Languages don't need to win any popularity contests to be alive. Language maximalism in the sense that you need to be one of the most popular languages or you are considered a failure and dead is just silly.
- agumonkey 4y agoWhat were your use cases for APL ? I love it to bits on principles but never used it seriously, despite all the efforts of dyalog and Aaron Hsu. niche languages have a flavour that mainstream spoils with feverish fads.. I always like to read perl or TCL forums and am surprised by the ideas and productions.
- seanmcdirmid 4y agoAPL is a great language for on the fly number crunching, which is pretty niche like writing with shorthand as a stenographer.
- actionfromafar 4y agoFinance/quant people sometimes use J which is some kind of APL: https://en.wikipedia.org/wiki/J_(programming_language) https://en.wikipedia.org/wiki/J_(programming_language) Edit: also K something something: https://en.wikipedia.org/wiki/Kx_Systems https://en.wikipedia.org/wiki/Kx_Systems
- 4y ago
- habibur 4y agoWindows Win32 API still uses Pascal calling convention instead of standard C. Shadow from the dead. And also there was the 4th generation language movement at that time, 4GL. Defined by coding like writing English sentences, and not much algo. More akin to our no-code, low-code trend. SQL was also a child from 4GL. C/C++ was then seen as 3GL. And then we can now watch 3GL ultimately took over 4GL, at least until now, for half a century. Tidbits. Corrected: COBOL was 3GL.
- zozbot234 4y agoCOBOL came well before the 4th generation of programming languages - it was one of the earliest 3rd-gen languages. One could argue that like 4th-gen languages it was domain specific, but most programming languages back then were tailored to rather narrow domains.
- ThinkBeat 4y agoI have a mild interest in obscure languages. Pascal is almost dead but still there is Delphi, FreePascal/Lazarus and Oxygen. They are all being actively developed. I just wish Embarcadero would stop charging an insane amount for Delphi. Basic is even more nearly dead. There are still a few interesting things left like: https://www.purebasic.com/ https://www.purebasic.com/ Up until a few years ago at least, and I still think it is the case Epic (https://www.epic.com/ https://www.epic.com/) had a huge amount of their codebase in Visual Basic classic.
- shakow 4y ago> Basic is even more nearly dead I would not say so. The BASIC used in the Office pack is the last child of the MS-BASIC/GWBASIC/QBASIC/QuickBasic/VisualBasic lineage, is still (unfortunately?) very much alive, and probably powering a much bigger part of the modern world than we should be comfortable with.
- galangalalgol 4y agoVBA isn't that bad a language. Compiles to native and runs with impressive speed. Lots of built in libraries for numeric programming among other things and fairly easy to call into any dll. The issue is it's accessibility. Like JS and Python people blame the language for what happens when you hand people with no software training and an interest only in solving their immediate problem, a computer language they are productive in. And how can we call basic dead when VB.net is still in the tiobe top 10?
- BlueTemplar 4y agoI was also exposed to a variant of BASIC in high school through my scientific calculator. I wonder if it is still the case ?
- shakow 4y agoIf you are thinking of TI calculators, it's very much still the case; at least until the nspire range completely takes over the older models.
- neilv 4y agoAdditional info about the influence of Simula on Smalltalk: http://worrydream.com/EarlyHistoryOfSmalltalk/ http://worrydream.com/EarlyHistoryOfSmalltalk/
- eternalban 4y agoThat chart with Java is amazing. And in my personal case, also true. Actually paid for something called SmalltalkAgents (which was pretty cool btw) just a bit before Java happened. Then Java happened. On QKS' SmalltalkAgents: http://computer-programming-forum.com/3-smalltalk/fe67cb349c995f90.htm http://computer-programming-forum.com/3-smalltalk/fe67cb349c... (amazed that there is not a single image of this software on the net.)
- denton-scratch 4y agoPL/1 was an IBM mainframe language; but Intel made a compiler for a stripped-down version targeting 8086, called PL/M (Programming Language for Microprocessors). PL/M was (I believe) the main language used in writing the CTOS/BTOS operating system (Convergent Technologies/Burroughs). PL/M was a nice language. It was suited for system programming (structs, pointers). I first came across it in some introductory programming book I bought from a second-hand crate. A lot of my early programming lessons came from that book, even though I had no access to a PL/M compiler. I have no idea who wrote it, or what its title was.
- Rochus 4y agoPL/M was a nice language indeed; I used it on embedded 8085 based systems; but I don't think it had many overlaps with PL/I; but there were similarities.
- karmakaze 4y agoMy encounter with PL/I was with some 3270-style Wang terminals for their minicomputers. They were programmable by writing PL/I which got compiled and stored in the terminal's NVRAM. There wasn't much you couldn't do with it, I made macros that could copy blocks of text between two different terminal sessions as well as a bunch of cursor positioning and general clipboard operations. PL/I is quite a nice language.
- wglb 4y agoHaving programmed in both, the most similarity is in the name. PL/I is a vastly complicated language that needs a specialized grammar to describe and PL/M works on microprocessors. Oh, and another flaw with the article is that PL/M was not invented by Gary Kildall, not Intel.
- denton-scratch 4y agoWell, I said that Intel produced a compiler. I see from Wikipedia that Kildall did indeed develop PL/M; the same article says that Intel "promoted" it. The compiler that we used was branded Intel. It sounds like Kildall developed it for Intel. [Edit] My notion that PL/M was a cut-down version of PL/I was clearly wrong; I never used PL/I, the closest I got was reviewing a few documentation pages.
- uncletaco 4y agoI worked at a bank and the truth of the matter is COBOL is never going away. Most large banks run on it.
- BlueTemplar 4y agoIt will go away one large bank bankruptcy at a time (perhaps several at a time in case of country bankrupcy). Who is going to use COBOL for a new project at a new bank ?
- KerrAvon 4y agoSurprised this doesn’t mention Smalltalk’s huge influence on two major living languages: Objective-C and Ruby, both of which use the Smalltalk object model, dynamic message passing paradigm and all, which is very different from how most other OOP implementations work. In the long run: Objective-C will be gone in 20 years, but Ruby won’t. Outside of ObjC interop facilities, Swift will retain some of Objective-C’s Smalltalk heritage, as one of many influences.
- alwillis 4y agoAgreed. Leaving out Objective-C using Smalltalk’s object model is a huge oversight.
- hosh 4y agoThe writing of history (historiography) is not meant to be a minutely detailed account of everything that happened. History is a narrative, a story about how we came to be here, and sees the past with a particular lens. I think this particular history was meant to bring appreciation of influential yet obscure and niche languages for the current generation of developers and software engineers. I doubt it was meant to be definitive or exhaustive. In fact, at the very bottom of the article, there is a link to the Encyclopedia of Programming Languages with over 8000 entries. The influence of Smalltalk’s “everything is an object” on Objective-C and Ruby is probably in there somewhere. Disclosure: I wrote Ruby professionally for over ten years, and learned the basics of OOP with ObjC back in the 90s. I get the significance of Smalltalk’s object model.
- alwillis 4y ago> The writing of history (historiography) is not meant to be a minutely detailed account of everything that happened. History is a narrative, a story about how we came to be here, and sees the past with a particular lens. Of course I get all of that; however, the author also chronicled the influence of these languages and certainly Objective-C use of Smalltalk's object model, a language that provided macOS and iOS such a competitive advantage for many years, it's probably worth a mention.
- Daunk 4y agoI just want to say that I still enjoy BASIC, but via BlitzMax NG. It's a good language to quickly prototype things in - https://blitzmax.org/ https://blitzmax.org/
- nuc1e0n 4y ago> That’s one reason I love studying history. To learn what we’ve lost and find it again. Same here. There's a lot of amazing things which we have yet to learn from the 'also ran' systems of history.
- walnutclosefarm 4y agoThis was a great trip down memory lane for an old retired sometime programmer and software engineer. I learned programming in K & K BASIC on a GE time share machine and FORTRAN II on an IBM 7090. I wrote production code in many of these languages (BASIC, COBOL, PL/I (not much), Pascal, SmallTalk (my favorite)). Among the odder "language" projects I ever worked on was a cross-compiler written in Pascal for a report generator. The compiler generated COBOL as it's object code, which we chose because of it's facility with reading database records, and formatting output for fixed spacing line printers. I'm familiar with all but a couple of the languages in his list, and wrote code in most of them, although in some cases not code that ever went into a product or production environment. ML and CLU, though, I've never touched.
- melenaos 4y agoI once learned Ada for a NATO project. I was amazed by the simplicity you could start a thread and monitor it. Its not dead but you will never see it trending. Its just a niche language as most of the languages at the post are.
- stoneman24 4y agoI’ll shout out for ADA as well. Really enjoyed working with it. Compiler was a nit picking monster but the rigour ensured that you really considered your program. Thanks for making me remember.
- elcritch 4y agoMy only real exposire to Ada was a report for a class project in college. One tidbit that stuck with me is that there were a few DOD projects using Ada after it was first created which actually got done ahead of schedule and under budget. That always impressed me given the normal DOD software track record. Also, I believe people place way too much emphasis on "popularity" of a language. If a language has enough traction to stay alive it can be valuable unless you're doing the most generic web dev stuff around. Heck there's cases where Perl still outshines modern competitors.
- ajxs 4y agoLike some of the sibling posters, I'll use this opportunity to share my feelings on Ada. I checked it out a few years ago, and I was amazed at how much it has to offer. Despite being designed by committee in the late 70s, Ada has many features that remain novel by today's standards. I'd say Ada is a 'must see' for anyone interested in implementing new programming languages, there are many great lessons language designers can take away from Ada.
- kqr 4y agoOne benefit I had from learning Ada was that it treats encapsulation, implementation hiding, inheritance, subclassing, message passing, etc. as separate mechanisms that you can opt into individually. This is a huge difference compared to something like Java or Python where "everything is a class and a class is everything", and if you desire implementation hiding you sort of automatically also opt into get encapsulation and subclassing and the rest of it. When you learn the mechanisms individually, object-oriented programming starts to make a lot more sense! Ada is worth looking at just for that experience alone! Then the other things are a bonus.
- miohtama 4y agoA bit unrelated, but comes to the features of different languages and who introduced. Does anyone else still remember how JavaScript prototypical inheritance was touted as a “good” idea?
- alwillis 4y agoI just posted a link about NewtonScript [1] in this thread, which had prototypical inheritance in the early 90s, which JavaScript later used. Short answer: it's more memory efficient than a full-blown OOP system. I was pretty active in the Newton MessagePad community back then and I knew lots of Newton developers; they loved NewtonScript and raved about prototypical inheritance. [1]: https://news.ycombinator.com/item?id=34047775 https://news.ycombinator.com/item?id=34047775
- jillesvangurp 4y agoThat particular feature came from a language called Self, which was a prototype object based dialect of Smalltalk invented at Xerox PARC in the late 1980s. https://en.wikipedia.org/wiki/Self_(programming_language) https://en.wikipedia.org/wiki/Self_(programming_language) It was one of several big language influences for Brendan Eich when he knocked out Javascript in a hurry a few years later.
- lp4vn 4y agoI would expand this list with: perl(mostly-dead influential), and ceylon and coffescript(these last ones mostly-dead and not so influential, let's be honest). I also would say that ruby is a future mostly-dead language, but I don't want to sound too controversial.
- Yahivin 4y agoCoffeeScript might just be one of the most influential languages. Tons of ES6 features were directly inspired by CoffeeScript and ES6+ JavaScript is the most popular language in the world right now.
- lp4vn 4y agoI'm not sure I agree with you. I'm not denying that coffescript might have inspired ES6+ features, but from this to say that it's a very influential, let alone one of the most influential languages, is a big leap. In my opinion, of course.
- ameliaquining 4y agoEach of the languages on the list influenced many subsequent languages, not just one.
- amval 4y ago> I also would say that ruby is a future mostly-dead language, but I don't want to sound too controversial. Aren't you just saying it anyway? Why do you think this?
- lp4vn 4y agoI developed a lot of projects with ruby and yet I can't think of a single reason to opt for ruby over python or typescript. Ruby doesn't do anything better both in terms of language or platform than its already very well established competitors. It's my understanding that ruby rose to prominence mostly because of ruby on rails, now that RoR is in a downward trend I think ruby will follow the same trend until it's reduced to a small community of enthusiasts in the same way that happened to perl.
- Rochus 4y ago> While SIMULA wasn’t the first “true” OOP language, it was the first language with proper objects and laid much of the groundwork that others would build on. This is wrong. Simula 67 was the first object-oriented programming language; though the term is said to be coined by Alan Kay who specified Smalltalk-72; but he understood and still understands object-orientation differently than we understand it today; our understanding of it today is more like what Simula 67 introduced; remarkably, Smalltalk-76 represented a significant departure from Smalltalk-72 toward the concepts already known in Simula 67; the primary difference of Smalltalk 76 from Simula was dynamic typing and the conception of even simple types as classes. Simula 67 was still actively used in the nineties (e.g. as a teaching language at Stockholm University until 1997). The performance was comparable to that of C++ or Pascal, definitely faster than Smalltalk on comparable machines.
- danbmil99 4y agoFORTH Lives on in every stack machine
- JadeNB 4y agoThe whole point of this list is to chronicle influential (but "mostly dead") programming languages; if they were counted as alive because of their influences, then they'd still be alive. But, also, Forth isn't on the list.
- danbmil99 4y agoMy point is FORTH should definitely be on the list. It is pretty much dead as an actual programming language in that no one programs in it anymore. But it was/is very influential... For example, PostScript is basically a dialect of FORTH.
- alwillis 4y ago> My point is FORTH should definitely be on the list. It is pretty much dead as an actual programming language in that no one programs in it anymore. Forth—not dead! The Forth community just had their 37th conference a few months ago [1]. It's obscure no doubt but it's still being used and dev tools are still being developed and updated. Apparently the FedEx handheld scanner runs on Forth and it's also used to create firmware and boot loaders [2] for various embedded systems [3]. [1]: https://forth-standard.org https://forth-standard.org [2]: https://www.freebsd.org/cgi/man.cgi?query=loader&sektion=8 https://www.freebsd.org/cgi/man.cgi?query=loader&sektion=8 [3]: https://www.forth.com/resources/forth-apps/ https://www.forth.com/resources/forth-apps/
- ComputerGuru 4y agoYeah, FreeBSD is/was a big Forth user for its boot menu, but that’s being ported to Lua now.
- 4y ago
- boulos 4y agoNot mentioned in the article or in prior discussions, but Scala seems "dead" to me. Or at least extremely niche and unlikely to take off. AFAICT, Scala has basically been replaced by Go for backends and Kotlin (or just plain Java) elsewhere.
- cardanome 4y agoScala 3 released like a year ago. Yes, it is niche but not extremely niche. People either into functional programming or that are part of the JVM ecosystem have at least heard of it. It is one of the big alternative JVM languages with Clojure and Kotlin. Sure it won't ever overtake Java and Kotlin is eating a bit of its lunch but Tech is not a popularity contest.
- valenterry 4y agoScala was certainly more hyped before (for better or worse). If Scala is what you would call dead then other languages like Haskell, Clojure, Racket, OCaml all must be considered dead as well, which doesn't make much sense.
- gumby 4y ago> BASIC was the first language with a real-time interpreter (the Dartmouth Time Sharing System), beating APL by a year. Of course Steve Russell wrote the first Lisp interpreter years before that. Not to take away the significance of BASIC, but that wasn't it. I think in fact many of the "Significance" sections are rather condescending; COBOL was significant in being the first "mass" high level language, transformational in the same was BASIC was (and more than BASIC). FORTRAN was hugely influential on computing, is mentioned all through the article, yet isn't considered "influential"?
- BlueTemplar 4y agoMore like it's not considered mostly dead (still used and taught in high performance computing).
- ameliaquining 4y agoFortran presumably didn't make the list because it's not dead. Scientific-computing labs still use it directly, and perhaps more importantly, if you write code today that does any kind of linear algebra, it's probably using foundational libraries that are written in Fortran and still actively maintained as such, even though most users call them through FFI from newer languages that offer a better developer experience.
- gumby 4y agoCOBOL is not dead, if few (if any) new projects are launched in it. APL is hardly dead; J is more an implementation than a descendant IMHO.
- fsckboy 4y agothe only knowledge I have of Fortran not being dead is that its use in scientific computing is brought up in EVERY SINGLE ONE OF THESE PL CONVERSATIONS I've been in dating back to the 1970s. (It was the first language I learned if you you don't count HP calculators) COBOL too. Do the people maintaining these libraries get harangued on a weekly basis about how Fortran has undefined behavior and the PDP-11 and IBM 360 ISAs are not appropriate for modern multi level cached pipelined speculatively executed CPUs? How can their matrix multiplication libraries be as fast as they can be if they are assuming/relying on memory allocation layouts that don't exist any more in the hardware?
- GMoromisato 4y agoMy friend is working on KlongPy (https://github.com/briangu/klongpy https://github.com/briangu/klongpy) which is has a terse array-notation language similar to APL. I'm curious: Is there anything interesting in APL that hasn't yet been implemented in NumPy, etc.?
- abrudz 4y agoConcise infix notation with combinators.
- graymatters 4y agoCan someone with real knowledge on deployment and usage of these language tell where are they being used (beyond a dedicated hobbyist community)? Which industries? What systems? Volume of transactions? Genuinely interested and will appreciate it. Thank you in advance.
- rebeccaskinner 4y agoI don't have a ton of experience with any of them, but I've had a few run-ins with COBOL. Most notably, at my last job I was working in a team that was actively working to replace a large legacy COBOL system for retail supply chain management. I never worked with the COBOL applications directly, but the stakeholders on my projects overlapped with users of that system. Less personally, but with more data points, there's a large employer in my city with a substantial code base in COBOL who actively recruit career changers and teach them COBOL. I've met several people who went that route while doing outreach and trying to mentor new developers in my community. My general impression is that the large COBOL codebases are used across a lot of different parts of industry, and for a lot of different things. The most common feature is that COBOL applications continue to be used in organizations that are so dysfunctional and bureaucratic that they can't successfully agree on how to replace it. The general shape of the problem seems to be that business decisions were made decades ago, and written into the codebase. Replacing the codebase would mean that someone at some level would need to sign off on requirements, which would mean taking responsibility for something, and the organizations that can't move off COBOL are so toxicly risk averse that nobody will make an affirmative statement about any requirement. Instead, they manage to just barely get by with a combination of very experienced developers who can retire comfortably and DGAF and make decisions, and very junior (and poorly paid) developers too naive to push back or ask too many questions.
- int_19h 4y agoI wouldn't be so dismissive of Algol 68. It wasn't particularly successful in production, but then neither was Algol 60. OTOH conceptually the former feels closer to modern PL design, with a greater emphasis on consistency and orthogonality. And if we're talking about specific features that ended up in other languages, well - the C keywords "void", "struct" and "union" all came from Algol 68.
- jejones3141 4y agoNot to mention "long" and "short". Also, yes, PL/I had a POINTER type, but just one. Algol 68 did what languages do now, i.e. specifies the type of thing the pointer points at (or the type of the thing the REF type references; speaking of Algol 68 vocabulary, "dereference" made it into common CS jargon).
- int_19h 4y agoYup, I totally forgot "long" and "short". Although I'm not sure that counts as a lesson learned given that C still came up with "double" for what should have been "long float". Typed pointers were an ALGOL-W thing originally, though.
- p_l 4y agoAlgol 68 structs descend, at least partially, from JOVIAL (which was based on ALGOL 58). A language that is annoyingly still in use, from what I heard.
- Taniwha 4y agoI'd agree - I think the classification of Pascal as an Algol60 derivative is a bit off - Wirth was on the committee that wrote Algol68 - my impression is that Pascal is essentially all the easier bits of Algol68
- int_19h 4y agoWirth was on the committee that worked on what was then referred to as "Algol X", but at the time there was no agreement on what exactly that would be. His (and Hoare's) proposal was more incremental relative to Algol 60, removing some features and adding others - most importantly, first-class strings, pointers, and structs - while retaining the overall syntax and semantics. This proposal did not get enough support on the committee, though. Some people rejected it because they saw the additions as too minor, not warranting a whole new language so early. Others didn't like the fact that it relied on the same BNF + verbiage approach to define the spec that resulted in numerous ambiguities to Algol 60 (which was supposed to be rectified by the new formalism just developed by van Wijngaarden). So Algol 68 ended up evolving in a different direction overall, which Wirth consistently criticized, and stepped down from IFIP after it published the first draft of the language. He took his own proposal and turned it into Algol W; and that, in turn, became Pascal. So you could say that some of the concepts that made it into Pascal compared to Algol-60 - namely, pointers and records - had the same origin as those in Algol-68, but the point of divergence precedes either language.
- Termich 4y agoDoes anyone have book recommendation on learning COBOL?
- kriro 4y agoFor reference, 4 of them are still in the current TIOBE top 50 (https://www.tiobe.com/tiobe-index/ https://www.tiobe.com/tiobe-index/): BASIC: 6 and 13 Pascal: 16 (Delphi/OP) COBOL: 27 ML: 50 Mentioned as being in the next 50 (for reference, Elixir and Clojure hang out in this tier): Smalltalk, APL Not in TIOBE top 100: ALGOL, PL/I, CLU, SIMULA 67
- pyinstallwoes 4y agoNo Forth? Wow.
- wglb 4y agoSo much wrong with this and the article linked in first sentence. Just a few notes. To be pedantic, COBOL was invented by the Navy, mostly by GMH. And to call it dead is not consistent with the humongous body of code that keeps many large institutions afloat. And Fortran is very much alive in many scientific endeavors, including the amateur radio program WSTJX which implements various weak signal protocols such as FT8, WSPR, and JT 9. These are built by Joe Taylor, Nobel Laureate in physics for work on pulsars and their declining period due to gravitational drag. These protocols are useful in weak signal work such as amateur radio moonbounce. And SQL was not invented by oracle but by IBM. There are too many other flaws in both articles to list here. The definition of death here is suspect, and the reasons noted not well reasoned. If one is truly interested in history, I suggest reading about the life and influence of not only GMH and Jean Sammet and the book covering the 120 programming languages in use in 1960. Edit: Full disclosure: I’ve professionally programmed in a significant number of the languages here, and my career beginning predates the invention of several of the important languages noted in these articles. I have strong opinions about all of these languages and often share them whomever wants to hear them and many who don’t. (Edit typo)
- jamesfinlayson 4y ago> the 120 programming languages in use in 1960 Geez, I think I'd struggle to name 120 programming languages in total right now.
- wglb 4y agoAnd there have been more than a handful invented in the intervening 60 years.
- gamegoblin 4y agoNot 120, but a decent list of stuff I'd never heard of: https://en.wikipedia.org/wiki/Timeline_of_programming_languages#1960s https://en.wikipedia.org/wiki/Timeline_of_programming_langua...
- hackerman123469 4y agoI guess people reinventing the wheel with a new programming language isn't just some newer-age thing, but happened frequently decades ago too.
- dgudkov 4y agoWhen I was at 7th grade I only knew BASIC. Then someone told me about Pascal and it blew my mind, because it didn't have the GOTO statement.
- mikewarot 4y agoProgramming languages are more like machine tools. The old and really fun to watch metal planer is like assembler. It plows though things leaving a stress free flat surface, but it's less efficient to work with. C is like a lathe, there are older and newer features, but they all work essentially the same. Pascal is like a Bridgeport, easy to understand, and straightforward in use. Unfortunately the main vendor got greedy and drove up the price too high. All the newer languages are like CNC machines, that come in all shapes and sizes.
- p_l 4y ago... I fear then that Lisp (especially Common Lisp) is that insane custom-programmed set of 6dof robots with tool changers.
- hosh 4y agoIt’s kinda amazing to me that the main discussion this article provoked is the “deadness” of the language, rather than the ideas and influence these languages have. For example, buried in there were things about CLU and Argus, and got me reading the Argus paper to see if there were anything interesting i can learn about contemporary distributed or federated systems (like Mastadon).
- dang 4y agoThat's mostly an effect of the title, which included the word 'dead' until I finally realized we needed to take it out.
- dang 4y agoDiscussed at the time: Most(ly dead) Influential Programming Languages - https://news.ycombinator.com/item?id=22690229 https://news.ycombinator.com/item?id=22690229 - March 2020 (289 comments) also Most(ly dead) Influential Programming Languages - https://news.ycombinator.com/item?id=24602741 https://news.ycombinator.com/item?id=24602741 - Sept 2020 (13 comments)
- lawxls 4y agoNo ABC? (https://en.wikipedia.org/wiki/ABC_(programming_language) https://en.wikipedia.org/wiki/ABC_(programming_language)
- alwillis 4y agoAnother missing tidbit: when the Mac was introduced in 1984, Object Pascal was the only language supported by Apple to write early Mac software [1]. Apple also shipped a version of UCSD Pascal for the Apple ][ as well. [1]: https://en.wikipedia.org/wiki/Object_Pascal https://en.wikipedia.org/wiki/Object_Pascal
- teleforce 4y agoThis is an excellent talk on designing successful programming language by Brian Kernighan [1]. In the beginning of the lecture he did show a picture of the Tower of Babel depicting plethora programming languages as it's appeared in the cover of Communications of the ACM (CACM) magazine in January 1961 and most of the programming languages mentioned in the article were already there! [1] Brian Kernighan on successful language design: https://youtu.be/Sg4U4r_AgJU https://youtu.be/Sg4U4r_AgJU
- porknubbins 4y agoThis was interesting, even as a non PL person. Everything before C and Basic is kind of hazy and distant to me. This is the first I’ve heard of the concept of four mother languages. I wonder if there is anything that explains it more.
- alwillis 4y agoMy personal list of dead but influential languages would include NewtonScript [1]: With the cancellation of the Newton project by Apple in 1998,[8] all further mainstream developments on NewtonScript were stopped. However, the features used in NewtonScript would continue to inspire other programming models and languages. The prototype-based object model of Self and NewtonScript was used in JavaScript, the most popular and visible language to use the concept so far. NewtonScript is also one of the conceptual ancestors (together with Smalltalk, Self, Act1, Lisp and Lua) of a general-purpose programming language called Io[9] which implements the same differential inheritance model, which was used in NewtonScript to conserve memory. [1]: https://en.wikipedia.org/wiki/NewtonScript https://en.wikipedia.org/wiki/NewtonScript
- forgotpwd16 4y agoNot sure why NewtonScript rather Self. Self is the originator of prototype-based programming and differential inheritance (although the term differential programming was preferred). NewtonScript adopted them, as did JS and Io.
- bb88 4y agoAda95 was good because it forced people to think about software and type safety.
- AlbertCory 4y agoHe does mention SNOBOL (and there was SPITBOL which was compiled, not interpreted). I'd like to think it influenced Awk, but I don't know if that's really true. I had an interview with Rational Machines in the early 80s, and they were Ada fanatics. A friend of mine who also interviewed there said it was really more like a religious cult.
- jhallenworld 4y ago"the question is why did C++ survive the Javapocalypse"... I was thinking you can't run Java on AVR, but you can run C++ (Arduino..) But here you go: https://atmega32-avr.com/java-virtual-machine-for-the-atmel-avr-atmega8/ https://atmega32-avr.com/java-virtual-machine-for-the-atmel-... Even so, this VM is written is C, with no JIT compiler on the 8K microcontroller, so C++ is much faster. Hmm.. now I'm wondering if GCJ could work with avr-gcc..
- folmar 4y agoThat's just suboptimal microcontoller choice. There are a lot of microcontrollers that directly the Java Micro Edition instruction set, for example aJ-100.
- nigamanth 4y agoTrue facts regarding Java. When Java came out, it hindered the ability for the other programming languages to grow. Till date, Java stays one of the most popular languages.
- fulafel 4y agoAre you referring to this? > Smalltalk wasn’t the only casualty of the “Javapocalypse”: Java also marginalized Eiffel, Ada95, and pretty much everything else in the OOP world I think it stifled one set of languages and helped others, while helping the "enterprise software" c++ crowd acclimatize to 70s era inventions things like memory safety and garbage collection. Python, Ruby, and JVM langugaes like Clojure and Scala were helped I think.
- iopq 4y agoSurprised Prolog isn't mentioned. It greatly influenced Erlang (the first version was written in Prolog)
- college_physics 4y agoover decades there has an enormous amount of discussion about the rise and fall of various programming languages but somehow it remains for ever a shallow analysis, more noise than signal. what do we really know about this phenomenon at the end of the day? one problem is the difficulty of measuring what we are talking about: when is a language "dead", when the last program in production stops running? when the last programmer that can program in it retires? when the last school that is teaching it removes it from the curriculum? or maybe when the last computer scientist that can enhance it decides there are richer academic and/or commercial pickings elsewhere? another problem is the objective measurement of any of the above definitions. beside the design and availability of surveys, objectivity was always a problem given that software is big business and hence various actors have incentives to skew the perceived state to support their aims. but it has become particularly problematic in the current interconnected universe of developers that leads to very pronounced virality and network effects which may or may not persist. finally the scope of programming is ever expanding as more and more aspects of society and economic life get digital but the process is still in full swing, materially incomplete and dominated by idiosyncratic oligopoly circumstances. think for example about the billion mobile devices around the planet that are currently practically impossible to program by their users. one could imagine e.g., of the "dead" languages (Basic?) suddenly return from the grave as an ubiquitous mobile device programming paradigm. A programming language that was useful in the past in a certain context may become useful again if a similar context reappears. what would be interesting is a sort of "principal component analysis" of the programming language space: identifying the principal functionalities / capabilities provided by different languages. a dead language could then be defined as one that is completely dominated (effectively a subset) of another one along all relevant principal component directions
- orthoxerox 4y ago> one problem is the difficulty of measuring what we are talking about: when is a language "dead", when the last program in production stops running? when the last programmer that can program in it retires? when the last school that is teaching it removes it from the curriculum? or maybe when the last computer scientist that can enhance it decides there are richer academic and/or commercial pickings elsewhere? When no company willingly starts a greenfield project written in this language.