I enjoyed my work with Scheme, having received my instruction in the early 2000s. I'm not a functional language or lisp language advocate in any way, and I don't even dislike Python for professional work, but I do regret that it is not taught anymore: Python's management of scopes is not as good for the instruction.
Readit NewsDeleted Comment
fdr commented on Simply Scheme: Introducing Computer Science (1999) people.eecs.berkeley.edu/... · Posted by u/AlexeyBrin
Deleted Comment
fdr commented on Silver plunges 30% in worst day since 1980, gold tumbles cnbc.com/2026/01/30/silve... · Posted by u/pera
Silver has plenty of industrial uses. Very little has changed in industry to cause demand or supply shifts to match the massive price swings. Thus a lot of this is probably meme investors gambling
Fun fact about silver, besides its heavy industrial footprint, which you mentioned: the supply is dominated by Mexico. There have been some, uh, erratic words about Mexico from the people in the position to affect trade policy and foreign policy.
fdr commented on IPv6 is not insecure because it lacks a NAT johnmaguire.me/blog/ipv6-... · Posted by u/johnmaguire
For those of you with this handy technology, the mobile phone, in the United States: you have an IPv6 address without NAT. Some of you even exist on a network using 464XLAT to tunnel IPv4 in IPV6, because it's a pure IPV6 network (T-Mobile). These mobile phone providers do not let the gazillion consumer smartphones act as servers for obvious reasons.
This is all to underscore the author's point: NAT may necessitate stateful tracking, but firewalls without translation has been deployed at massive scale for one of the most numerous types of device in existence.
> but some others will pick up where he left off, with more modest goals
Already happening :-) https://github.com/Dicklesworthstone/beads_rust
the main area I'd like to see some departure from beads is to use markdown files (or something) to be able to see the issue context/comments better in a diff generated by git.
The other area I'd like to see some software engineering thinking that's more open ended is on regression testing: ways of storing or referencing old versions of texts to see if the agent can complete old transformations properly even with a context change that patches up a weakness in a transformation that is desirable. This is tricky as it interacts with something essential in software engineering, the ability to run test suites and responding to the outcome. I don't think we know yet when to apply what fidelity of testing, e.g. one-shot on snippets versus a more realistic test based on git worktrees.
This is not something you'd want for every context, but a lot of my effort is spent building up prompt fragments to normalize and clean up the code coming out of a model that did some ad-hoc work that meets the test coverage bar, which constrains it decently into having achieved "something." Kind of like a prototype. But often, a lot of ungratifying massaging is required to even cover the annoying but not dangerous tics of the LLM, to bring clarity to where it wrote, well, very bad and unprincipled code...as it does sometimes.
To be fair, he's always been a little loopy. At least, I think this post of his was loopy: https://steve-yegge.blogspot.com/2007/06/that-old-marshmallo...
It was also one of my favorite posts of his and has aged incredibly well as my experience has grown.
that's one reason I am less worried about him than some, although, I don't want to say that only to have something bad happen to him, that is, a form of complacency. Just because (say) Boltzmann and Cantor had useful insights along the way didn't mean people shouldn't have been looking to support them.
I use beads quite a bit, but not as steve intended. And definitely the opposite of "Gas Town," where I use the note-taking capability and integration with Git (that is, as something of a glorified Makefile and database) to debug contexts, to close the loop and increase accuracy over time. Nevertheless, it has been useful for large batch runs over my code base: the record has been processing for thirty hours straight while getting something useful, and enough trace data to make further improvements.
Steve has gone "a bit" loopy, in a (so far) self aware manner, but he has some kind of insight into the software engineering process, I think. Yet, I predict beads will break under the weight of no-supervision eventually if he keeps churning it, but some others will pick up where he left off, with more modest goals. He did, to his credit, kill off several generations of project before this one in a similar category.
When people talk about inflation, I don't think they're referring to just CPI, but asset inflation too. Things like equities, real estate, gold/silver/platinum, bitcoin, etc.
These have been outpacing CPI because they're levered by cheap debt, brought to you by central bank actions that keep rates low so governments can play the same levered games with their own runaway fiscal policies.
That's a lot of financial devices painted with a broad brush, and I think the charge that so may central banks are knuckled under with fiscal dominance is simply not sustainable. The ones that are, we tend to hear about.
Because there's a lot one could write about each of: equities, real estate, gold, silver, platinum (which have very different industrial exposures), and bitcoin, which have many price drivers.
So let's try something more parsimonious: what do you make of people, institutions, etc that bid on short and even long-dated sovereign debt around the globe, and come up the collective discovered price of, say...3.5%, annualized, for maturity in a month? https://www.treasurydirect.gov/auctions/announcements-data-r...
Taking your example in good faith: Gold is four times as expensive today as it was at this time in 2015. Has food seen a 4x increase? No, right? So gold is volatile on a level way beyond inflation. QED.
Are CPI measurements difficult? Sure. It takes a bunch of expert eggheads and a lot of shouting to come to consensus. Still better than trusting some kind of magical commodity market to tell you.
You don't even need to trust CPI alone when looking in history, where things have evened out a bit: we have historical short-term bond yield data, even the yield curve: people bidding on short periods with the safest debtor expecting changes in nominal value.
Not to suggest CPI is redundant, there's a reason why central bankers read it after all. For one, it's the most timely data they have. But it's impossible to nudge it year after year -- accumulative error -- without it become obviously decoupled from other data, including the long-term bond market data. It just so happens commodities are the wrong yardstick.