3 ms·
> PG’s “blub” thesis is particularly terrible, even for him. How do you tell what your language is missing? That's a real issue. If you ask people, they usuall
by Animats 4y ago
> PG’s “blub” thesis is particularly terrible, even for him.
How do you tell what your language is missing? That's a real issue. If you ask people, they usually ask for incremental improvements.
Useful directions for work:
- Much of programming today is hooking thing A up to things B, C, and D. All have constraints. Are they properly satisfied? How do you tell? Secondary problem: If they don't quite connect, and you can't change them, can you bash them into connecting? Type theorists work on the first of those two issues, but usually ignore the second.
- Much software is plumbing plus algorithms. Classically, algorithms were the center of attention. But today, most of the algorithms are off the shelf, while each system has unique plumbing. Should languages be plumbing-first? Attempts in this direction (modules, APIs, CORBA, XML schemas, JSON schemas, REST, etc.) have usually assumed a master-slave relationship, where one side defines an interface and the other struggles to match it. Is a symmetrical approach possible?
- You can have all the CPUs you want, but they're not going to speed up much. We've been at 3-4 GHz for well over a decade now. Parallelism in languages has improved quite a bit, but it's improved from "it's not the language's problem" to "we have some reasonable primitives now". Not to "as easy as sequential".
- Why does the complexity of web pages seem to grow without bound, despite them not doing
all that much more?
- When it really, really needs to work right, software isn't that good. Even for small programs. Consider Solidity and the track record of smart contract hacks.
- Some things don't need to be Turing-complete. We don't have good ways to make them. Older technologies, such as ladder diagrams, decision tables, and simple regular expressions, have fallen out of favor. Some of those are exhaustively testable, which is useful.
- pdimitar 4y ago> - You can have all the CPUs you want, but they're not going to speed up much. We've been at 3-4 GHz for well over a decade now. Parallelism in languages has improved quite a bit, but it's improved from "it's not the language's problem" to "we have some reasonable primitives now". Not to "as easy as sequential". Mostly correct but there are exceptions: Erlang/Elixir and Golang in particular make concurrent and parallel code extremely easy to write and 99% of what can go wrong is already taken care of for you. Rust makes pretty good strides as well, and OCaml 5.0, once stabilized, promises to give you an ML language with GC memory management and very good parallel primitives that its community will likely quickly develop further. It's super strange to me that most programmers actually refuse to acknowledge that there is such a thing as the right tool for the job (not talking about you, you obviously are more open-minded, judging by your comment). That seems to be the bane of the modern programming -- the people and their bias. A lot of us became wannabe council of elders. And I completely agree that non-Turing-complete technologies are extremely useful. I've been preaching for a configuration language that deliberately omits several important things (like passing functions around or recursion) so you can never hack a system through a malicious config. Alas it seems nobody cares until I sit down and write it... > - Why does the complexity of web pages seem to grow without bound, despite them not doing all that much more? Sigh. I'd like to know as well. Likely the newer generation are a bit spoiled and feel they can pile complexity on top of other complexity forever? Or, much more likely, nobody sticks around for a long time in their workplace and they are like "frak that, the next guy is gonna fix it"? Who knows. But it's indeed severely not okay.
- sidlls 4y agoIf the “blub” thesis were merely about choosing the right tool for the right job I’d agree with you (I think). But that isn’t his thesis. His thesis is that not choosing the language PG would choose (most likely, a lisp) means a programmer is a bit gormless. The entire point of that essay was a giant broadside ad hominem against a huge population of programmers and engineers.