5,495 karma · joined September 17, 2008
http://www.storytotell.org
Feel free to email me at fusion at storytotell dot org.
[ my public key: https://keybase.io/fusiongyro; my proof: https://keybase.io/fusiongyro/sigs/aYrkbCZouBBhqp_qOKPGdBfIn---A8P8wPVCKLSlpnA ]
Most music is worth exactly one listen. You can tell right away if you're going to need to hear it again.
I think it would be interesting to experience a screenless office. Obviously I would think more deeply about things. Some of that thought would be "wasted," in the sense that I would be working things out I could simply look up on Stack Overflow. But I think there is a cognitive difference between working something out yourself and copying someone else's answer. In the former case, it feels like you are sort of exercising your own capacity to think, and in the latter case you can remain somewhat disengaged. The former is like walking a path, the latter is like watching a video of someone else walking it.
While paper is a renewable resource, this project is more of a thought experiment. Are we happy with the way we have become dependent on screens for computing? Every technology brings some tradeoffs—are we happy with the tradeoffs we are implicitly accepting? If not, what are we willing accept in return for change?
Being slightly more serious, I do web dev, mostly backend, for a radio astronomy observatory. I don't know anything about the science, but I wind up executing their routines in the cluster and doing typical database apps. I don't have much time on the side but I have been enjoying trying to learn J and realizing how much applied math is missing in my background!
I'm aware of the licensing costs, I'm more curious about whether Dyalog is obtaining popularity versus J, and if so, why. Of course, three new people going to the Dyalog conference would be a 10% increase in popularity, it looks like… so maybe this far out on the long tail it doesn't matter.
However, ICFP is 4 days, not a month, and the experience was good enough that it made me want to actually learn Haskell properly. I had fun and benefited in the long run. :)
Congratulations! This is the most entitled sentence in all of computing. The prize ceremony will be held at your house, tomorrow. I'll be casting a statue of gold for you, but first I have to rebuild all the software between me and the CNC machine in Coq or Typescript.
He also thought it would be funny in another edge case to have the program print out "SB no es bueno." I thought it was funny too...
https://www.metalevel.at/lisprolog/
At 160 lines, it's short enough and readable enough to give a hint of the kinds of things Prolog is good at.
Often you can follow Bird's advice for Haskell and make an inefficient program that is obviously right as a base. Prolog programs often have a generate-and-test flavor; once you have a good base, you can start refining inefficiencies in one side or the other. Maybe it's easier to make your generator produce better-qualified candidates, maybe it's easier to make your test faster.
Prolog also sometimes has surprising abilities owing to the unification process itself. For example, difference lists give you singly-linked lists with O(1) append to the tail. Data structures with "holes" are a generalization of that idea.
There's also a whole book devoted to making Prolog programs efficient: The Craft of Prolog by Richard O'Keefe.
In practice, Prolog requires the programmer to have some understanding of how it's going to be executed. This is in contrast to SQL, which is intentionally high-level to allow the database to figure out the best strategy and does require a lot more in the backend. Mercury also finds this abhorrent, but Mercury is another sufficiently-smart situation and a bit more obtuse.
There is some mismatch between what XML was designed for and the problems XML is good at solving. It was most certainly designed to be easy for humans to read and write manually. In practice, it is a great interchange format, by which I mean the specific idea of different parties writing XML for exchange between each other, because it can be validated mechanically. There is a large and powerful ecosystem of software that has sprung up around it which simply isn't there for s-exps or JSON.
Elsewhere on here, marcoperaza points out that it is kind of against hacker ethic. That's true. But enterprise software often involves multiple separate organizations having to agree on what a document can contain, and XML is great for that, and that use case tends to be more valuable in industry than whether it is the tersest, most flexible or readable format.