ecsolticia
@ecsolticia.bsky.social
Mathematics, DSLs, automata, computer simulation and big words tickle my fancy.
ecsolticia.codeberg.page
ecsolticia.codeberg.page
Another day of working on #logissert, a simple boolean logic DSL with equivalence-aware asserts for boolean functions.
Implemented said equivalence-aware asserts. One can now define new functions and test whether expressions using them are equivalent to other expressions.
Implemented said equivalence-aware asserts. One can now define new functions and test whether expressions using them are equivalent to other expressions.
![[assert]
AND(x,y) = NOT(OR(NOT(x),NOT(y)))
Result: TRUE](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:h5uflu6cfdbvjsggusevvy6i/bafkreigh7mrjht5xoaw3f5bnyx72kz2qboe446jir6tyjaadca2dgqg7me@jpeg)
December 24, 2025 at 9:51 AM
Another day of working on #logissert, a simple boolean logic DSL with equivalence-aware asserts for boolean functions.
Implemented said equivalence-aware asserts. One can now define new functions and test whether expressions using them are equivalent to other expressions.
Implemented said equivalence-aware asserts. One can now define new functions and test whether expressions using them are equivalent to other expressions.
Played Cities: Skylines (the original one) after 5 whole years. I find myself suddenly performing better generally than I was ever able to back then. The most noticeable difference is that I am better able to think in terms of systems and consider long-term consequences of each decision. (1/2)
December 22, 2025 at 11:16 AM
Played Cities: Skylines (the original one) after 5 whole years. I find myself suddenly performing better generally than I was ever able to back then. The most noticeable difference is that I am better able to think in terms of systems and consider long-term consequences of each decision. (1/2)
Another day of working on #logissert
Implemented let statements today. That's it.
I sort of don't feel like working on the project anymore, but I feel like I am in such a state that I would feel that with anything. So am just slowly pushing through.
Implemented let statements today. That's it.
I sort of don't feel like working on the project anymore, but I feel like I am in such a state that I would feel that with anything. So am just slowly pushing through.
December 22, 2025 at 11:07 AM
Another day of working on #logissert
Implemented let statements today. That's it.
I sort of don't feel like working on the project anymore, but I feel like I am in such a state that I would feel that with anything. So am just slowly pushing through.
Implemented let statements today. That's it.
I sort of don't feel like working on the project anymore, but I feel like I am in such a state that I would feel that with anything. So am just slowly pushing through.
Wanted to make the simplest sandbox game that I could make. Ended up with an implicit puzzler.
#gamedev #indiedev #godotengine
#gamedev #indiedev #godotengine
December 17, 2025 at 10:42 AM
Wanted to make the simplest sandbox game that I could make. Ended up with an implicit puzzler.
#gamedev #indiedev #godotengine
#gamedev #indiedev #godotengine
In spite of how simple it is and the fact that I have already implemented the core once, I kind of lost interest in finishing #logissert. It's like I just wanted an excuse to write a recursive descent parser, and now that the parser is mostly done, my interest in the project is gone too.
December 11, 2025 at 11:17 AM
In spite of how simple it is and the fact that I have already implemented the core once, I kind of lost interest in finishing #logissert. It's like I just wanted an excuse to write a recursive descent parser, and now that the parser is mostly done, my interest in the project is gone too.
Day 4 of working on #logissert, a simple boolean logic DSL with equivalence-aware asserts for boolean functions.
Today I added data structures for representing boolean functions as truth tables, and for mapping symbols to truth tables. Constants are treated as functions with zero arity.
Today I added data structures for representing boolean functions as truth tables, and for mapping symbols to truth tables. Constants are treated as functions with zero arity.
December 8, 2025 at 1:33 PM
Day 4 of working on #logissert, a simple boolean logic DSL with equivalence-aware asserts for boolean functions.
Today I added data structures for representing boolean functions as truth tables, and for mapping symbols to truth tables. Constants are treated as functions with zero arity.
Today I added data structures for representing boolean functions as truth tables, and for mapping symbols to truth tables. Constants are treated as functions with zero arity.
Day 3 of working on #logissert, a simple boolean logic DSL with equivalence-aware asserts for boolean functions.
The parser is "done" (codeberg.org/ecsolticia/l...). Technically, it's not true to the grammar I wrote down in that it ignores sugar syntax, but that's for another time.
The parser is "done" (codeberg.org/ecsolticia/l...). Technically, it's not true to the grammar I wrote down in that it ignores sugar syntax, but that's for another time.
December 6, 2025 at 4:03 PM
Day 3 of working on #logissert, a simple boolean logic DSL with equivalence-aware asserts for boolean functions.
The parser is "done" (codeberg.org/ecsolticia/l...). Technically, it's not true to the grammar I wrote down in that it ignores sugar syntax, but that's for another time.
The parser is "done" (codeberg.org/ecsolticia/l...). Technically, it's not true to the grammar I wrote down in that it ignores sugar syntax, but that's for another time.
Day 2 of working on #logissert
Halfway there to a recursive descent parser for the grammar.
Thought I could write the parser in a day, and I COULD. But that would require me to spend more time on in, and I don't want to do that today.
The parser should be done by tomorrow if nothing comes up.
Halfway there to a recursive descent parser for the grammar.
Thought I could write the parser in a day, and I COULD. But that would require me to spend more time on in, and I don't want to do that today.
The parser should be done by tomorrow if nothing comes up.
December 5, 2025 at 3:05 PM
Day 2 of working on #logissert
Halfway there to a recursive descent parser for the grammar.
Thought I could write the parser in a day, and I COULD. But that would require me to spend more time on in, and I don't want to do that today.
The parser should be done by tomorrow if nothing comes up.
Halfway there to a recursive descent parser for the grammar.
Thought I could write the parser in a day, and I COULD. But that would require me to spend more time on in, and I don't want to do that today.
The parser should be done by tomorrow if nothing comes up.
Building it from scratch again. The existing code wasn't spaghetti or anything, I just don't like how I structured it anymore. Also cutting down on some fluff.
A zero-copy lexer done today. I'm going slow this time as I have other things to do. Will implement the parser tmrw.
Calling it #logissert
A zero-copy lexer done today. I'm going slow this time as I have other things to do. Will implement the parser tmrw.
Calling it #logissert
Why settle for a typical digital logic circuit simulator when you can build your own, but as a computer language instead? I already have a correct implementation of the core functionalities (it's rather simple), but I have yet to fully sort the UI out. Been a fun project so far!
December 4, 2025 at 3:27 PM
Building it from scratch again. The existing code wasn't spaghetti or anything, I just don't like how I structured it anymore. Also cutting down on some fluff.
A zero-copy lexer done today. I'm going slow this time as I have other things to do. Will implement the parser tmrw.
Calling it #logissert
A zero-copy lexer done today. I'm going slow this time as I have other things to do. Will implement the parser tmrw.
Calling it #logissert
Have been on a total break from my usual projects for a while. Too much going on.
December 2, 2025 at 5:25 PM
Have been on a total break from my usual projects for a while. Too much going on.
Reposted by ecsolticia
Interpreter alignment chart
October 15, 2025 at 7:56 PM
Interpreter alignment chart
Reposted by ecsolticia
the ugly truth they don't want you to know is that the math without numbers is actually more fun than the math with numbers
November 18, 2025 at 1:59 PM
the ugly truth they don't want you to know is that the math without numbers is actually more fun than the math with numbers
Why settle for a typical digital logic circuit simulator when you can build your own, but as a computer language instead? I already have a correct implementation of the core functionalities (it's rather simple), but I have yet to fully sort the UI out. Been a fun project so far!
November 18, 2025 at 9:19 AM
Why settle for a typical digital logic circuit simulator when you can build your own, but as a computer language instead? I already have a correct implementation of the core functionalities (it's rather simple), but I have yet to fully sort the UI out. Been a fun project so far!
I'm wondering to myself why I approximately quadrupled the amount of development time just for fancier error-reporting for an utterly simple DSL I'm cooking. The rules are simple enough that the errors are generally easy to spot by inspection anyway. But hey, it looks nice! (I think)
![Implied terminal output of `cargo run` on said DSL project:
```
[[tokens]]
1 |[let][OR][(][A][,][B][)][NOT][(][AND][(][NOT][(][A][)][,][NOT][(][B][)][)][)]
2 |[assert][!]
---
Error code 7:
Expected assignment operator '='
-
1 | let OR(A, B) NOT(AND( NOT(A), NOT(B) ))
- -------------^^^
Error occured at line 1, from column 14 to 16
=======
Error code 9:
Expected valid identifier in expression
-
2 | assert !
- -------^
Error occured at line 2, from column 8 to 8
=======
```](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:h5uflu6cfdbvjsggusevvy6i/bafkreifmou24px3mt7uw22jpwucxdqoedu6expszjshpem3mqopvus2qc4@jpeg)
November 10, 2025 at 12:01 PM
I'm wondering to myself why I approximately quadrupled the amount of development time just for fancier error-reporting for an utterly simple DSL I'm cooking. The rules are simple enough that the errors are generally easy to spot by inspection anyway. But hey, it looks nice! (I think)
Reposted by ecsolticia
there was this great talk at one of the zig conferences where a developer talked about how they preferred static types because of their adhd.
static types are also an accessibility tool
youtu.be/vd1-rAIYV6I
static types are also an accessibility tool
youtu.be/vd1-rAIYV6I
Types and other techniques as an accessibility tool for the ADHD brain - Michael Newton
YouTube video by Zig SHOWTIME
youtu.be
November 8, 2025 at 3:51 PM
there was this great talk at one of the zig conferences where a developer talked about how they preferred static types because of their adhd.
static types are also an accessibility tool
youtu.be/vd1-rAIYV6I
static types are also an accessibility tool
youtu.be/vd1-rAIYV6I
Autopilot. Sharp turns.
Symmetry. Periodicity.
Symmetry. Periodicity.
November 9, 2025 at 4:54 AM
Autopilot. Sharp turns.
Symmetry. Periodicity.
Symmetry. Periodicity.
Reposted by ecsolticia
When people celebrate the individual genius of folks in science, they should also
mourn the collective loss of genius of folks who were actively discouraged or disadvantaged from a career in science because of the same person(s)
mourn the collective loss of genius of folks who were actively discouraged or disadvantaged from a career in science because of the same person(s)
November 7, 2025 at 11:43 PM
When people celebrate the individual genius of folks in science, they should also
mourn the collective loss of genius of folks who were actively discouraged or disadvantaged from a career in science because of the same person(s)
mourn the collective loss of genius of folks who were actively discouraged or disadvantaged from a career in science because of the same person(s)
I have this reoccurring bias of assuming that what is obvious to me must be obvious to others too. Unsurprisingly, I often get surprised when I say something that's obvious to me, and someone else labels it insightful or illuminating somehow.
October 30, 2025 at 7:41 AM
I have this reoccurring bias of assuming that what is obvious to me must be obvious to others too. Unsurprisingly, I often get surprised when I say something that's obvious to me, and someone else labels it insightful or illuminating somehow.
Reposted by ecsolticia
At this point I have to admit I have no idea who anyone means when they refer to "normies"
October 24, 2025 at 2:43 PM
At this point I have to admit I have no idea who anyone means when they refer to "normies"
Reposted by ecsolticia
New in Leaflet Publications: subpages!
One of our favorite features from Leaflet docs, now available to turn your blog posts into…
…collections? wikis? project logs? zines? essays with twisty tangents? or other complex creative branching forms :)
Check out this post to see what it looks like!
One of our favorite features from Leaflet docs, now available to turn your blog posts into…
…collections? wikis? project logs? zines? essays with twisty tangents? or other complex creative branching forms :)
Check out this post to see what it looks like!
Pub subpages & other recent features!
Lab Notes 013: publications can now have nested pages — illustrated here with pages about embeds, comments, and more
lab.leaflet.pub
October 21, 2025 at 7:42 PM
New in Leaflet Publications: subpages!
One of our favorite features from Leaflet docs, now available to turn your blog posts into…
…collections? wikis? project logs? zines? essays with twisty tangents? or other complex creative branching forms :)
Check out this post to see what it looks like!
One of our favorite features from Leaflet docs, now available to turn your blog posts into…
…collections? wikis? project logs? zines? essays with twisty tangents? or other complex creative branching forms :)
Check out this post to see what it looks like!
Recursive descent parsers have become my favorite thing to program recently.
October 19, 2025 at 3:25 AM
Recursive descent parsers have become my favorite thing to program recently.
I was mainly procrastinating on it, but my indefinitely-flying paper airplane thingy has been evolving!
Now, your paper airplanes can't get out of view. Instead, you can bounce with the bounds again and again to create fun trails.
#gamedev #godotengine
Now, your paper airplanes can't get out of view. Instead, you can bounce with the bounds again and again to create fun trails.
#gamedev #godotengine
October 15, 2025 at 6:49 AM
I was mainly procrastinating on it, but my indefinitely-flying paper airplane thingy has been evolving!
Now, your paper airplanes can't get out of view. Instead, you can bounce with the bounds again and again to create fun trails.
#gamedev #godotengine
Now, your paper airplanes can't get out of view. Instead, you can bounce with the bounds again and again to create fun trails.
#gamedev #godotengine
It's funny to look at this in hindsight and note that my current "systematic approach" involves simply going with the flow a bit more. I currently don't even have a "main thing" going on the way I used to.
I feel impulses to do so many things yet constantly feel as if I do not have enough time for anything, other than my perceived "current main thing". I believe I would benefit from a more systematic way of interleaving. My current approach is a trivial "do one thing at once" taken to the extreme.
October 13, 2025 at 7:03 AM
It's funny to look at this in hindsight and note that my current "systematic approach" involves simply going with the flow a bit more. I currently don't even have a "main thing" going on the way I used to.
I don't know where I'm taking my indefinitely-flying paper airplane game anymore. Something something asymmetric symmetry. Something something mirroring
#gamedev
#gamedev
October 10, 2025 at 4:33 AM
I don't know where I'm taking my indefinitely-flying paper airplane game anymore. Something something asymmetric symmetry. Something something mirroring
#gamedev
#gamedev
I have been thinking about #gamedev again, and my text adventure idea went mostly nowhere.
I'm trying some other ideas. Lo and behold, an indefinitely flying paper airplane... well, indefinitely flying as long as you don't hit something. Where is THIS going? Could be nowhere, hopefully somewhere.
I'm trying some other ideas. Lo and behold, an indefinitely flying paper airplane... well, indefinitely flying as long as you don't hit something. Where is THIS going? Could be nowhere, hopefully somewhere.
October 7, 2025 at 9:24 AM
I have been thinking about #gamedev again, and my text adventure idea went mostly nowhere.
I'm trying some other ideas. Lo and behold, an indefinitely flying paper airplane... well, indefinitely flying as long as you don't hit something. Where is THIS going? Could be nowhere, hopefully somewhere.
I'm trying some other ideas. Lo and behold, an indefinitely flying paper airplane... well, indefinitely flying as long as you don't hit something. Where is THIS going? Could be nowhere, hopefully somewhere.