5 ms·
I 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, reg
by plsceptic 11y ago
I 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 agoWhy not just let the market sort it out? Because software development will never become software engineering if we continually do the equivalent of changing the number and measure system every five years.
- seanmcdirmid 11y agoYou mean because the tools that we use in real engineering have remained the same for the last 100 years?
- angersock 11y agoSo, speaking as somebody who went to school for real engineering (mechanical)...the tools haven't changed as much as you'd expect. We standardized on steel nomenclature ( http://en.wikipedia.org/wiki/SAE_steel_grades http://en.wikipedia.org/wiki/SAE_steel_grades ), and on airfoil design ( http://en.wikipedia.org/wiki/NACA_airfoil http://en.wikipedia.org/wiki/NACA_airfoil ), and on formulas for common engineering problems ( http://en.wikipedia.org/wiki/Roark%27s_Formulas_for_Stress_and_Strain http://en.wikipedia.org/wiki/Roark%27s_Formulas_for_Stress_a... ), and so on and so forth. We've gotten better tools for design (say, CAD via Solidworks or Autocad or ANSYS or what have you), but the implementation stuff has been near-constant for almost a century. And that has meant that we've been able to routinely build gigantic things with hundreds of people that last for decades and can be repaired--software doesn't have the same track record of quality, safety, or anything else really. That's not a bad thing, mind you; however, our industry does shoot itself in the foot by either mudballing on existing languages or by creating lots of incompatible new languages to solve similar problems. Again, it's as though the mechanical engineers had to learn a new type of math for the same calculations every five years.
- seanmcdirmid 11y agoMost new programming languages are very incremental. For every Rust and Elm, there are 10 Typescripts, Darts, and Gos. Its like being handed a new and slightly improved AutoCAD every 5 years, which isn't very strange at all. If you leave the industry for 15 years, you might not be familiar with the version of AutoCAD when you come back. Now the more edgy stuff (say Elm, Rust, even Haskell, and perhaps Scala if you choose to use it that way) IS a bit more different, but adoption is challenging as a result. Its like being handed a new CAD program with a new diagramming paradigm (something AutoDesk would never do, by the way, as their users would kill them).
- the_af 11y ago> and rest were mere reskins of C ...or "Java with minor improvements". But I think you're talking about PL creators/designers, not researchers. Surely PL researchers don't want yet another reskin of C/Java.
- reality_czech 11y agoI think a big part of it is that a lot of the traditional programming language researcher obsessions are not that interesting to working developers. For example, proving software correct is used in a very, very small number of cases (mostly safety-critical things like elevators or medical devices), but for most projets the extra development time is nowhere near worth the benefits. Plus for many things like user interfaces, the specification for getting them "correct" may not be any shorter than the code itself (sometimes it's longer.) Elegance and minimalism (how small can you make the language's standard library? etc.) are loved by academics but nobody else cares. Plus, most academics don't have any awareness that different languages are useful for different things-- because they've never actually done any of the different things. You might want a C-like language to write a kernel, but a TCL or Javascript-like language to write a graphical user interface. Perhaps you want a MATLAB or R-like language to do numerical work. Most PL people don't have any awareness of the different use-cases so they try to produce "the messiah language" that will solve all problems. It never works. The other thing is that there's not a lot of awareness of the psychological aspects of programming in the PL field. For example, sometimes it is desirable to limit the expressiveness of a programming language in order to make code easier to understand and share between people. These tradeoffs are almost never discussed (I have never seen an academic paper discuss them). Instead languages like Java and Go are ridiculed for the "missing" features (didn't they know that higher-order types were invented by academic language X Y years ago? etc. etc.)
- the_af 11y agoThe counterpoint is how many PL creators ignore all existing research and go on to make the same old mistakes.
- Retra 11y agoAKA, Java's 'billion dollar mistake' of allowing null references when there is no great justification for it.
- reality_czech 11y ago
- nmrm2 11y agoIt sounds like you missed the point. The point of the article was that a lot of PL research is focused on non pure SE problems/domains. That is, a large part of the argument was that only a very small amount of PL research is about designing languages that are intended to be used as programming languages in the software engineering sense of the term. The article gives a myriad of examples of PL researchers who have contributed novel results to non-PL fields of Computer Science by applying PL techniques. In these cases, PL researchers are solving open problems in other areas of Computer Science, such as checking properties of software-defined networks or adaptive Bayesian inference. In these two cases, these are areas where PL researchers applied PL techniques to open problems that other subdisciplines were already studying, and came up with novel and competitive/superior solutions. In these cases, the "purely software engineering"-oriented metrics/goals mentioned in your post are irrelevant -- the scientific contributions of the PL research exist and can be evaluated independently of the software engineering implications of the work. The language is the methodology, and isn't necessarily intended for use in software engineering.
- mafribe 11y agoAs a working PL researcher, I agree with plsceptic: we, the field of PL research, have a measurement problem. We don't have empirically validated and methodologically sound studies that quantify the "dividends" of one PL or PL feature "over another, such as reductions in deficits, program size, or development time". To be sure, all this can be measured in principle, and measurement is one of the hallmarks of being a science. Alas, things are not so simple: 1. Like with cosmology or string theory, experiements that would readily decide scientific questions (like Java is a better programming language than ML) are prohibitively expensive. We could take 10 million programmers, split them in two groups and let them use the same problem but with one group using language L and the other language L'. Let this exeriment run for 10 years. Naturally, during that experiment, both groups must not, in any form or shape, communicate with each other. Due to the sheer expense of such an experiment, it's never going to happen. 2. Like the social sciences, reflective humans are integral part of any relevant experiement, leading to all manner of problems. For example the participants could actively sabotage the experiment. Of course PL research isn't the only field that lacks easy empirics. And like those, PL shouldn't let the perfect be the enemy of the good. It's quite clear that PL features do have positive productivity consequences, with garbage collection being the most clear-cut example. The interesting question is what do we do the absence of good empirical methods. One answer, and one that has been supremely successful is mathematical proof, although there is a real danger of loosing touch with what's needed on the proverbial 'ground'. Another answer, and one that is clearly being taken, is to let a form of social evolution play out: flood the world with programming languages, and see what happens. The poster complains about this flood and I understand why this can be seen as a problem, but I see this flood of new PLs as a sign of PL research's triumph: making new programming languages (for sequential computation) is now so easy that it's a frequent topic of undergraduate dissertations. Note the qualifier: while PL development is essentially played out for sequential computation (except at the margins) and not a research topic any more, languages for parallel and distributed computation is a wide open field. Note that there are virtually no typing disciplines or verification methodologies comparable to dependent types for non-sequential computing. I would also like to correct the misconception that PL research is (soley) about developing new languages. Clearly what's a good language depends in parts of the application domain. PL researchers are few and application domains are many. Consequently, a core component of PL research involves the following activities. a. Finding repeated patterns in software, and the software construction and evolution processes. b. Analysing these pattern mathematically, to find common abstractions. E.g. monads as generalised sequential composition, pattern matching, or various forms of interaction as a common form of computation. c. Automatising repetitive activities, e.g. compilers, or testing-tools.
- chriswarbo 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. There's certainly a lack of empirical user research in the field, when the research has that aim. However, the point of many research languages/features is not that it reduces development cost, etc. but that it exists at all. The article gives examples of non-PL research, eg. the discovery of an incremental algorithm to calculate convex hulls, and these are legitimate results on their own; regardless of whether they "lower convex hull discovery costs", etc. The PL angle is the discovery of general abstractions, eg. a language for incremental computation, of which convex hull discovery is just one of many programs. The discovery of such an abstrction is also a legitimate result on its own; regardless of whether it "lowers incremental algorithm discovery costs"; etc. These results are a "pure" basis for language and library implementors to work from. If that incremental computation language only existed as, say, a collection of Java classes, then it would be difficult for other implementors (eg. in Javascript) to know which parts of the architecture are fundamental to the approach and which are artefacts of using Java. Of course, when investigating which primitives to use, there may be no existing language capable of expressing them (short of embedding an interpreter; in which case, you've just created a new language anyway!). Few academic language creators expect their languages to be adopted. They're usually proofs of concept, or meant to inform and inspire future work. Only a few are meant to be used for real work (for one thing, it places a maintenance burden on the researcher!).