C# did not ship with async/await, and Java didn't have virtual threads back then. I am specifically referring to the initial choices made in C#'s foundation.
The mystery of why .NET got so many things right is simply that C# was built several years later by the exact same Microsoft engineers who had previously worked on extending Java, giving them a perfect blank slate to fix the architectural flaws they had already encountered
Let’s look at the actual historical record, because the pattern is undeniable: the root cause of this conflict is the absolute refusal of the regional and local leadership to ever accept a sovereign Jewish state within any borders.
In 1937 and 1947, the Jewish community accepted partition, but the local leaders rejected it and chose war.
Following the Six-Day War in 1967, the Arab League shut down any path to compromise by issuing its 'Three No's': no peace, no recognition, and no negotiations.
Decades later, Israel engaged in direct talks at Madrid in 1991 and made massive concessions under the 1993 Oslo Accords to establish the Palestinian Authority, only for the process to be dismantled by waves of suicide bombings.
At Camp David in 2000 and the Taba Summit in 2001, Israel offered an independent state encompassing Gaza and over 90% of the West Bank, but their leadership walked away to launch the Second Intifada.
When the Arab League proposed a plan in 2002, they conditioned it on non-negotiable terms regarding refugees and borders that compromised Israeli security, while Palestinian factions rejected the deal entirely regardless.
In 2003, Israel accepted the international Roadmap for Peace, but the process stalled permanently because the local government failed to fulfill its basic obligation to dismantle terrorist infrastructure.
In 2005, in a one-sided prayer for peace, Israel completely dismantled every single settlement in Gaza, dragged out its own citizens by force, withdrew every soldier, and handed the entire territory over to Palestinian custody.
In 2008, Israel proposed its most sweeping offer yet, including near-total territorial withdrawal and international administration of holy sites, which Mahmoud Abbas flatly refused to sign without any counteroffer.
You cannot blame Israel for a lack of effort when it has repeatedly offered statehood and land for peace. While the West labels Hamas as an extremist group, the reality on the ground is that they are viewed by a vast number of Palestinians as a mainstream governance structure and a legitimate movement of armed resistance against occupation. The true obstacle to peace remains this foundational objective, which Hamas champions and the local political culture reinforces, to establish an Islamic state over the entirety of the land and eliminate Israel entirely. If at any point there is a Palestinian majority and a leadership that genuinely seeks peace, it will happen in a second, despite whatever imperfections Israel may have.
Hi, thanks! I appreciate your input and generally agree. The TDS article wasn't really aimed at the HN crowd, but it did help a bit with the more general audience.
I do plan to also develop an interactive guide that breaks down post-rotation quantization fundamentals in a more educational, hands-on way.
TurboQuant is a recent paper from Google and NYU that has gained massive traction in mainstream media and the AI community. As implementations of TurboQuant are integrated into various popular projects, it is important to note its relation to EDEN quantization.
TurboQuant is essentially a partial implementation of EDEN quantization (first work published in NeurIPS 2021, extention published on ICML 2022). The few differences that do exist make EDEN significantly better.
In the vLLM documentation quoted above, TurboQuant (which is a restricted version of EDEN) is referred to as a specific case of HIGGS. Note the symmetry: EDEN acts as a special case of HIGGS; hence, HIGGS functions as a generalization of EDEN.
In any case, the quantizer is indeed an extension, regardless of whether it was explicitly framed that way in the paper. I say this not to diminish their contribution at all, but just to clarify the relationship, as it was also stated in the vLLM doc.
Thanks for the pushback, and I appreciate the reference to classical information theory.
While I probably overstated things by using the very general phrase "taking advantage," I want to be very precise about the claim, as I believe these works are foundational to quantization, beyond the scope of deep learning. The mechanism of applying a deterministic biased quantizer, such as Lloyd-Max, to the induced post-rotation distribution, alongside mathematically correcting its inherent bias, is a distinct contribution (which asymptotically improves the worst-case error).
If there is a classical paper that utilizes such a combination, I would genuinely be very eager to review it. But to my knowledge, this was not introduced prior to DRIVE and EDEN.
It is worth noting that taking advantage of the post-rotation distribution was not actually done until DRIVE (2021), which was made possible via our proper scaling. Furthermore, applying a Lloyd-Max codebook post-rotation was introduced EDEN.
We consider these to be the foundational works in this regard.
Thanks for that!
Note that the residual chain is empirically and theoretically inferior to our unbiased scale; furthermore, it requires an additional bit in certain cases.
Additionally, TurboQuant was not the first to apply EDEN to KV-cache (see for example https://arxiv.org/abs/2411.17525 from 2024).
I believe our claim at this point is more fundamental than just lack of citation.
The quantizer in TurboQuant is EDEN quantization (2021) applied to the KV-cache. It is neither a novel quantizer nor an improvement in quantization techniques.
In DRIVE/EDEN, we already introduced the version used in "TurboQuant"'s paper and suggested an optimal scale configurations which are better in both mse-minimizing and unbiased scenarios.
When you use TurboQuant, you are essentially using the EDEN quantizer under a different name applied to KV-cache.
Both EDEN and its 1-bit variant have been implemented in PyTorch, JAX, and TensorFlow across numerous open-source libraries and are used in various applications. I am currently writing a blog post that will document these in detail.
EDEN defines a scale parameter, S, for which we suggest specific optimal values for both biased and unbiased versions. As shown in the note I shared, these values lead to clear empirical improvements. Consequently, users who rely on the less optimal S value and the unbiasing method popularized by TurboQuant will generally see inferior results compared to those using EDEN with the optimal scale values suggested in our original papers.