Native-GUI distributed system in a tweet
blog.metaobject.com
blog.metaobject.com
Conversely, I see Objective-S as just a batteries-included, insanely high level declarative language. How is that any less of a DSL, per the creator's logic?
Plus, saying that your language is the "first [real] general purpose language" is a bit smug.
To start, I think DSLs for algorithms is a bit off; it's more like DSLs for manual memory management. But I think the significant thing is that those languages are closer to a natural way of speaking about the "execution environment" of a computer vs that of human thought, which is essentially the gap or spectrum which programming languages attempt to span.
And it makes a certain kind of sense to talk about generality of languages in terms of the set of human thoughts which they are effectively applicable to realizing. But this is very much against intuition when speaking of the generality of abstract structures since there are common, specific meanings in connection within them, and in computing that's typically what's meant. But, if you do look at it in the other sense, something higher level is going to have higher generality than something lower level.
Just playing devil's advocate 'cause I was curious where they might be coming from with it (because it sounds like such nonsense at first).
I choose unorthodox and provocative ideas over conservative bore of docile academic terms any day.
You call it being smug, I call it scientific confidence needed for progress.
(D and Nim immediately come to mind)
Marketing drivel. You choose marketing drivel over science. That's how I read that sentence.
It is a profound insight.
It might be a wrong profound insight, but "drivel" it ain't.
I suppose it would be using Rebol widgets though instead of native widgets, but that also means it'll work cross-platform with no changes.
The reasoning is given. How is the reasoning incorrect, other than colliding with beliefs and assumptions we make that are so implicit we don't even see them?
But very briefly: ALGOL.
> How is that any less of a DSL, per the creator's logic?
Very simple, from a software-architectural POV: it includes call/return as one of the architectural styles it supports. But it also supports other architectural styles, ideally including building your own, though that is still a bit thin. So n = 1, vs n > 1.
See also: https://blog.metaobject.com/2019/02/why-architecture-oriente...
It’s an issue of terminology, I’d say - you’re using very sweeping, imprecise language to describe your critique. “This particular mechanism is a useful feature other languages lack” would be received much better than “other languages are fundamentally only suited to writing algorithms, rather than general-purpose software” when we’ve got 60+ years of every kind of software imaginable written in them. Arguing about the criteria for what “general purpose” means, this far down the line, is vastly less interesting than actual features, and I’ve read two blog posts and I still don’t really see, specifically, what Objective-S has that’s so paradigm shifting. Reprogrammable literals, so I can embed URLs in my code without delimiters or anything? Syntax for “connecting” things?
In what way is it not obvious? Here is something we need to express a lot, and our "general purpose languages" can't express it. I am not sure how it can get any more obvious than that.
The use of the word "express" is important here. Of course we can implement everything and anything once our language is Turing complete. But if that's the criterion, why do we have high level languages? After all, we surely can implement everything by punching machine code into our hex editors. Or maybe get super-fancy and add an assembler.
But we cannot express non-procedural concepts and systems, and we cannot abstract our way out of this problem the way we otherwise often can because it is the abstraction mechanism itself that is procedural.
> What about when I’m plumbing stuff between APIs and databases?
Exactly! That was precisely the use case where this became obvious to me, because in Wunderlist, for example, our iOS/macOS GUI clients were on the order of 140KLOC, and a large percentage was just plumbing, shuffling data between APIs, the persistence and the GUI.
So what do you actually do when you create this plumbing? You write procedures, functions or methods to accomplish the plumbing. To either or both (a) set up the plumbing and (b) mediate the plumbing. So you can implement the plumbing by writing all these procedures, but you can't actually express the idea of plumbing, because it isn't itself procedural. As Andrew Black puts it: "The program's text is a meta-description of the program behavior, and it is not always easy to infer the behavior from the meta-description." (https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.48...)
And the fact that (a) you can always kinda sorta get away with implementing what you need using procedures and (b) we have gotten so incredibly used to this that we don't see the indirection as a problem is exactly why I call this "The Gentle Tyranny of Call/Return".
And the mismatch and indirection have a very real and significant cost. For example, WL had a significant chunk of code that translated the REST API of the backend into a "nice" set of methods. With callbacks. Which had to duplicated every time we introduced an abstraction. Huge mess, huge amount of code, and I've seen the same in every comparable system I've encountered since.
With in-process REST, all that code goes out the window. It's not needed. Now you can make implement in-process REST using current languages, and we did. But it goes against the grain of what the language wants you to do.
> you’re using very sweeping, imprecise language to describe your critique.
Nah, the language is actually very precise, if apparently unfamiliar. That is something I obviously have to deal with, so thanks for the heads-up on that.
From a software-architectural POV it is blindingly obvious. For example here is a taxonomy of software architectural connectors:
https://www.researchgate.net/publication/3864292_Towards_a_t...
Call/return is in a tiny little corner. That is what our "general purpose" languages provide linguistic support for. Everything else we can build, but not express.
I think Java better fits the conventional notion of a general purpose language but it still feels a bit too much work to do simple things in a lot of cases.
Doesn't help that the author comes off as super defensive.
In other words, if we ignore syntax, what is the fundamentally new capability?
There hasn't been any fundamentally new capability since (pick your favourite):
1. the Turing Machine
2. the Lambda Calculus
3. the stored program computer
4. the NAND gate
No high level language has ever added any fundamentally new capability, everything it can do can be done in machine language. See also: compilers and interpreters.
High level languages are purely for human convenience, they exist in order to allow us to express what we want to accomplish in a straightforward manner. When the two don't match, we have an impedance mismatch, one of the most famous ones was using goto for control structures (https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...), solved by the introduction of structured programming.
Today we also have such an impedance mismatch, because most of what we do is no longer procedural in nature, but our means for expressing this are essentially procedural.
My last long-form attempt at explaining this was here:
https://2020.programming-conference.org/details/salon-2020-p...
For the domain of GUIs (one area where the mismatch is particularly painful and obvious), Stéphane Chatty did a much better job of explaining the problem than I did:
https://dl.ifip.org/db/conf/ehci/ehci2007/Chatty07.pdf
So the "new capability" in Objective-S is having linguistic support for architectural abstractions, so you can directly express components and connectors and their connections. Rather than just implementing them with procedures.
And GUI bindings are a good example (which I also talk about in my "Tyranny" paper): we can implement in current programming languages, but we generally cannot express them in the language.
That's... not clear at all to me. This seems like the kind of code that is fun to write, annoying to read, infuriating to debug.
The dataflow part where text flows into an S3 file is interesting, but it feels like as you get into corner cases that need more complex transformations with more potential bugs, the "just bind this value to its destination" syntax would quickly become cumbersome, and you'd want something closer to RxJS.
… this is not the compliment that you think it is