5 ms·
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
by mpweiher 11y ago
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. :-(
- munin 11y agoany 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!
- madgar 11y agoI'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.
- fmap 11y agoYou're seriously underestimating the amount of work that goes into a phd, or into writing a textbook...
- munin 11y agoI'm a current PhD student in programming languages, I don't think I am...
- fmap 11y agoLet'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...
- munin 11y agookay, 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.
- mathetic 11y agoAnd what would be the omitted part of programming language theory?
- chrisseaton 11y agompweiher 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.
- chrismonsanto 11y agoI 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.
- chrisseaton 11y agoI 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.
- seanmcdirmid 11y agoYou 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...).
- seanmcdirmid 11y agoThere 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?