11 ms·
What is PL research and how is it useful?
- deleted 11y ago[deleted]
- mlitchard 11y agoI imagine the burden will be mitigated by not requiring everyone to have the same level of expertise. The model I see is an architect using the type and proof system to make a language that describes the problem domain at hand. It is this language that will be for the rest of the team. Now, will it look familiar? I would hope so.
- plsceptic 11y agoI don't think the author actually demonstrated the usefulness of PL research, at least not enough to convince me of it. For that I would need to see actual, regular controlled experiments from PL researchers showing that a given language or construct yields measurable dividends over another, such as reductions in deficits, program size, or development time. Instead what you get from PL researchers is papers full of conjecture advocating some such language or construct, but seldom any scientific evidence to support any of it. Further, programming languages by themselves, in 2015, don't matter that much. Unless a language has an industrial-strength implementation, a robust tool chain, and a vast collection of libraries, it won't, or at least shouldn't, gain widespread adoption. I think we have far too many languages as it is. Of all the languages I've learned or at least been exposed to, only a handful were genuinely novel, such as Common Lisp/Scheme, Smalltalk, and Haskell, and rest were mere reskins of C. The compile-to-JavaScript languages are easily some of the worst offenders, and it leads me to wonder, how many new languages are the product of a good faith effort to solve a yet-unsolved or poorly-solved problem, and how many spring largely from the vanity of their inventor, who dreams of becoming the next great BDFL, being invited to give keynotes at conferences, and capriciously giving his thumb up or down to enhancement proposal like a Roman Emperor deciding on the fate of a fallen gladiator in the Colosseum? I actually think we as an industry could benefit from a PL moratorium. How many of us have had to use a language with poor or no IDE support, or one that lacked native code compilation (JiT or otherwise), or that had gaping holes in its standard library simply because it was new and trendy?
- seanmcdirmid 11y ago> For that I would need to see actual, regular controlled experiments from PL researchers showing that a given language or construct yields measurable dividends over another, such as reductions in deficits, program size, or development time. You might be interested in Stefan Hanenberg's research: https://www.dawis.wiwi.uni-due.de/en/team/stefan-hanenberg/ https://www.dawis.wiwi.uni-due.de/en/team/stefan-hanenberg/ > Instead what you get from PL researchers is papers full of conjecture advocating some such language or construct, but seldom any scientific evidence to support any of it. There is PL science and PL design. You won't see much PL design anymore in the academic conferences, they are mostly oriented toward PL science these days. Did you read the article at all? Excerpt: > But the main point I want to make is that PL research is broader than designing and implementing new languages. To me, a PL researcher is someone who views the programming language as having a central place in solving computing problems. In other words, PL research is not about designing PLs these days. > Further, programming languages by themselves, in 2015, don't matter that much. Unless a language has an industrial-strength implementation, a robust tool chain, and a vast collection of libraries, it won't, or at least shouldn't, gain widespread adoption. That is like saying theoretical physics research doesn't matter much anymore. We are reaping the benefits of 20 year-old PL research today, what about 20 years from now? Have we reached a point where what can be tried and improved in PL has already be done? PL is finished as a field where we can make progress? > Of all the languages I've learned or at least been exposed to, only a handful were genuinely novel, such as Common Lisp/Scheme, Smalltalk, and Haskell, and rest were mere reskins of C. What about the experimental languages that you haven't been exposed to? Like that first live programming language called Flogo II in somebodies dissertation? You will never program in that, but it moved us forward. > largely from the vanity of their inventor, who dreams of becoming the next great BDFL, being invited to give keynotes at conferences, and capriciously giving his thumb up or down to enhancement proposal like a Roman Emperor deciding on the fate of a fallen gladiator in the Colosseum? Trust me, there is no glory to be had in this game. At best, you'll get your name written down in lots of places, but even Guido van Rossum has a day job. > I actually think we as an industry could benefit from a PL moratorium. Why not just let the market sort it out?
- angersock 11y ago
- JesperRavn 11y agoI think a better illustration of the usefulness of PL research is to compare the languages produced my Microsoft and Google. Microsoft produces C# and Typescript. Google produced Go and Dart. I think it's fair to say that C# is a better language than Go. The biggest flaw in Go (lack of generics) is met with the weak excuse that they haven't figured out how to do it right. I don't know much about Dart, but Typescript is a stellar language. Microsoft has a lot of PL expertise in house, including Simon Peyton Jones. Their languages clearly benefit from expertise in PL theory. Google, on the other hand, favors pragmatism over theory and prefers to draw on software engineering experience. Google's languages aren't bad, they just don't seem to have much going for them as languages. Their failings are partly made up for in other things, like the toolchain, libraries, etc. So I think looking at these real world examples, it's clear that PL theory does lead to better languages, even when one excludes languages like Haskell with little industry adoption.
- seanmcdirmid 11y ago> Microsoft has a lot of PL expertise in house, including Simon Peyton Jones. Their languages clearly benefit from expertise in PL theory. Google, on the other hand, favors pragmatism over theory and prefers to draw on software engineering experience. Google has ALOT of PL expertise in house, so much so that a lot of them don't work on PL. There language design is actually quite competitive to Microsoft's, on the theory, design, and implementation sides. Whenever we go to conferences, you'll usually have similar numbers of current and ex-academics from MS and Google.
- marssaxman 11y agohttp://4.bp.blogspot.com/_D_Z-D2tzi14/S8TRIo4br3I/AAAAAAAACv4/Zh7_GcMlRKo/s1600/ALOT.png http://4.bp.blogspot.com/_D_Z-D2tzi14/S8TRIo4br3I/AAAAAAAACv...
- pjmlp 11y agoYet the best that have came up with are Go and Dart.... While Apple and Microsoft have come up with Swift, F#, F*, C#, TypeScript.... I wonder what those so called PL researchers are doing at Google.
- chipsy 11y agoI love PL research, for all its warts. I worry that it's wasted on most programmers, because we don't get a comprehensive pedagogy of each type of problem that these abstractions are meant to solve, and contexts where a less abstracted approach is preferable. The result is the much maligned cargo cult method - presented with so many options, we invariably end up with all of them put into production at the same time, for the wrong reasons. Experience is gained through a combination of guess and check, and rumor. A lot of the confusion with current PL science as it's presented to programmers is in the emphasis on mathematical methods. Restrictions that are proven to improve statistical metrics or lead to important technology within the toolchain get dismissed on the regular as being incomprehensible or incompatible with "my style". Surface changes get the majority of attention, bad or good. The PL designer has a tough job in that, if they're going for the general purpose crown, they have to comfort the nervous creatures that are ordinary programmers while also incorporating the best practices of the known science.
- imh 11y agoThe best case for learning this stuff is the old adage along the lines of 'Any sufficiently complicated program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of common lisp.' While not exactly true, it definitely rings familiar with some of the bigger projects I've been on. If you're going to have an system that is practically it's own language, it will benefit from you knowing about language design.
- ninkendo 11y agoOfftopic: So we're all just calling programming languages "PL"'s now? Why is it so hard for people to type? (Seriously though, it's a strange kind of memetic behavior, I rarely see it abbreviated as "PL" ever, but in each comment I scan, people are using "PL" here too. It was enough to get me to click the article just to see if "PL" was some new thing I haven't heard of.)
- Sirenos 11y agoIt's just you. PL isn't that rare an abbreviation, although I mostly see it used within discussions about PL Theory.
- seanmcdirmid 11y agoIt was a more common abbreviation in the 70s when many languages included it in their name, starting I think with Iverson's APL in 1969.
- nmrm2 11y agoPL is a very common abbreviation in the research community and has been for at least decades. Common usage in academia probably stems in part from the fact that conferences are often named by their initials, so the conference on "Principles of Programming Languages" becomes "POPL" and so on.