72 results found.
viv 0.14.0 is out. It installs PHP dependencies from a composer.lock and writes the same vendor/ Composer would, byte for byte – 20 of 20 pinned projects identical in this release's sweep.
This is the last release where that is the whole point. From here viv is a research vehicle for package manager design, one measured chapter at a time, with the compatible mode frozen as the control. Looking forward to learn a whole bunch! #projects #vivace
It began as a question, whether a person directing coding agents can build a faster drop-in Composer, and that question is answered. The compatible mode is finished and frozen as a control. viv continues as a research vehicle for package-manager design, one measured chapter at a time; Now exploring "Beyond composer" https://github.com/svandragt/vivace/blob/main/docs/research.md #projects #vivace
Vivace got a manual now! Good software has good documentation! #projects #vivace
Park support sync now, so you can totally use it as a private decentralised issue tracker.
It keeps parked work context in a SQLite database, and until now the way to use it on two machines was to point PARK_DB at a synced folder, this can cause corruption: SQLite writes a database as several files that have to stay in step, a syncer copies them one at a time, and eventually you get a half-copied set that will not open at all.
So park no longer shares the database. Each machine appends its changes to its own <hostname>.jsonl in the shared folder, reads every log it finds, and folds them into a local database that you can delete and rebuild whenever you like. No file has two writers, so there is nothing for the syncer to get wrong.
Two environment variables and a one-time seed:
export PARK_DB="$HOME/.local/share/park/park.db"
export PARK_SYNC_DIR="$HOME/sync/park"
park sync-seed --i-understand-this-runs-once
then park rebuild --yes on your other machines.
Also in this one: park serve reads a snapshot rather than holding the database open, search indexing stopped rebuilding the whole index on every write, and park version exists.
Vivace 0.11.0 is out. This is the first proper release!
Anyone putting viv in a CI step or a Dockerfile no longer has to pin a version and update it by hand, or reimplement "latest" themselves.
Viv is at least twice as fast as any alternative I'm aware of: most of what the milestone tracked had already shipped in 0.10.0, and the one user-visible change is constraint matching, which went from about 27ms across 33,000 calls to 4 or 5. The bigger numbers in the README moved because the table was two releases stale.
viv installs PHP dependencies from a composer.lock and writes the same vendor/ Composer would, byte for byte – the compatibility sweep for this release was 44 rows identical, 0 differing, and all ten pinned projects resolving the same lock. It's around 6x faster on a cold install and 19x warm than composer.
| Scenario | viv vs Composer | viv vs riff |
|---|---|---|
| Cold | 6.1× (2.7 to 10.9) | 2.0× (0.9 to 127.2)[^5][^6] |
| Warm | 19.4× (5.8 to 104.0) | 5.5× (2.1 to 147.4)[^6] |
| No-op | 43.3× (19.3 to 109.6) | 12.6× (2.5 to 52.1) |
| Update-warm | 1.8× (1.4 to 4.2) | n/a |
What I want now is more real projects using it, because the useful bug reports have all come from someone trying to migrate something real and hitting a wall. The last release's best change came from a person who unpacked the tarball by accident and found a drop-in composer shim nobody had documented. So: if you try it and something gets in the way, I'd like to hear about it.
Originally written on lamb-releases:
First release candidate for 0.15.0. The theme is authoring and media: drafts survive a reload, phones can attach photos directly, and uploads render responsively.
DailyFeed gathers the blogs, news sites and newsletters you follow into a single edition. It arrives at the hour you pick, in your own timezone. It is finished when it lands, and it does not grow while you read it.
Free up the rest of your day!
Released version 0.2 of Gala-xy, my plugin for the Gala window manager.
After experimentation to enhance the default elementaryOS workflow and a few days switching to Gnome + PaperWM, I added a feature where you can switch between windows with a single keystroke, twice as fast as alt-tabbing,
Together with the focus ring around the active window, this creates a very smooth workflow, as elementaryOS itself already provides nice window management (hide, maximize, tiling, workspaces), and a great multimonitor workspace support (workspaces apply to the first monitor only, the windows on the second monitor are visible on all workspaceS).
I've been building diagnostic tools for identifying and correcting errors with the syncing and backup process of the JottaCloud backup solution. Claude triggered my inner nerd, when after being questioned to review its size of the CLAUDE.md file where it stores its learning:
No hard limit is near; that's a comfortable size for a repo whose whole value is hard-won operational lore.
Operational lore! This reminded me of all the companionship and anecdotes shared when developers and friends of the industry meet up. So I asked it to track the lore of the project and turn it into the stuff of legend, "the same lore as CLAUDE.md, told as it
might be told by firelight three hundred years on, when nobody remembers what a
daemon was".
The result is surprisingly entertaining, so after a bit of iteration, you can now unravel the Legends of the Sleeping Keeper within the repo.
Originally written on lamb-releases:
A release candidate for 0.13.0. Try it on a test install before you put it on a site you care about, and report anything that looks wrong. The headline is that you can now get your content out of Lamb and back into it: a full site export, and importers that read it back. Login also gets a brute-force throttle, and Micropub gains several fixes.
As its developer I use early versions on this very website, and imported two Known sites into this blog. #lamb #projects