Honest question, how do you discover interesting content over this protocol?
Is there people building the equivalent to web directories and web rings? Or search engines? What are the cultural expectations on navigating other people's published resources?
Meanwhile, I've heard that very argument every time some official organisation makes a proposal to regulate the market to limit the dominance of some dominant players. Those distorting the market in their favour will oppose any regulation that reduces their power by bemoaning how it will limit consumer's choice.
The article says 'abundance'. The point you make that having choices is a requisite for freedom, but truth is that freedom comes from meaningful choices, not an abundance of them.
You have a myriad of artificially created choices that amount to more or less the same outcome; think of a supermarket, where all products are the same high-processed food and imported vegetables. Freedom would be having a competing family-owned local shop with proximity products.
To have meaningful choice, you cannot depend of having a single homogeneous environment providing all the choices you can make; this can come from having healthy competition, or sometimes by you creating your own choices when there were none.
I think one important point in the article is being unnoticed: these special highlights would not be the default for reading code, but specific tools that the developer can turn on and off for when their use case is needed.
So, not much different than a search for regular expressions or a "show definition" tooltip
Open-source has many technical advantages over closed-source, in addition to the moral ones (which are quite powerful themselves).
Being able to inspect the software you use makes you able to trust house it works, and fix it at points where it's not working; those were the first motivators for creating the FLOSS movement.
There's also the advantage that in the long term you don't depend on the company developing the software; if the company goes under, or simply stops supporting the software, you can hire a different batch of developers to carry on maintaining it. That's the reason why many big contracts require that the software vendor puts the source code under escrow.
In reality, closing the source of software only benefits the seller; everybody else benefits from having it available. With FLOSS, you get that for free.
It took several environment-changing events to get our unique kind of intelligence; mammals had to thrive in place of saurs; and then, Africa needed to be split by the Rift and to create the dry savannah.
This forced some apes to climb down the trees and depend on a diet of scavenging for meat, which happened to both increase brain size AND require improved intellect to survive, forcing the evolution of our hypertrophied symbolic brain.
Had this not happened however, other intelligent species could have filled the niche. There's no shortage of other intelligent species in our planet, not just other mammals but octopus and some birds. And then you get hive intelligence, which could equally be forced to evolve into a high problem-solving organism.
I prefer the name given in mathematical optimization, which is Constraints Satisfaction Problems; instead of using an imprecise physics metaphor, it gets a descriptive logical term of what's going on.
In CSPs, each cell is a 'decision variable' with a 'domain' of values, which get pruned by 'constraints' that propagate to values invalidated by the decisions made in the connected variables, until the whole 'problem' gets into either a solution which 'satisfies' all the constraints, or a contradictory state where a variable's domain is empty, causing the algorithm to backtrack.
CSPs have the advantage of having clear and efficient methods to go back to a previous state and keep exploring every alternate possibility, rather than having to restart from the beginning. The article hints at that possibility ('saving checkpoints' or'reverse the collapsing of a cell'); there's a whole field of study dedicated on the best ways to do that on a large scale for very general problems.
Boris the brave coined the term "Constraint Based Tile Generators" (CBTG) [0], which is a specialization of the more general CSPs to this particular domain.
Personally, I find CSPs overly general and mired in esoteric, byzantine terminology. It's a large cognitive load to put on people to run through the glossary of terms just to talk about the problem set up. I don't think the quantum mechanic analogy is great but I can see it being much more intuitive than the obscure language of CSPs.
Surely the 'solving' part of CSPs may be obscure, but the basic concept can be readily explained with the metaphor of crosswords and sudoku (both are very direct instances of CSPs); there's not much obscurity to that. In fact, the article resorts to that same metaphor to explain with precision what the 'waveform' metaphor couldn't.
Of course terminology for CSPs will get confusing when you get to represent them mathematically; but that happens to anything that you turn into math. The core concept is quite familiar and intuitive.
Is there people building the equivalent to web directories and web rings? Or search engines? What are the cultural expectations on navigating other people's published resources?
reply