Dusty Phillips Codes

I know from experience that if I use a laptop keyboard for any length of time, I will be forced to do voice coding for months while the RSI heals.

I spent most of my winter break in my wood shop, working on some tech adjacent projects that I will post about later.

I love coding.

In earlier articles, we have implemented a tokenizer, parser, and transformer to convert WAT syntax to a Wasm AST, and got started on the code generation.

In earlier articles, we have implemented a tokenizer, parser, and transformer to convert WAT syntax to a Wasm AST, and got a good portion of the code generation step in place.

In earlier articles, we have implemented a tokenizer, parser, and transformer to convert WAT syntax to a Wasm AST and got started on the code generation.

In earlier articles, we have implemented a tokenizer, parser, and transformer to convert WAT syntax to a Wasm AST, and started building a code generator to create bytes from that AST.

In earlier articles, we have implemented a tokenizer, parser, and transformer to convert the Web Assembly Text Format to an Abstract Syntax Tree that can hopefully easily compile to Wasm.

In earlier articles, we implemented a tokenizer and parser to convert Wasm’s WAT syntax into an S-expression abstract syntax tree and started to implement a transformer to convert that AST into one more suitable for generating Wasm bytecode.

In earlier articles, we implemented a tokenizer and parser to convert Wasm’s WAT syntax into an S-expression abstract syntax tree and started to implement a transformer to convert that AST into one more suitable for generating Wasm bytecode.

In earlier articles, we implemented a tokenizer and parser to convert Wasm’s WAT syntax into an S-expression abstract syntax tree, and started to implement a transformer to convert that AST into one more suitable for generating Wasm bytecode.

In earlier articles, we implemented a tokenizer for the Wasm text syntax (WAT) and started on a parser to convert those tokes to a S-expression AST.

It’s been a while since I published the last chapter of LazyVim for Ambitious Developers on the website, but I was waiting for the print edition to be available to share it widely.

In earlier articles, we implemented a tokenizer for the Wasm text syntax (WAT).

In earlier articles, I introduced this “WAT to Wasm compiler in Roc” project, wrote some Roc code to load an input file, and implemented a tokenizer for a “hello world” of Wat to Wasm compilation.

In earlier articles, I introduced this compiler project, wrote some Roc code to load an input file, and started implementing a tokenizer with error handling.

In earlier articles, I introduced the project, wrote some Roc code to load an input file, and started implementing a Tokenizer.

In part 1 and part 2 of this series, I introduced the project and we wrote some Roc code to load an input file and save the compiled result to a different file.

Table of contents for my series on building a WASM compiler in Roc: Part 1 - Project Introduction (Roc and Wasm) Part 2 - Arguments and IO in Roc Part 3 - Tokenizer boilerplate Part 4 - Errors and positions in tokenizer Part 5 - Testing and tokenizing Part

My latest hair-brained project is a WAT-to-Wasm compiler written in the Roc programming language.

I’ve been curious about the Roc programming language for a while now, but I haven’t had/taken the time to really dig into it.

I’m working on a new book!

Dexie Cloud was released publicly today, and I love this product so much that I want to lend my voice to the marketing effort.

My wife and I have been working on Fablehenge—a writing app for novelists—for several years.

In my last article on Inko, I implemented several data structures to demonstrate how Inko’s single ownership model works.

I briefly described Inko’s unique memory management model in my previous article.

I’ve spent much of my free time (if there is such a thing) over the past few years researching various esoteric programming languages for no reason whatsoever.

UPDATE: I’ve updated the Inko Formula on Homebrew to 0.11.0, so you may just want to use brew install inko instead.

Throughout my career, I’ve at least tried most of the available programming editors.

Introduction This is the sixth in a series of articles exploring the Gleam programming language.

Introduction This is the fifth in a series of articles exploring the Gleam programming language.

Introduction This is the fourth in a series of articles exploring the Gleam programming language.

I’ve started a tutorial-style series on the Gleam programming language and wanted to collect them together here.

Introduction This is the third in a series of articles exploring the Gleam programming language.

(Original published September 30, 2021.

Introduction This is the second in a series of articles exploring the Gleam programming language.

Introduction Gleam is a newish programming language that I recently stumbled upon.

Introduction I was basically flat with an illness (yes, that one) on my back for two weeks in March.

Introduction I’ve been writing plenty about Rescript this year, although I’ve taken a bit of a hiatus to focus on developing a couple (Rescript) open source libraries.

As hinted in some of my recent articles on Rescript, I’ve been working on bindings to the wonderful Dexie interface to IndexedDB.

Introduction (Note: There is a more recent version of this article) Most of my Rescript series so far has been about combining Rescript with React using create-react-app.

Introduction For basic syntax, functional programming does not feel that different from other paradigms.

Introduction Polymorphic variants in Rescript are strange beasts.

Parsing dynamic content such as JSON in a statically typed language can be rather daunting.

In a recent article I introduced rescript-zora, a library I wrote for unit testing Rescript code with lightning fast responses.

I wrote Rescript bindings to the zora test framework and wanted to write about how to actually use them.

Continuing my explorations of RxDB and Rescript, this article hooks up mutations to allow RxDB to automatically sync its offline-enabled changes to the graphql server.

I’ve become quite comfortable in Rescript over the course of the past few months.

In the previous article we implemented the sync read endpoints between our graphql server and our RXDB client.

Now that our Rescript client and server have the same data model, we can hook up the graphql endpoints to sync the offline rxdb database with the graphql server.