4 ms·
A very insightful article. Others have commented on its merits, but I have a different question - one I constantly return to: what about languages for professio
by TeMPOraL 5y ago
A very insightful article. Others have commented on its merits, but I have a different question - one I constantly return to: what about languages for professionals? Are there guidelines for design of languages meant for people who already know programming?
Our industry has an obsession with lowering barriers to entry, making everything easy for the novice at the expense of making it difficult for the seasoned professional. It's, like, the opposite of other professions, where tools are optimized to empower those doing the work, not for ease of learning. So are there any guidelines to design of powerful programming languages? Tools that sacrifice the learning curve to make them more powerful and better at managing complexity?
- adrian_b 5y agoI believe that there are enough examples in various niches. One of the most obvious is APL and languages inspired by it. While the original APL would not be a good choice today, due to various features missing in it, for managing program structure and more complex data organization, even the first version of APL had much more powerful methods for handling arrays/tensors than almost all popular programming languages used today. When using a set of high-level APL-like operators, someone familiar with them can avoid wasting a lot of time with writing low-level redundant code, i.e. loops, like you are forced in most programming languages.
- 2RY6gGorhN733X 5y agoBoth the power and simplicity of a program come from its abstractions. Any language that makes new abstraction easy allows for a seasoned professional to easily make simple and powerful programs. Beyond that, the language itself cannot do this work for you beyond providing libraries where other programmers have done it already, and shared their work. And the reason for this is simple. To make an abstraction, we must think, and no language can think for us. The power and simplicity of our code is a product of our thinking. The rest is just technical implementation based on specs. With languages that make abstraction hard, programmers have created tools to help. HTML and CSS have horrible abstraction features. Server-side Perl and PHP and client-side javascript has been used to abstract HTML. Sass, Less, and SCSS are tools invented for CSS. The learning curve for abstraction itself is language independent.
- crispyambulance 5y agoProfessionals, which is anyone who makes a living programming for at least part of their job, suffer from exactly the same sins in the article. If anything, pros suffer from even MORE sins of the stuff that surrounds the language... tooling, builds, deployment, environment concerns. One big one is configurational dumpster fires-- dealing with reams of brutally unpleasant YAML.
- Koshkin 5y agoIndeed, the tooling is the most important aspect on which (a good) developer's productivity hinges these days. As to the languages, according to my observations (and conversations) more experienced professional developers care less about languages and think little about switching from one to another when necessary. (Also, they stop being fans of any language in particular.) Their focus is simple: getting stuff done in the most straightforward and coherent way possible given the constraints imposed on the various aspects of their work.
- gilbetron 5y agoAs an experienced dev, I agree and disagree with what you said. I do care less about languages, although I do have preferences, that part is true. However, I hate switching between them, and vastly prefer to stay in one language. The syntax is not the problem (although it is annoying trying to remember how to do an if-then statement when switching a bunch). It is the libraries and tooling that drives you crazy, plus the paradigms and idioms that are often used. I don't enjoy developing in Java, not because of the language, but because Java codebases are almost always an ornate mess of abstractions and layer after layer of tiny functions that make it incredibly difficult to hold enough of the codebase in your head to get things done.
- goto11 5y ago> making everything easy for the novice at the expense of making it difficult for the seasoned professional. This would be a valid concern if there was only a single programming language in the world. In reality there are thousands, some aimed at absolute beginners and some extremely complex and demanding, aimed for specialized professionals.
- ModernMech 5y agoThis is true in a sense, but in practice the usage of languages follows a Poisson-like distribution. There are maybe a handful of languages used by maybe 80% of people, and then maybe a dozen or so used by another 10%, with the thousands of obscure languages used by a sliver of people. Many of those thousands have at best a single user, the creator of the language. And there is a cost to supporting lots of languages, because a language isn't just a compiler that takes up no room or resources. For a language to thrive it has to have a community, a development team, good documentation, integration with other languages and development tools etc. These things take money and power to bring them into existence, and there really only are so many good PL people in the world. It's not a super huge community of people, and we're not exactly churning PL experts out of colleges. These days the intro to AI will be waitlisted, but intro to compilers will be sending out e-mails reminding students the course still exists. And it's not like there are a lot of paid positions for PL devs anyway. If you want to work on a language you can find jobs at Apple, Google, Microsoft, etc., but if you want to work on your own idea then there's not a lot of money to be had. A couple have gotten lucky with startup capital (Eve, Dark, Enso), others have gotten corporate patronage (Elm), and others have gotten user patronage (Zig). But I don't know how deep those dollars go, and how many languages they can support. I'm not sure but I have a feeling it's not thousands of languages.
- deleted 5y ago[deleted]
- Verdex 5y agoThe way that I think about it is in terms of N-dimensional spheres. https://en.wikipedia.org/wiki/Volume_of_an_n-ball https://en.wikipedia.org/wiki/Volume_of_an_n-ball If you checkout the formulas there, you may notice that as the number of dimensions of the sphere increase, then the greater amount of "volume" of the sphere ends up right next to the surface of the sphere. For high dimensional spheres, the majority of "volume" is right at the edge of the sphere. Or poetically, The further you swim into the ocean the deeper the water gets. So, my metaphor is that if you have a field which has many different orthogonal aspects (like programming does) then the beginners (living in the exact center of the sphere) will have a relatively shallow space to swim around in. This experience can be understood and optimized. However, the further you get from the center, the greater the possible volume of space that you have to explore. At the very beginning of a programming journey you're swimming in a puddle, but at the end you're swimming in a gas giant. I suspect that there's so much space in programming alone (not even counting software engineering) that each individual programmer on earth has the opportunity to end up in a unique ocean. Coming up with any guidelines for THAT feels like a failing venture. Although that didn't stop me from trying. You'll notice that there isn't actually any way for us to describe bad code. We've just got best practices and code smells. Best practices just being "someone else was successful once and also doing this" and code smells being "this code makes my tummy feel bad ... no I can't quantify that". I think I've got a metric that can explain why code is bad regardless of language and domain. Although there's still a lot of work to do. Also, this is only one aspect of what you would need to do in order to design a powerful programming language for experts. I suspect we're currently in the very beginning of an effort that's going to take easily a hundred years (at least) for humanity to figure out.
- giovannibonetti 5y ago> Tools that sacrifice the learning curve to make them more powerful and better at managing complexity? That's the value proposition of Haskell, as far as I can tell. Lisp might be a more powerful language, but it doesn't help so much in managing complexity. Haskell's type system is arguably the best at tackling complex systems, but the learning curve is tough.