271–280 of 1001 posts
Mostly writing for myself; I should really convert some drafts into proper blog posts because I'm really interested in discussing my ideas with others. I've been thinking a lot about the current field of AI research and wondering if we're asking the right questions? I've watched some videos from Yann LeCun where he highlights some of the key limitations of current approaches, but I haven't seen anyone discussing or s…
Can be used for everything from slightly skewed beat-making to generating undulating waves of sound!
I've been working on a fully electric last-mile delivery company: https://hudsonshipping.co Beyond the landing page (built with Astro), I've been building all of the route optimization, the delivery and warehouse management systems. A combination of go and java has allowed me to write a few microservices in the past 6 months to handle all of my logistical processes, and I'm just testing the mobile app in the field as…
I've added a few exclusive features to one of my extensions for subscribers in addition to settings syncing, and have auth and Stripe redirects and webhooks working, so now at the stage of working out the best heuristics to use for when to sync and connecting the extension to the settings API.
Not as exciting or big as some of the projects on here, but just a small personal one I’ve been wanting to do for a while. I recently impulse bought an Epson receipt printer, and I’ve started putting together a server in Go to print a morning update every day. Getting it to print the weather, my calendar and todos, news headlines, HN front page. Basically everything I pick up my phone for in the morning, to be on pap…
I store the chunks in a custom-built database (on top of riak_core and Bitcask), and I have it automatically also make an HLS stream as well. This involved remuxing the AAC chunks into MPEG-TS and dynamically create the playlist.
It's also horizontally scalable, almost completely linearly. Everything is done with Erlang's internal messaging and riak_core, and I've done a few (I think) clever things to make sure everything stays fast no matter how many nodes you have and no matter how many concurrent streams are running.
I've been working on a fully electric last-mile delivery company: https://hudsonshipping.co Beyond the landing page (built with Astro), I've been building all of the route optimization, the delivery and warehouse management systems. A combination of go and java has allowed me to write a few microservices in the past 6 months to handle all of my logistical processes, and I'm just testing the mobile app in the field as…
Local-first web applications with a compiled backend – After eight years working on web platforms, the conventional stack feels bloated. The client already defines what it wants to fetch or insert. Usually through queries. So why not parse those queries and generate the backend automatically (or at least, the parts that can be)?
Triple stores as a core abstraction – I’ve been thinking about using a triple-based model instead of traditional in-memory data structures, especially in local-first apps. Facts could power both state and logic, and make syncing a lot simpler.
Lower-level systems programming – I’ve mostly worked in high-level languages, but lately I’ve been writing C libraries (like hash maps) and built a minimal 32-bit bare-metal RISC-V OS.
It’s all still brewing, but I think these ideas tie together nicely. What if the OS didn’t have a file system and just a fact store? Everything could be queried and updated live, like a Lisp machine but built on facts.
Some other things I’ve been playing with:
A jQuery-like framework and element factory - You can pass signals that automatically updates the DOM.
A Datomic-like database on top of OPFS - where queries become signals that react to new triples as they enter the system. Pairs well with the framework above.