The Era of Programming Languages Exploration is upon Us

9 points by abhin4v


fuzzypixelz

I believe that PLs are for people. As long some people write code for other people with intent and care, then PL design will matter for the original author, for the reviewer, for future maintainers, for hackers and for users (on account of enjoying a program whose behavior was grasped by a person).

For a PL researcher, I imagine the thought of my systems no longer being exclusively exclusively or even primarily used by people quite disheartening.

But the more research we put into empowering people to use PLs with ease (less cognitive load, friendlier tooling, simple semantics, etc) the more attractive and exciting it will be to write code by hand. I am really excited to learn Zig for example because I see many refreshing ideas in it coming from Rust. Of course it will never reach the same level of effortlessness as using LLMs, but it is something that many people care still care about.

I also think that it’s interesting to think about whether it’s possible to have a clean separation between human authored code and LLM-generated code inside a code base, whether we can have language features that help with restricting the effects of running slop (e.g. limited capabilities), etc.

It seems that recent online discourse is increasingly critical of LLMs and already thinking of hopeful ways forward. We’re moving away from the phase of astonishment and panic. That’s quite pleasant to see. Although maybe I shouldn’t have been so online in the first place :P

nemin

This is a disappointingly callous post from an author whose previous work I always enjoyed and found fascinating. I hope she will reconsider her stance.

gasche

There is a weird disconnect between the first part of the post, which suggests that we should de-emphasize applications and can now focus on "the beautiful ideas, the insights, the beauty", and then the second half, which presents the following three examples:

  1. Getting a machine to generate a possibly-correct (who knows?) declarative description of a programming language from an implementation of the language.
  2. Helping Amazon verify their proprietary software faster by adding LLMs in their verification tools.
  3. Asking a machine to produce a declarative specification of a programming language in a problem domain that we don't understand, because we do not allow ourselves to spend the time to learn it (but can still serve as an expert to help the system authors assess the resulting spec).

I am sure that being able to work on all of these faster than before can be exciting and satisfying -- this is the main point of the article. But I fail to understand how they relate to the proposal of worrying less about applications/adoption and focusing more on things that are beautiful and insightful.

(I also think that the post is tone-deaf and weird as a follow-up on the TYPES discussion, but oh well, this is a discussion to have with the author.)

rs86

Reads a bit like written by people under LLM induced psychosis .

jtm
Comment removed by author
Student

Well I suppose this is a manifesto for treating programming language research as a pure science.

I’m rather more interested in knowing what factors make programming languages readable. In this new era there’s already a lot of code that humans only read and don’t write. I strongly suspect that the ideal programming language for this era will be easy to read and make no concessions to being easy to write - the LLM can and should grind on checkers and making things consistent, but as humans we’ll be reading the code, commenting it, and very lightly editing it for the llm to follow our lead.