Tomorrow, I’m getting married, which is a pretty big step.

Probably getting ready for Hurricane Dorian

I am working on a mini image gallery (like flickr, 500px, google photos I guess)

Started off as a way to publish my photos in groups and view exif data in a very simple way, but I got carried away…

I haven’t been able to work on tilerswift tiler this week (NES tile editor written in Qt). Maybe I can get back to it this weekend.

But probably not tomorrow! Tomorrow I’m going to a taco festival!

http://tacofestmtl.com/fr/

http://tacofestmtl.com/en/

Bought some redheart last week, gonna turn some seamrippers. Also probably going to put some time in on the hammock out back. It’s gonna be a really nice weekend, and I’m going to try to do as little as possible.

Get better a D! I’ve been using it (and loving it!) in a project at work and I want to get better at it.

Learning the deep end of LaTeX stuff like writing your own classes and packages. Not going to lie, it’s a lot more straight-forward than I thought. It’s just a couple of identifiable macros (\NeedsTeXFormat and \ProvidesClass) and declare your new settings.

This Saturday I will be having a BBQ to celebrate my birthday. There are still a bunch of things I need to buy, and an ants nest to exterminate in my lawn (right where I want to BBQ).

Coding wise, I am still working on porting the parser for Inko from Ruby to Inko. This is taking quite some time now as I am making various syntax changes as we go along, mostly in the form of removing syntax or making it more strict. A challenge that I am currently facing is support for arguments without parentheses, allowing you to write something like this:

person.update 'Alice', 24

Support for this syntax was mostly inherited from Ruby, and it allows you to write something like this:

some_value.if true: { ... }, false: { ... }
some_value.if_true { ... }

Unfortunately, at the parser level this requires a whitelist of tokens that are valid for arguments, otherwise we might parse foo! as foo(!) instead of foo()! (in this case ! is used to cast from ?T to T). Another example would be foo[10], which without the whitelist would be parsed as foo([10]) and not foo()[10]. Since I don’t like whitelists, I have been thinking about limiting the possible values to: a single closure, or a list of keyword arguments with values. This still requires that we limit the amount of expected/allowed values at the parser level, but this list is much smaller than allowing arbitrary expressions.

I also thought about just removing arguments without parentheses, but this leads to code I am not a fan of, such as:

some_value.if(true: { ... }, false: { ... })

Or when breaking it over multiple lines:

some_vale.if(
  true: {
    ...
  },
  false: {
    ...
  }
)

Instead of what you can currently do:

some_vale.if true: {
  ...
}, false: {
  ...
}

Hopefully this weekend I can reach a decision on which path to take

Finally, I need to start writing this month’s progress update for Inko, which I expect will take a day or two.

I’ve been rewriting my Mastodon client TUI from scratch using urwid. I’m pretty happy where it is now.

Here’s a short demo: https://asciinema.org/a/264863

I’m taking my girlfriend to play minigolf.

She has never heard of minigolf.

I hope to find some time to work on a small performance optimization in CHICKEN Scheme, to avoid consing optional arguments (which are currently treated as a standard rest argument list). I hope this will improve performance of at least SRFI-13 (which is horribly slow).

I’m looking into Flutter’s internals. Specifically more into how the widget tree gets initially rendered, then how only changed parts get updated, i.e. the widget/element/render trees, plus keys (local/global etc), and the relationship between Builder, StatefulBuilder, StatefulWidget and StatelessWidget.

Anyone want to compare notes?

Getting ready for the holidays! I’m leaving for Hungary on the 2nd with some friends. I’ve been working almost all of August so I’ve really been looking forward to pulling the plug for a while.

Travelling to Toronto for a week onboarding at new remote job. Simultaneously excited about the week to come and dreading the long flight—and week away from family!

I’m getting a copy of Practical TLA+ so I’ll be reading that this weekend.

Finishing my third Western novel (Elmore Leonard’s Forty Lashes One Less). Otherwise, chilling with the in-laws on the Oregon coast.

I’m setting up a vive in the living room! Gonna play beat saber and stuff.

EDIT: apparently we have enough space for both the vive and the PSVR to be set up side by side! Awesome!

I have to finish and polish a C library that aims to make fork servers easier to use by abstracting out most of the gory UNIX programming. A fork server are a nice hack allowing to use the fork(2) system call without too much pain in multithreaded programs (especially if execve is not used immediately after fork).

Writing something in Nim.

Got back from a work conference this afternoon and spent the evening having dinner with a friend.

I took along “Implementations of Prolog” to read on the plane and at the hotel, and now I’m so far in I think I’ll keep reading before I jump back to “Parallel Logic Programming”.

I haven’t been able to ride all week, so I’m definitely riding somewhere, maybe even an overnight trip somewhere.

• Working on trading in my old laptop for a new one.
• Finishing up moving Mockturtule’s source/config into the lobsters-ansible repo.

Figuring out how to move my desktop’s file system from LVM on one disk to something that can take advantage of all of the available disks.

Anniversary dinner tonight! Getting dining room chairs from Structube tomorrow. Recording a new episode of Mr. Rewatch (a good podcast I produce) in light of the new season of Mr. Robot - tomorrow night. Setting up a bird net on my balcony on Sunday (finally a poop-free balcony experience!). And Monday, labour day, I will probably chill and do nothing.

Experimenting with handheld CNC router, maybe learning Rust, and finishing up a PCB or two.

Probably going to continue working on my Ben Eater inspired software implementation of the SAP-1 https://git.sr.ht/~vhodges/cputhing and/or starting on the hardware implementation