Tooling

Research Idea: Maintaining A Write Ahead Log For Application Runtime State

Exploring the stepladder of features that lead to well-engineered backends

vados

13 minute read

tl;dr:What if there was a write-ahead-logging layer above/outside the database? Then you could get CQRS+ES capabilities and assurnaces from your database without rewriting, and even abstract out the database as a whole, going as far as to create your own DSL for application-level changes, ADD_USER instead of INSERT … INTO USERS …* I spend a bunch of time thinking about how I can waste less time writing applications. Over time I’ve worked on various protoypes, with varying levels of completeness, but as I move across languages, frameworks, databases, and stacks, I always find myself solving the same problems, and having the same worries.

vados

3 minute read

Working with PDFs on arch linux tldr; If you’re on arch, not all hope is lost when trying to deal with PDFs. pdfunite is out there for combining PDFs, Firefox is surprisingly helpful since is uses pdf.js, pdftk is there if you’re down with downloading the dependencies, convert is available for paring down scanned images, and ultimately, any software you can run on ubuntu can run on arch with a little docker.

Using jspm, systemjs, and vuejs together

Getting JSPM, SystemJS, and Vue.JS to play nicely together

vados

8 minute read

Using JSPM, SystemJS, and Vue.JS together tldr; There isn’t much much vue-with-jspm support outside of the systemjs-plugin-vue, so I made a thing that compiles jspm templates from html files, and JSPM+VUE is really working for me. Also, Vue.JS is the view library people should recommend to beginners. Not React. Lots of words about JSPM It looks like jspm isn’t winning the mindshare of new JS developers these days. Though I’m not sure I can blame anyone for not having mindshare left to give, with the constant onslaught of new libraries, frameworks, doodads and what-have-yous that pop up from day to day.