skchrko

- What's your job?
- 38:12

[skchrko @skchrko]

I can already tell you what's going to happen to all those extra cycles that faster hardware is going to give us in the next hundred years. They're nearly all going to be wasted.

Graham, The Hundred-Year Language.

[Anna Riedl @AnnaLeptikon]

"Everything not saved will be lost."

— Nintendo Quit-Screen Message

[skchrko @skchrko]

https://t.co/WxOkHp6Lw9

[Racket (& Rhombus) @racketlang]

A language that is easy to learn and use and uniquely customizable?

https://t.co/PK2ZXgaCFr

[Vivian Plasencia @ViviPlasenciaC]

I also wrote a new article on one application of LeanIMT+: privacy-preserving revocation for verifiable credentials using zero-knowledge non-membership proofs.

The idea: verifiers can check that a credential has not been revoked without learning which credential is being presented or contacting the issuer.

This preserves privacy, anonymity, and unlinkability while supporting efficient revocation.

Article link: https://t.co/rj22YecPT2

[skchrko @skchrko]

@adamnemecek1 @NathanFlurry It's more about learning curve. Typst is definitely easier to grasp than LaTeX. At the same time, you can't ignore momentum. Some journals require you to use the specific LaTeX template for their articles, for example. So, for collaboration typst is usually not the 1st choice

[skchrko @skchrko]

@adamnemecek1 @NathanFlurry Things like markdown being the most popular format for sharing formatted text nowadays. Working on knowledge arifacts is not always a single-player game, after all. And for the cases where you need a proper layout there is TeX, so typst has that strange niche in between.

[skchrko @skchrko]

@adamnemecek1 @NathanFlurry It can be better for some niche uses, but in general it’s not close due to things like https://t.co/Qdkdthla62.

[Anatoly Karp @akarp]

Guys be like “I know a place”

The place:

[Joran Dirk Greef @jorandirkgreef]

It’s 2026.

Do you understand and have an engineer independently review your code (apart from autonomous testing)?

Do you agree that critical code should be simple, a pleasure for generations to read and maintain?

I guess what I am asking is:

Are you https://t.co/UFV4aBIgpe?

[Mitchell Hashimoto @mitchellh]

Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).

If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!

I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.

Feeling pretty swell about this mentality with all the supply chain attacks happening.

[KC Sivaramakrishnan @kc_srk]

"Machine Learning in OxCaml" by Mark Elvers

https://t.co/LzVXp4k0uA

Mark is quietly putting the rest of us to shame by hacking on wildly diverse things and, more importantly, writing about them consistently! See https://t.co/6qE5oupKBJ

[Prof. Brian Keating @Briankeating]

What's the shortest definition of Kolmogorov complexity?

[Dominik Tornow @DominikTornow]

Joe Hellerstein (@joe_hellerstein) cuts to the core of coordination:

What Is Coordination, Really?

Coordination is the machinery a system needs when correctness depends on excluding futures that might otherwise still occur.

[clem 🤗 @ClementDelangue]

"But here is what we found when we tested: We took the specific vulnerabilities Anthropic showcases in their announcement, isolated the relevant code, and ran them through small, cheap, open-weights models. Those models recovered much of the same analysis. Eight out of eight models detected Mythos's flagship FreeBSD exploit, including one with only 3.6 billion active parameters costing $0.11 per million tokens. A 5.1B-active open model recovered the core chain of the 27-year-old OpenBSD bug." https://t.co/yBTiiMq1Xy

[skchrko @skchrko]

And fuzzing.

[David K 🎹 @DavidKPiano]

More developers should learn about property-based and model-based testing

Unit, integration, E2E tests are fine for "this should work" but are usually not good enough to test "this should never happen"

[skchrko @skchrko]

A friend of mine learns Chinese and built an app to help with memorization.

[Sherzod @sherzod_v]

Packed HSK vocab into 15-word groups and built an app to drill them. HSK Elementary = 67 groups.

• Ready groups by HSK level
• Writing & pinyin drills separately
• Stats + spaced repetition
• Smooth sessions + smart hints

https://t.co/7E8bsHcgCM

[Dominik Tornow @DominikTornow]

Found the formal roots for durable execution semantics in a 1977 technical report: trace theory

A Mazurkiewicz trace is an equivalence class of traces that share a causal structure but differ in how concurrent ops are ordered

Deterministic replay = same equivalence class

[Yaron (Ron) Minsky @yminsky]

This is a fairly wild post about OxCaml Labs from @avsm. It's hard to summarize the stuff they're doing, but, some examples:
- Some wild vibecoding
- A formal semantics for package managers
- A decade of docker containers (including OxCaml!?!)

[neural oscillator of uncertain significance @mycoliza]

if you have been personally victimized by bhyve’s lack of nested virt, you may be entitled to compensation! see here for more information: https://t.co/2XjsyquZKu