A cross-language compiler pipeline that translated Elm to Rust, implemented in Haskell with full constraint based type inference and checking.
My least loved project but IMO a greatly improved Bash dialect via an indentation sensitive parser. The syntax mimics the clarity of Python, but compiles to raw shell for automation heavy workflows like AWS deployments.
Indentation sensitive parser:
aws cloudformation deploy
--template-file $(pwd)/aws-infrastructure.yaml
--stack-name ...
--s3-bucket ...
--capabilities CAPABILITY_IAM CAPABILITY_NAMED_IAMFunctions:
from ./backend/services do
stack build
stack exec provision-dbMultiline Strings:
psql -d services -tc
"""
CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
"""A perfect example featuring the aws cli (i.e. because tool is incredibly VERBOSE):
# AWS Helpers
command aws::deploy do
aws cloudformation deploy
--template-file $(pwd)/aws-infrastructure.yaml
--stack-name ...
--s3-bucket ...
--capabilities CAPABILITY_IAM CAPABILITY_NAMED_IAM
command aws::deploy::info do
aws cloudformation deploy
--template-file $(pwd)/aws-infrastructure.yaml
--stack-name ...
--s3-bucket ...
--no-execute-changeset
--capabilities CAPABILITY_IAM CAPABILITY_NAMED_IAM
# Build and upload our image.
command ami::build do
linuxkit build -format vmdk -dir .linuxkit-out ./aws-image.yaml
ami-uploader .linuxkit-out/aws-image.vmdkNotice that this is basically bash + misc. conveniences like an indentation sensitive parser.
Other examples:
# idk...
command publish do
echo "Publishing..."
silent do
git add .
git commit -m "auto"
git push -u origin master
echo "complete"
echo "Complete."
git --no-pager log --name-status HEAD^..HEAD | grep commit
command db::init do
# Since Postgres doesn’t support something like “CREATE DATABASE IF NOT EXISTS”,
# well just run the following command and discard the the error it will produce
# if already created via the `try do [code block]` function.
try do
createdb services
psql -d services -tc
"""
CREATE EXTENSION IF NOT EXISTS "uuid-ossp"
"""
from ./backend/services do
stack build
stack exec provision-db
echo "Setup complete."
command run-chrome do
# Usually commands ending with an ‘_’ will redirect stdout/stderr to `/dev/null`.
run_ "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome"
--app=http://127.0.0.1:3000
--auto-open-devtools-for-tabs
command test do
# should this be something like `let lorem = ...`?
lorem <- echo "lorem ipsum"
parallel do
echo "first"
echo "second"
silent echo "third"
echo "done"
imager.io
|
github.com/imager-io
Automated image compression for efficiently distributing images on the web.
See my Medium article: Modern Image Optimization for 2020- Issues, Solutions, and Open Source solutions
Notably includes a tool called imager for optimizing the binary encoding of images in a brute force trial ’n error sorta manner, using a new (at that time) ML based perceptual quality metric designed to be a more accurate model of human perception compared to prior formulaic approaches.
It is extremely good at what it does.
source : ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 39.00M (4 images) kraken.io : ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 24M jpegmini.com : ▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇▇ 16M compression.ai: ▇▇▇▇▇▇▇▇ 8.90M imager : ▇▇▇▇ 4.20M
Sub Projects
I renamed this project to subscript-old after I decide to call my note taking tools ‘subscript’ which seemed more fitting because it dealt with typesetting.
There’s actually some pretty cool ideas in here. Abandoning this project is a major regret of my life.
A data-driven, Rust-native frontend library designed for backend developers — Subscript rethinks web UI as infrastructure. Built for those who want to author views, state, and styles entirely in Rust, with zero XML, full CSSOM control, and expressive compile-time macros.
Ideal for backend developers treating the frontend as just another client — including full inline CSS support (media queries, keyframes, pseudo elements) via a "selector-less functionalized CSS" model. Built-in routing, component messaging, and versioned view syntax enable deeply structured applications without frontend boilerplate.
parse_url!, with totality checks and type-safe bindings.
v1! for ergonomic and incremental UI design.
Client side URL routing/parsing VIA pattern-matching-like syntax:
parse_url! {
[] => {
Page::Homepage
},
["account", user_id: Uuid] => {
Page::AccountUser {
id: user_id
}
},
_ => Page::NotFound
};
Intermixed markdown and styling:
v1! {
display: "flex";
button !{
event.click[] => {
move || Msg::Increment
};
"Increment";
}
}Whe inline-styling compiles down to CSS stylesheets.
Impact: Inventive take on frontend architecture through Rust. Encourages architectural unification between client and server codebases, with precise control over styling and rendering.
Safe - Fast (and Non Blocking) - Dependency free - MIT License (with no GPL extras) - Image Loading, Resizing, Conversion and Processing.
At the end of 2019 I raked up an impressive 1,323 contributions on GitHub that placed me among the platform’s most active developers.
To put this in perspective, data from a 2016–2017 GitHub ranking shows the 256th most active user recorded 1,322 contributions—my activity surpassed this benchmark, placing me among the platform’s top contributors. While my work wasn’t featured in such lists due to follower-based filtering, my focus remains on creating impactful projects.
Sources
Top 2017 GitHub Contributors:
https://web.archive.org/web/20200415010317/https://gist.github.com/paulmillr/2657075/
Colbyn's GitHub Profile (stats at the bottom):
https://github.com/colbyn?tab=overview&from=2019-12-01&to=2019-12-31
The beginning of my note taking explorations.
Paged Media Support for native page handling)
My Book
Graph of y = x^2
y = x^2
y = x^2
f \triangleleft x &= f(x) \\
x \triangleright f &= f(x) \\
|x| &= \sqrt{x^2} \neq x \\
|x|^2 &= x^2
\delta \sin(x) &= \cos(x)
\delta \cos(x) &= -\sin(x)
\delta \tan(x) &= \sec^2(x)
\delta \csc(x) &= -\cot(x)\csc(x)
\delta \sec(x) &= \tan(x)\sec(x)
\delta \cot(x) &= -\csc^2(x)
Lemon drops sweet roll cupcake biscuit cookie. Ice cream pie apple pie fruitcake dessert sweet roll chocolate bar.
Sesame snaps lollipop marshmallow marzipan
Regarding the
This pattern was very common with my old school notes, where I could include screenshots of all the essential definitions from a given chapter.
Versatility in Subscript is made possible VIA macros, the syntax is akin to web components, but it's expanded out at compile time, instead of at runtime (i.e. a macro).
Comes with a syntax highlighting extension for VS Code.
It injects the LaTeX grammar from latex-workshop into the
Everything was produced via a dedicated note taking app that compiles your freeform notes into self contained webpages.
The note taking app was designed in such a way that everything can be very quickly navigated via autogenerated **tables of contents** from the root notebook down to individual pages.
Created this to use with LinuxKit.
Amazon machine image uploader & other miscellaneous utilities.
Example:
$ cargo run -- upload --bucket my-s3-bucket --image ./my-source-image.vmdk --name my-aws-amiAlternatively:
$ cargo run -- upload --bucket my-s3-bucket --key new-ami.vmdk --image ./my-source-image.vmdk --name my-aws-amiWelcome to the SubScript Note-Taking & Content Publishing Tools
Tools to accommodate my preferred note-taking workflow, from beautifully typeset (but relatively time consuming) LaTeX math and other markup, to rapid hand drawn notes when time constrained — all in one and seamlessly intermixed.
Features
Content publishing VIA Web-Technologies!
There are TONS of JS libs that do very specific things (for literally everything) that no-one ever uses outside perhaps an official web-app, for instance Desmos and GeoGebra are trivially embeddable but people hardly ever use their JS APIs. The goal of Subscript is to make this as convenient as possible with a declarative non-programming API for each. Something akin to e.g. exclusively using HTML tags for each in a declarative manner.
In a certain regard, SubScript is basically LaTeX, except, while you loose out on it's massive array of packages that do everything from math to extremely fine tuned musical notation rendering, you instead get a WIP LaTeX-like interface to the COLOSSAL JS ecosystem.
In 2022 popular markdown displays are finally getting support for displaying math, but it's still relatively limited with regards to the feature-set LaTeX provides.
The goal of Subscript is to be a monolithic publishing platform for everything under the sun, and by monolithic, I mean monolithic. While red flags may go off in your head, I've tried AsciiDoc, and the problem with AsciiDoc is that it's both slow, incredibly slow after a while, and especially, there's no syntax highlighting or autocomplete of embedded content! In theory AsciiDoc's idea of extensibility sounds nice, it may please your enterprise system architect, but it leads to a multitude of annoyances (to say the least) that you simply don't have with LaTeX. Furthermore, AsciiDoc makes assumptions that wouldn't easily translate to a browser environment. Whereas a monolithic architecture entails end-to-end uniformity.
In theory, Markdown based content publishing tools has the same issue, I've seen platforms built upon markdown with extra features, but will your stock markdown syntax highlighter support such? Whereas e.g. if you see a LaTeX package, odds are it supports the entirety of (Xe)LaTeX syntax and whatnot.
Subscript Markup Language
\h1{…} a tag, it's a
command (you can go on calling it a tag, idc. Originally, in the compiler implementation I used
the tag terminology for relevant names, but this was later changed without any particular
conscious reason, perhaps's it was just less confusing given it's LaTeX-like syntax,
regardless this is what stuck.)\ (which is an easy trigger for
auto-complete),!) (inspired by rust).\name[attributes]{arguments}\h1{Hello World}\include[src="./path/to/filename.ss"]\layout[cols=3]{…}\frac{1}{2}\name[attributes]{argument} or \name[attributes]\name[attributes]{arg1}{arg2}…{argN}parent command, for instance,
\row is only available if it's nested under a \table command. (It's a
variable arity/argument convenience command for creating a table row where each argument is
automatically wrapped in in a table-data element (if its not already), since HTML tables are very
verbose and I've been trying to streamline their creation for fast notes).Math Support
| Cmd | Type | Notes |
|---|---|---|
\math{…} |
Math Block | |
\{…} |
Inline Math | Due to how frequently it's used, I made it's invocation as short as possible |
\equation{…} |
Math Block | The default environment is equivalent to LaTeX's equation + split env |
Also the \math command support a few options for quickly defining common environments and whatnot, as shown in the following example (the num and tag options also work for \equation):
Which results in:
| Value | Shorthand | Notes |
|---|---|---|
equations |
e |
|
centered |
c |
When I update the \where! macro to support rewriting attributes, you'll be able to use such to keep track of labels within a local expression. Which will be something akin to:
By default numbered expressions are turned off, because I want a better interface for such than what KaTeX provides.
Layout
Things can be broken down into newspaper like columns VIA the \layout[col=num] command, for instance,
By default this also includes breakpoints that will decrement columns as the viewport width decreases until it breaks into single column mode.
While the \grid command gives you access to very fine tuned CSS grids:
File Import Support With Relative Headings
For example
Furthermore, this rule is recursively applied in a bottom-up fashion when files import other files that import other files and so forth (I really wish there were more HTML heading tags). So in any .ss file, always begin with H1 and decrement sub-headings relative to such (so the headings therefrom will result in the appropriate level in any given hierarchical context of file imports).
Automatic Table Of Content Generation
Currently being reimplemented to better handle multi-page and nested (hierarchical) page layouts.
Currently looks like this (in dark mode):
Unicode Support and Typography:
unicode-segmentation crate (which identifies Grapheme Cluster, Word and
Sentence boundaries according to Unicode Standard Annex #29 rules)."..." → “…”Local (anonymous) rewrite rules (VIA the \where! macro):
This was initially motivated by the ungodly mess that happened when I tried to color-code a complex bit of LaTeX math, where the resulting markup thereafter was incredibly hard to read... What I wanted was something akin to
Update
WARNING: I forgot to include ‘;’ at the end of each rewrite rule! Due to recent changes to the parser. It should instead look like this:
Integration with hand drawn notes VIA your iPad and Apple Pencil (With Dark/Light Mode Support!)
For rapid note taking and freeform content creation such as diagrams and hand drawn visualizations. Which the Subscript Markup Language and compiler natively supports for seamless integration into your published content.
Safe your files to e.g. iCloud Drive and seamlessly include such in your notes
Each freeform file can contain multiple drawing entries, which can be manipulated & formatted like so (VIA the \where! macro):
Notes:
.ss1-drawing files, since
.ss1-composition files are more complicated and I haven't worked out how the interface should work.
Drawing Editor Overview:
Regarding the pen list:
Foreground pens point downBackground pens point upForeground/Background feature allows you to underline and highlight things and
have such highlights render ‘underneath’ foreground strokes (it just looks nicer). Page Layout Editor Overview
Note that the above was produced VIA an older version of the app that e.g. had no support for light/dark mode.
This feature is specific to the ‘SubscriptComposition’ app.
Real World Example - My old chem notes:
Note that this was produced VIA an older version of the app (and therefore e.g. had no support for light/dark mode),
PDF Support WIP:
An experimental LaTeX like language with syntax highlighting support.
Features support for colorized nodes based on nesting depth:
A greatly improved macOS/iOS UI.
Editor:
Web/HTML Presentation:
Not Open Source
Experiments in compiling dictionaries, phrasebooks, and the like for language learning apps.
Tons of linguistic details.
Used my background as an amateur compiler engineer to build a sophisticated pipeline that can produce massive datasets from LLM generated entries.
Intro. My Note-Taking App & Why It Matters in the Age of Bots (YouTube): https://youtu.be/PEC5PyNhIds?si=W6w6zOrrK29rD37C
Contact me for details — will be publishing the initial version to the app store sometime in the near future — subsequent work will include more parallel (bilingual) scripture content of different books.
A proof of concept native markdown renderer for macOS/iOS.
Supports Freakin Markdown Tables!
With full text selection support:
Unlike the ChatGPT iOS app.
Also while it’s not pretty, I thought this was interesting:
The above was an early example multi cursor text selection of tables that—notably— includes an empty column at the end, which I kinda like but the latest version on GitHub has this disabled to be more akin to the original source code. What I like about adding an empty column at the end is that I could make it easy to append columns to the end of the table, just position the cursor at the end of a table row and press enter.
Overall:
Initially the work began with a proof-of-concept prototype with the following aims:
See my article:
At the time of this writing:
Now that the core functionality has been proven viable, I (the author) have learned much and I intend to translate my experience and lessons learned from the proof-of-concept prototype codebase into a viable set of libraries that app developers can depend upon. Starting from a blank slate.
So keep in mind:
High Level Objectives:
Additionally:
Overall I hope you’re excited as I am!
Personally I, the author (Colbyn Wadman), have been messing around with miscellaneous problems concerning text processing and text rendering (in one form or another) for a very long time and—as far as the POC has demonstrated—it’s good to see something interesting come from it, and when I release my work, I hope you’ll be pleased with the results. 🤞