Look it up: https://pijul.org
It also makes cherrypicking and rebasing wayyyy easier. You can actually add or remove any set of patches, at any time, on any peer. It's a dramatic model shift -- and is awesome.
3,057 karma · joined May 5, 2012
https://invisible.college/@toomim
https://braid.org
Look it up: https://pijul.org
It also makes cherrypicking and rebasing wayyyy easier. You can actually add or remove any set of patches, at any time, on any peer. It's a dramatic model shift -- and is awesome.
- The original 1977 version control system, SCCS, was a CRDT: https://braid.org/meeting-60/sccs-is-a-time-collapse
- It called its data structure a 'weave"
- Brahm's old project "Codeville" used a weave for version control
- But then git blew up in popularity.
- The project "DARCS" tried to make a robust "theory of patches," and eventually led to the development of Pijul
- Pijul is a VCS that is a CRDT: https://pijul.orgSeattle is the worst. They call it the "seattle freeze." The San Francisco Bay Area became almost as bad in covid.
The south is still friendly. Austin is incredibly friendly with strangers. Miami has strong stranger vibe. NYC is still alive, too.
The antimatter algorithm allows peers to learn where the rest of the network has caught up to, without a central actor, or relying on consensus, across arbitrary P2P connection & disconnection events in the network. It even allows subnetworks, after a partition, to prune the history that they generate while partitioned, while still holding onto the necessary older history to reconnect with the other half of the partition.
The more general definition of "constitution" is "that which constitutes" a thing. The composition of it.
If Claude has an ego, with values, ethics, and beliefs of an etymological origin, then it makes sense to write those all down as the the "constitution" of the ego — the stuff that it constitutes.
But one issue: it's not actually the case that "all CRDTs are OTs".
OT is the feature of Transforming and Operation. This requires two things: (1) Operations, and (2) Transforming them so that they do the same thing when applied from one place in distributed time vs. another place in distributed time.
However, there are plenty of CRDTs that (a) do not have operations, and also plenty of CRDTs that (b) do not transform operations.
Consider a typical state-based CRDT like LWW register. It does not have operations; it just has a current state: the value of the register. And it does not transform operations. It just always computes the current value of the register.
(For more on the relationship between OT and CRDT, see my notes at braid.org/meeting-111.)
https://invisible.college/toomim/toomim-linked-editing.pdf
> Abstractions can be costly, and it is often in a programmer’s best interest to leave code duplicated instead. Specifically, we have identified the following general costs of abstraction that lead programmers to duplicate code (supported by a literature survey, programmer interviews, and our own analysis). These costs apply to any abstraction mechanism based on named, parameterized definitions and uses, regardless of the language.
> 1. *Too much work to create.* In order to create a new programming abstraction from duplicated code, the programmer has to analyze the clones’ similarities and differences, research their uses in the context of the program, and design a name and sequence of named parameters that account for present and future instantiations and represent a meaningful “design concept” in the system. This research and reasoning is thought-intensive and time-consuming.
> 2. *Too much overhead after creation.* Each new programming abstraction adds textual and cognitive overhead: the abstraction’s interface must be declared, maintained, and kept consistent, and the program logic (now decoupled) must be traced through additional interfaces and locations to be understood and managed. In a case study, Balazinska et. al reported that the removal of clones from the JDK source code actually increased its overall size [4].
> 3. *Too hard to change.* It is hard to modify the structure of highly-abstracted code. Doing so requires changing abstraction definitions and all of their uses, and often necessitates re-ordering inheritance hierarchies and other restructuring, requiring a new round of testing to ensure correctness. Programmers may duplicate code instead of restructuring existing abstractions, or in order to reduce the risk of restructuring in the future.
> 4. *Too hard to understand.* Some instances of duplicated code are particularly difficult to abstract cleanly, e.g. because they have a complex set of differences to parameterize or do not represent a clear design concept in the system. Furthermore, abstractions themselves are cognitively difficult. To quote Green & Blackwell: “Thinking in abstract terms is difficult: it comes late in children, it comes late to adults as they learn a new domain of knowledge, and it comes late within any given discipline.” [20]
> 5. *Impossible to express.* A language might not support direct abstraction of some types of clones: for instance those differing only by types (float vs. double) or keywords (if vs. while) in Java. Or, organizational issues may prevent refactoring: the code may be fragile, “frozen”, private, performance-critical, affect a standardized interface, or introduce illegal binary couplings between modules [41].
> Programmers are stuck between a rock and hard place. Traditional abstractions can be too costly, causing rational programmers to duplicate code instead—but such code is viscous and prone to inconsistencies. Programmers need a flexible, lightweight tool to complement their other options.
For anyone interested in this topic, I'm publishing a new theory on this called Collapsing Time Machines: https://braid.org/meeting-111.
Brendan Eich was the Director of Mozilla. This is the guy who invented Javascript in 10 days, at Netscape, and then co-founded Mozilla, and became the technical lead. He was Chief Architect of Mozilla, then CTO of Mozilla Corporation, then CEO. He made Firefox great. This was when Mozilla was in its heyday, and passed IE in marketshare.
Then he was fired in 2014 because a bunch of people went crazy that he made a $1,000 political donation for a California ballot proposition that had nothing to do with computers.
This sent a signal that Mozilla doesn't reward technical improvements to its software — it rewards following political trends.
All of the bad stuff in Firefox started then.
HTTP/2 and HTTP/3 are binary protocols. And if you replace the JSON with CBOR, then even the payload becomes binary.
The reason for using HTTP is that the semantics are right. HTTP is a state transfer protocol, and ultimately, that's 90% of what you need for sync.
The other 10% is for subscriptions, updates, with versioning, and patches. You can get these by adding the Braid extensions (see braid.org) which upgrade HTTP from a state transfer to a state synchronization protocol. (I work on Braid.)
Yeah. When he said "Just sayin'", that was his cue for sarcasm.
You're leaving out the context of Ms Rachel. Charlie is saying everything in response to her.
Let me go into extra detail here to explain what I think he meant:
"Ms Rachel is saying that she acts like this because God said 'Love your Neighbor,' and is acting as if that law is so important that we should always adopt the preferred pronouns of people around us. However, the best way to love your neighbor is to tell them the truth, and tell them what sex they are, rather than upholding their preferred pronouns, which I see as untrue to their sex. Secondly, one should not take these Mosaic laws from Leviticus as literal rules for modern day Christians to follow. Christ + his Apostles said that these Mosaic laws were applicable to the Jews (the direct descendents of Israel) in a covenant between them and God, which were only necessary before he arrived as Messiah, and now that he is there, he is fulfilling that covenant for all people, and the gentiles who convert to Christianity do not need to follow the Mosaic laws literally, but rather follow their moral intent as he teaches. Thus, if Ms Rachel really wants to take these laws so literally... she should look in the previous chapter where it says that gays should be stoned to death. I don't think that she would agree with stoning gays to death. So it's hypocritical of her to take these laws so literally."
----
Christian Context (from AI):
After Jesus’ resurrection, the early church—initially Jewish—grappled with whether Gentile (non-Jewish) converts needed to follow the Mosaic Law. This led to the pivotal Jerusalem Council (Acts 15, ~50 CE), where apostles like Peter and Paul decided:
- Gentiles were not required to follow Levitical laws like circumcision or kosher diets.
- They were asked to follow basic moral guidelines (e.g., avoiding idolatry, sexual immorality) to maintain fellowship with Jewish Christians.
Paul’s letters further clarify this shift:
- In Galatians 3:23-25, he describes the law as a “guardian” until Christ came, after which faith in Jesus supersedes the law’s role.
- In Romans 10:4, he says Christ is the “culmination of the law” for those who believe.
- However, moral principles (e.g., loving your neighbor, Leviticus 19:18) remain binding, as they’re reaffirmed in the New Testament (Romans 13:8-10).
----
^ So that's why "Love your neighbor" is still valid in Christianity, but stoning gays is not. This was decided in the Jerusalem Council, which all modern Christian sects inherit from. Charlie was using "stoning gays" as an example of something modern Christians do NOT believe in, even though it was a law of Moses, and is written in Leviticus.
He did not say that.
Again, Christians do not follow Leviticus. I'm not a Christian, but I just looked this up:
> Mainstream Christian theology holds that Jesus Christ's life, death, and resurrection fulfilled the ceremonial and civil aspects of the Leviticus laws, making them no longer obligatory for believers, while the moral principles are reaffirmed and expanded in the New Testament under what is often called the "law of Christ."
You seem to think Charlie wants to stone gays because he's a Christian, and you're assuming that Christianity believes in stoning gays. But that last part is false. Christ revised the old testament. Charlie's making a point that you can't just take Leviticus at face value, and interpret its passages out of context from the new testament.
You're now interpreting Charlie's point to mean the opposite of what he meant. You're assuming that he actually wants to stone gays, because he's pointing out that the old testament talks about it, and because you don't understand Christianity.
Full clip: https://www.youtube.com/watch?v=CceJpiUPgPU
Again, I'm not a Christian, and I myself appreciate gayness. But we have to stop taking clips out of context and framing people as evil to justify political violence.
Yet you're seeing the opposite — after the killing of a conservative, it's the left that says violence is justified.
Furthermore, this trend on the left had been building for a while, which we see in surveys done before his killing:
No, arguing against cherry-picking does not mean you endorse everything. In the third link, it says that Christians do not follow Leviticus. Charlie was no different. He loved and supported gay people and welcomed them into his movement. There are many gays in his organization, at high levels. To assume that he wanted them stoned to death is absurd, and incredibly ignorant.
Here's Charlie on Gay People: https://youtu.be/N14ywRyTWVI?si=AQzLU_6TBNwSDGEr&t=942
But as for "causing" violence, they also asked whether "political violence is ever justified", and the difference between left vs. right there was even more — 25% vs 3%.
In truth, he's more of a political nutcase than a political activist.
> We included individuals whose public exposure occurred between 1948 and 2018.
The last 8 years of politics have been very very abnormal. And in today's data, the "very liberal" approve of political violence at a rate of 24% vs. 3% for the "very conservative":
https://today.yougov.com/politics/articles/52960-charlie-kir...
This ^^^ is the troubling statistic, and there's a 7x difference between the left and the right.
https://x.com/StephenKing/status/1966474125616013664
https://www.youtube.com/watch?v=y-dMa3rIcjY
https://youtu.be/1pteZE5FpNc?si=UG2jJZovGldIJKJ0&t=1559
This has the effect of whipping up political anger and violence against people based on false pretenses. You are an embodiment of the problem.
Casualties are a sad fact of war. But it's not genocide because Israel's doing everything it can to save the civilians while combatting Hamas. If genocide was defined by the number of deaths, would you say that the US was genocidal against germany during WW2? We killed 3 million civilians to defeat the Nazis.
Good luck in your bubble.
For instance, he ignores that Israel goes out of its way to warn civilians before attacking, and provides aid to civilians. He ignores that Israel could simply kill ALL the civilians with a bunch of bombs if its intent was actually genocide, and yet it has not.
This is not a serious debate. Israel is not genociding. If you disagree, you need to respond to the actual arguments. But nobody on the other side is doing so, because they can't, because Israel is not genociding.
Please think about this.