5,637 karma · joined August 30, 2017
Codeberg: https://codeberg.org/ashton314
GitHub: https://github.com/ashton314
Blog: https://lambdaland.org
Here’s a better link for Fira Sans: https://carrois.com/fira/
Also, if you have Fira Sans installed on your computer, you can use it in Slack with `/slackfont Fira Sans’
With the Artificial Inanity systems and the Rampant Orphan Botnet Ecologies (ROBE) beginning to spew tremendous amounts of crap (a technical term) onto the Ret, things are getting tricky for us ITA.
We need subject experts, not McKinsey consultants.
Turnstile relies on the fact that in Racket, you can have identifier macros [1] which can be expanded in pretty much any location (except binding, naturally). Racket is unique in this regard. Clojure has a mechanism to get roughly the same thing, but it's complicated. [2]
1: https://docs.racket-lang.org/guide/pattern-macros.html#%28pa...
2: https://lambdaland.org/files/2024_ecoop_type_tailoring.pdf
This is the gotcha: in stateful environments you'll have state-space explosion so big you'll have to come up with some compromising measure of "equivalent". You're right that that would constitute a proof by exhaustion of correctness. Unfortunately in practice it's entirely impractical.
For those curious, there are a lot of neat ways to implement choreographic programming! Choral uses a custom compiler which gives it very powerful analysis techniques. Some are libraries and have to rely more strongly on host language features to work. My library uses macros to embed the language directly into Elixir which gets you a bit of the advantages of both: https://github.com/utahplt/chorex
Quote:
You might say, “Well, if AI gets good enough and the product is the same, what’s the difference?” The difference is that the books aren’t the product. They aren’t the art--not completely. And this is the point. The most important thing to understand is that the process of creating art makes art of you.
My friends, let me repeat that. The book, the painting, the film script is not the only art. It’s important, but in a way it’s a receipt. It’s a diploma. The book you write, the painting you create, the music you compose is important and artistic, but it’s also a mark of proof that you have done the work to learn.
Because in the end of it all, you are the art.
I did a close reading of the implementation in the original miniKanren paper; you can see my write-up and implementation here: https://codeberg.org/ashton314/microKanren
miniKanren paper: http://webyrd.net/scheme-2013/papers/HemannMuKanren2013.pdf
Also relevant—a practical use-case for miniKanren: https://aphyr.com/posts/354-unifying-the-technical-interview
Knowing what I know now, I would’ve tried to push for a threaded interpreter to get rid of the runtime overhead of dispatching altogether. I don’t know if they’ve changed the architecture of that module much since I left :-)
These are nifty data structures that can quickly search the space of equivalent programs.
> All the while, those additional credit hours cost students a shitload of money and debt and take focus away from their actual fields of study.
This is a straw-man. The purpose is not to turn people into renaissance scholars. It's to inculcate appreciation for what makes life worth living. An educated populace is also a requirement for a healthy democracy. Everyone ought to know some history at a minimum.
Making art and humanities programs demonstrate some kind of pecuniary benefit is disgusting and myopic. My wife pursued English because she loves writing. She's earned about 0 dollars from that degree because she's home with our kids. And that's OK! Our lives are so much richer because of her degree—as well as the classes I took from the English department. So we should penalize the humanities because it merely makes people better thinkers and doesn't have as high of an ROI as an MBA? Yuck!
(EDIT: the article does mention that this bar is low—so not too bad—but the fact that this is a metric and criteria in the first place opens this up to abuse in the near future.)
I get that it's intended to cut down on ballooning tuition and fees, but *this is not the right way to do that.* (Actually, if we eliminated half the administration, I wonder how much we could cut costs…)
All my volume/brightness/etc functions are handled on a separate layer. I've got function keys on another layer as well, but I don't ever use them.
If you use function keys a lot, then you could do something like putting the function keys on one layer all on the right hand like it's a num pad and then adding a key on the left hand to switch to that layer. You could add combo-taps on your main layer to trigger the function key (e.g. press `q` and `1` at the same time to hit `f1`, `w` and `2` at the same time to send `f2`, etc.), etc. etc.
QMK gives you a lot of options to do what you want. There's also 3 keys towards the center of the keyboard on each side that I rarely hit (in fact, they're used for some layer switching some times!) that you could easy bind to function keys directly.
Note that a key can do like 4 different things depending if you tap, hold, double tap, or tap and hold if you want to get really fancy.
I've looked at some other more minimal boards and, while they look nice, I actually make good use of pretty much all my keys and I would not like going down to a smaller layout.
In my mind, the most important pieces of a good keyboard are, in this order:
1. QMK/ZMK firmware so you can add stuff like mod-taps and whatnot
2. Split & tented to avoid bad wrist angles
3. Lots of buttons for your thumb to press: it's your strongest finger so you should put it to work
4. Ortholinear layout for more natural finger movement
ZSA (the maker of the Ergodox, Moonlander, and Voyager) is a great company—I've had incredibly positive experiences with their support team whenever I've needed help. One time I was having trouble using their online configuration tool (https://layout.new) and so I emailed support. I got an email back within the hour from a developer asking for more details. After I supplied this, it was just another hour until I heard back saying that they had found a bug and that the fix was live. So awesome!!