"Maude’s basic programming statements are very simple and easy to understand. "
Never, ever start your tutorials that way.
"Maude’s basic programming statements are very simple and easy to understand. " Never, ever start your tutorials that way. To find out where the forest forest fires are in Canada, you have two options:
Show previous comments
@neauoire i know this shouldn't be needed, but is nitter (for example https://nitter.nl/) fine to access the twitter account unlogged? @neauoire I've been in canada for only a year and half, so I'm definitely ignorant in that regard, but is the 2nd one you're mentioning https://firesmoke.ca/ ? If not, their FAQ provide a technical description of their system and source; would that help? https://firesmoke.ca/resources/bsc-2014-description.pdf Implemented something like lambdas(fancy word to mean inline anonymous functions) in #Uxntal, it makes some types of code a bit more readable. Here's a little snippet that applies the body of a lambda to each pixels of a 256x256 texture. The body of the lambda is Viznut's code from the Permacomputing paper in the latest Computing Within Limits workshop. I spoke too soon earlier, it turns out that forth-style lambdas are possible by adding only 31 bytes to the self-hosted assembler. It might be worth it, it adds a lot of expressiveness by allowing to play with a lot of joy-like things.
Show previous comments
@neauoire you're making me come back to Factor and Joy :) and try uxntal + varvara but that's for another day... maybe a port of Joy? Instead of an absolute address(a-la cdr) to the end of the lambda scope, I'm piggy-backing on the JSI opcode which stores a relative address, so this gives me the length of the lambda scope, and as a side effect, "free" Pascal-style strings. I've totally lost track of where I was going with this lambda project, but I LOVE IT Spent all afternoon trying to implement closures in Uxntal, with an implementation budget of 0x20 bytes, and I couldn't get it done. I've tried both strategies, inline and jumping over, or collect and write at scope change. Both are more intricate than I'm willing to spend, but in different ways. @neauoire The ~~Kolmogorov~~ 100 Rabbits Complexity of closures is over 32 bytes. Noted. @neauoire I played around with closures here, to get a *spec style DSL working: https://github.com/tsujigiri/uxpec#usage By the time we got back to the shore, the water had risen to waist high where we had anchored it, which was the beach at the time. When trying to board the dinghy from the water, I went for a very brisk and bracing swim as I tried to plop myself into it. I'm sure it must have been an absolute joy to watch for any observer from the anchorage.
Show previous comments
@neauoire ...there is nothing – absolutely nothing – half so much worth doing as simply messing about in boats.
[DATA EXPUNGED]
@wim_v12e I'd like to have you thoughts on this idea, if you have the time, it doesn't have to be right away. But for a little while now I've been thinking of adding something to uxntal, or maybe make it its own language, but basically uxntal with inline definitions. You could anonymous segments of code, and the assembler would write those in memory someplace, and just put their address as a LIT2 at the definition. Any thoughts on this? That's your department. "providing all those features in 64KB sent me down a very, very deep rabbit hole, and I'm still not entirely out of it." @neauoire i don't think it's bad at all (especially if you have typedef) What I think is bad about C is, for example, this: char c = 0x80; Went for dinner, came back and had to scroll through two pages of new followers notifications from almost exclusively the hachyderm instance. Could one of you care to explain? Every evening, Rek does readings to me from Sylvie & Bruno, we're almost done. We fall asleep laughing at Bruno's delightful and totally absurd humour and.. the demented illustrations. @neauoire Thanks, I don't know this book! For those who are wondering who is the illustrator : it's Harry Furniss. https://commons.wikimedia.org/wiki/File:Sylvie_and_Bruno_illustration_scan_60.png It turns out that I spend way more time editing 80-columns text files than I expected, so I added a way in Left to add some words in the body of a paragraph, and reformat it to fit. A tiny addition, that'll save me a ton of time. I get my best ideas walking in the woods, but then, I'm in the woods.. So, I gotta run back We're always gathering notes for projects we'll try to tackle in the upcoming winter, but one that I've been particularly looking forward is to take out the household water tank we put under the v-bert, and build one from scratch that follows the curves of the bow, built into the hull itself. @neauoire it will be far from a perfect fit but I do have the water tank from under the v-berth of my Albin that you are welcome to. @neauoire Not a water tank, but my dad built a holding tank out of fiberglass that follows the curve of the hull, if you're looking for ideas: http://www.sltf.com/boat/system/plumbing/?zoom_highlight=holding+tank As the forecasts for next summer are rolling in, we're making plans to prepare Pino over the winter so we can ride the heat wave out in the damp and foggy Broughtons next year. |
@neauoire Yeah this is one of the first things I learned when writing technical things. People write these things thinking it makes it more approachable (don’t worry, you’ll have an easy time) but all it does is alienate anyone for whom it is not easy. I actually wrote a quick plugin for my text editor that highlighted any instance of “simple”, “easy”, “trivial”, “straightforward”, and about a dozen other similar words. Deleting them always made my writing better and more approachable.
@neauoire when I first started doing technical writing in my work, @robpike taught me never to describe things as “simple” or “obvious” or to say “just do x”, all of which imply a facility in the reader that may not exist. It stuck with me.
@neauoire but what if I hate my students?