3 ms·
Isn’t this all on the same spectrum as all programming? Every programmer is using someone else’s code at all times. Even if you are writing in assembly, you are
by cortesoft 6y ago
Isn’t this all on the same spectrum as all programming? Every programmer is using someone else’s code at all times. Even if you are writing in assembly, you are still relying on a compiler to turn your written words into machine code.
- zabzonk 6y ago> Even if you are writing in assembly, you are still relying on a compiler to turn your written words into machine code. To nitpick, an assembler.
- erikpukinskis 6y agoIt's sort of a spectrum yes... (or, really, there are infinite spectrums like the one you are imagining,) But there are also discontinuities on all of those spectrums. The ergonomics of a declarative API are not continuous with the ergonomics of a procedural one. There's just a gap there which, when you cross it, you lose a bunch of things, and get a bunch of other things for free. There'a also a huge discontinuity when moving from code to point-n-click, which is what the article is about. Many of the affordances of code cannot be replicated in a GUI, with ANY amount of effort. And vice versa.
- jrochkind1 6y agoSure, you could consider it a spectrum, in terms of abstraction. So this article is focusing on things at one end of the spectrum I guess? I think though there are some qualitative differences between purely/mostly pictoral/icon/graphical environments and textual programming languages.