News for hackers. Stuff that matters.
Re:A Path to Programming Language Theory by mpweiher on Saturday April 30, 2016 @04:38PM (#11603451)
This seems very one-sided, skewing towards type-theory and functional programming.

Is that what is taught these days? No wonder people think that's all there is. :-(

Re:A Path to Programming Language Theory by mathetic on Saturday April 30, 2016 @05:35PM (#11603721)
And what would be the omitted part of programming language theory?
Re:A Path to Programming Language Theory by chrisseaton on Saturday April 30, 2016 @05:52PM (#11603780)
mpweiher could mean implementation theory, so things like how to write better compiler analysis and optimisations and things like that, but in the academic and research community I think that just isn't thought of as coming under the term 'programming language theory'. It's not thought unimportant, it's just a different topic, more grouped under 'systems'.

Looking at mpweiher's profile it looks like he might be interested in things like metaprogramming and object protocols - again they're seen as either part of the software engineering or systems disciplines rather than PLT.

Re:A Path to Programming Language Theory by chrismonsanto on Saturday April 30, 2016 @11:09PM (#11604680)
I disagree that compiler analysis/optimizations would be considered under 'systems', I would expect that kind of work to be published in PLDI, which is definitely the PL community. Systems is more OSDI/NSDI/SOSP.

Metaprogramming also has a rich history in traditional PL venues like POPL and ICFP, such as the Scheme/Racket work on macros, Template Haskell and friends, staged computation work a-la MacroML.

Re:A Path to Programming Language Theory by chrisseaton on Sunday May 01, 2016 @03:19AM (#11605255)
I think POPL is PLT and PLDI is systems.

I say that I'm a systems person to signify that I want to talk about ASTs, IRs and compiler output rather than core language models and formal semantics.

But you could argue about definitions all day.

The relevant observation is that the reason this list focuses on formalisms like type theory and models we can reason about formally like FP is that this is what we mean by PLT.

Re:A Path to Programming Language Theory by seanmcdirmid on Sunday May 01, 2016 @03:37AM (#11605297)
You mean, systems in the OSDI/SOSP sense? Systems and PL implementation (compilers) communities have always overlapped quite a bit, maybe more so a decade ago than today (e.g. see Sanjay Ghemawat and Jeff Dean as PL people who did systems who are now doing machine learning...).
Re:A Path to Programming Language Theory by mpweiher on Sunday May 01, 2016 @09:51AM (#11606160)
Apologies for being a bit brief, it was late.

First, I don't have specific things that were left out (well, maybe a few), it was more a sense of there is so much more, especially that I would want to know and feel I should know when creating a computer language. The important bits.

First and foremost, programming languages are for people and for building systems. Except for CTM, that seems to be almost completely missing (and I had initially missed that it was actually on the list, so my bad).

So anyway, if you want to have theory of programming languages, you have to have something about how people think and work and how that affects programming language design. As an example, I found John Pane's HANDS system very illuminating, or maybe the "Smalltalk: Bits of History, Words of Advice", which talks about iterating on language usability, or Henrik Gedenryd's thesis "How Designers Work". Not saying these are it, but just the flavour I'd be looking for.

On the systems front, I think I'd want to see how problems building systems lead to features in programming languages, what the tradeoffs are etc. Again, without this, what's the point of a theory of programming language? And I do hope features in programming languages are trying to address actual problems building systems. Otherwise, it would be like having theories of engineering without talking about real world objects that we are trying to build such as airplanes, bridges or buildings.

As a tiny and obvious example, what are the tradeoffs between more compile-time checking with longer compile times and more inscrutable errors and a more dynamic approach with much faster cycle times but less checking? And yes, there are tradeoffs.

When you look at Hennessy/Patterson for Computer Architecture, you see (well understood?) tradeoffs that matter in terms of application. Yes, more registers are good, but then you have encode them in the ISA, and your path lengths increase and you need to save/restore more on a context switch, etc.

One thing that should also definitely be on there is HOPL. Histories of people actually designing programming languages, trying to solve specific problems and then figuring out what worked, what didn't and why. Without some sort of reflection like this (=evidence), again, what's the point of even beginning to talk about a "theory" of programming language? Unless it's a definition of the word "theory" that I am not aware of.

Re:A Path to Programming Language Theory by munin on Saturday April 30, 2016 @04:54PM (#11603534)
any book list that starts with "first you should read TAPL and PFPL, then move on to SF and CPDT and read HOTT and of course these three category theory textbooks" is really out of touch IMO. mostly because i don't think there's anyone alive that has simultaneously read all of those works, not even the authors of each individual work!
Re:A Path to Programming Language Theory by madgar on Saturday April 30, 2016 @06:46PM (#11603979)
I'm 27 and while I'm only about halfway through HOTT - it's tough - I've read all the other named books. TAPL was tough too but invaluable to wrap my head around as an undergraduate.
Re:A Path to Programming Language Theory by fmap on Sunday May 01, 2016 @05:46AM (#11605570)
You're seriously underestimating the amount of work that goes into a phd, or into writing a textbook...
Re:A Path to Programming Language Theory by munin on Sunday May 01, 2016 @11:50AM (#11606618)
I'm a current PhD student in programming languages, I don't think I am...
Re:A Path to Programming Language Theory by fmap on Sunday May 01, 2016 @05:48PM (#11608010)
Let's talk again in a few years. :)

In all seriousness, though, I'm also just speaking from personal experience. That said, if you are working in type theory, chances are that you will end up skimming almost everything on this list...

Re:A Path to Programming Language Theory by munin on Sunday May 08, 2016 @01:20PM (#11654779)
okay, I've skimmed everything in that list. I haven't read any of them cover to cover though. that's what I really question, mostly because, who has the time for that? there's especially a lot of shared material between PFPL and TAPL, so why are you reading about the material twice?

the problem is that all of those textbooks are great for an introduction (that's why they're textbooks) and so what is usually more productive is:

1. ask your supervisor or a senior student or postdoc for a 10-30 minute explanation / intro to a topic

1a. skim the relevant chapter(s) from one of the textbooks to make sure you got what they said

2. go read research papers

and frequently, you can just skip straight to 2.

Re:A Path to Programming Language Theory by seanmcdirmid on Saturday April 30, 2016 @06:04PM (#11603810)
There is much more to PL than these topics, of course, and even PL theory is more dominated by a long tail. But then, when everything is niche, what do you cover in a course?