I went into detail on my blog about this, but when I went to find the books to learn the tech stack—the ones considered as iconic to .NET developers as Programming Ruby is to rubyists—I was smacked in the face by choice overload. There doesn’t seem to be a book (or even a small set of books) that the community generally agrees is the best, like The Rails Way for Ruby on Rails. So, I’ve gotta pick and I’d like to base it on more than just the back covers.
PERSONAL: Continue working on my RTS with programmable units, I redid the movement system yesterday and will focus on custom unit UIs this week if I have time
I have some devlogs and ideas on the itch.io page: https://marcecoll.itch.io/kikai. It’s all in very early stages, planning to upload a sandbox demo soon and start iterating.
Let me know if you have any questions, ideas or anything really :)
For a basic ‘get it working’ implementation, the definition in the denotational semantics section of the report can be translated fairly easily into running code. See the definition in Chibi for an example.
A clever/more efficient implementation can be tricky and depends on your implementation of procedure call and return.
Thanks for the resource! I had not seen this file.
Chez Scheme also lists an example implementation. That implementation I cannot use as it is not properly thread safe as far as I can tell. I do not like implementations that use global variables, even thread local ones are not robust enough since scheme-rs functions can move threads.
I’m doing the same thing as I do for exception handlers - pass an extra parameter that contains the current dynamic extent. Then, when calling the escape procedure, we can compare dynamic extents and determine which functions need to be called:
I’m fleshing out the logistics of a trip to the US where I’m going to meet a bunch of people from the internet (in SF, Chicago, NYC and Bellingham of all places). Very much looking forward to it!
Working on an exploratory programming language. Next up is function monomorphization.
The ultimate aim is to try to mix Zig-like comptime with Swift/Hylo-like mutable value semantics, but with comptime being statically typed instead of dynamically typed like in Zig. (If calling Zig’s comptime dynamically typed doesn’t make sense, there are three phases: (i) type checking, (ii) comptime, (iii) runtime. I mean for all type errors to happen at type checking time, instead of at comptime like in Zig.)
Also hoping to accept a job offer or two. Will hear from one of them in a couple hours.
I got properly started on my new personal website my style aim for it is bureaucracy core so that is fun to play around with. I am also trying out using Typst as a markdown-equivalent for blog posts on it which is interesting.
Today I start a new job after 5 years of hard grind in an startup; it’s completely weird to change jobs after so long working on a place, but it’s incredibly exciting and refreshing. I will never get so burn out to stop believing software is beautiful!
As for my personal life, I went on a trip almost to the top of Monviso, it was an incredible experience
Working on my synth/groovebox project. I’ve made a little simulator for it using Raylib (great library!) which should speed up development a lot, don’t need to constantly flash the microcontroller now.
Trying to stay afloat with an ever growing todo list 😅
Highlights of the week should be a live recording of the Smith n Sniff podcast, and heading down south to visit a friend for a long weekend. Also made progress on my head unit bracket, think I have the positioning correct enough for it so now experimenting with how to strengthen it. Think I might print it in ABS and see how that holds up as a “strong prototype”, then I’ve got some PETG-CF to print a final edition of it. We’ll see how far I get with that this week.
Also chasing an electrical fault in a different car, on which the MOT expires this week. Realistically with travel that’s probably going to take a fortnight to get back on the road, sigh. At least I can sell it knowing all the issues with it have been chased out at that point though.
Figuring out how to use LiteFS with fly.io for my job. It’ll probably go okay. Outside of that, getting ready to move to north carolina and devour this book “Category Theory in Context” by Emily Riehl.
I’m reading the front matter to 53 books about C# and .NET to pick five to read each quarter for the rest of the year.
Why so many?
I went into detail on my blog about this, but when I went to find the books to learn the tech stack—the ones considered as iconic to .NET developers as Programming Ruby is to rubyists—I was smacked in the face by choice overload. There doesn’t seem to be a book (or even a small set of books) that the community generally agrees is the best, like The Rails Way for Ruby on Rails. So, I’ve gotta pick and I’d like to base it on more than just the back covers.
WORK: Tidy up after finishing a project
PERSONAL: Continue working on my RTS with programmable units, I redid the movement system yesterday and will focus on custom unit UIs this week if I have time
You have my attention and my curiosity.
I have some devlogs and ideas on the itch.io page: https://marcecoll.itch.io/kikai. It’s all in very early stages, planning to upload a sandbox demo soon and start iterating.
Let me know if you have any questions, ideas or anything really :)
Trying to get
dynamic-windimplemented for scheme-rs, which is the last control feature I need to implement before it’s just banging out features.Going on a trip tho, so not sure how far I’ll be able to get. It’s an annoying feature
For a basic ‘get it working’ implementation, the definition in the denotational semantics section of the report can be translated fairly easily into running code. See the definition in Chibi for an example.
A clever/more efficient implementation can be tricky and depends on your implementation of procedure call and return.
Thanks for the resource! I had not seen this file.
Chez Scheme also lists an example implementation. That implementation I cannot use as it is not properly thread safe as far as I can tell. I do not like implementations that use global variables, even thread local ones are not robust enough since scheme-rs functions can move threads.
I’m doing the same thing as I do for exception handlers - pass an extra parameter that contains the current dynamic extent. Then, when calling the escape procedure, we can compare dynamic extents and determine which functions need to be called:
I’m fleshing out the logistics of a trip to the US where I’m going to meet a bunch of people from the internet (in SF, Chicago, NYC and Bellingham of all places). Very much looking forward to it!
Working on an exploratory programming language. Next up is function monomorphization.
The ultimate aim is to try to mix Zig-like comptime with Swift/Hylo-like mutable value semantics, but with comptime being statically typed instead of dynamically typed like in Zig. (If calling Zig’s comptime dynamically typed doesn’t make sense, there are three phases: (i) type checking, (ii) comptime, (iii) runtime. I mean for all type errors to happen at type checking time, instead of at comptime like in Zig.)
Also hoping to accept a job offer or two. Will hear from one of them in a couple hours.
But most importantly:
I got properly started on my new personal website my style aim for it is bureaucracy core so that is fun to play around with. I am also trying out using Typst as a markdown-equivalent for blog posts on it which is interesting.
Today I start a new job after 5 years of hard grind in an startup; it’s completely weird to change jobs after so long working on a place, but it’s incredibly exciting and refreshing. I will never get so burn out to stop believing software is beautiful!
As for my personal life, I went on a trip almost to the top of Monviso, it was an incredible experience
Working on my synth/groovebox project. I’ve made a little simulator for it using Raylib (great library!) which should speed up development a lot, don’t need to constantly flash the microcontroller now.
Trying to stay afloat with an ever growing todo list 😅
Highlights of the week should be a live recording of the Smith n Sniff podcast, and heading down south to visit a friend for a long weekend. Also made progress on my head unit bracket, think I have the positioning correct enough for it so now experimenting with how to strengthen it. Think I might print it in ABS and see how that holds up as a “strong prototype”, then I’ve got some PETG-CF to print a final edition of it. We’ll see how far I get with that this week.
Also chasing an electrical fault in a different car, on which the MOT expires this week. Realistically with travel that’s probably going to take a fortnight to get back on the road, sigh. At least I can sell it knowing all the issues with it have been chased out at that point though.
Figuring out how to use LiteFS with fly.io for my job. It’ll probably go okay. Outside of that, getting ready to move to north carolina and devour this book “Category Theory in Context” by Emily Riehl.
work: first production deployment of the website I’ve been building for the last month
personal: uhhh… not sure
Mostly going through my backlog of client reported issues at work, and hopefully a few more chats with the new manager who came in last week.
On the personal front I will be reading up this series and follow it to implement ActivityPub for my blog.
Waiting for feedback on a study how to create likely-correct software: https://www.osequi.com/studies/list/list.html
And thinking about consulting / monetization
First half: writing/making sure it works fine after the third iteration of my password manager. Second half: let’s see how the first goes first.
Trying to learn the basics of machine learning, while looking for my first project for my new consulting gig
Probably just clearing out some of the short-and-sweet indie games in my backlog.
Continue building a flappy bird game using 3js and Cursor. Want to build this one for ever!