Something Later

A delightful Ruby way to work with AI. No configuration madness, no complex callbacks, no handler hell – just beautiful, expressive Ruby code.

Very nice API/interface

No ollama support yet. Watching this pull request to add that 🤞

Kinda like FastHTML, but for Go

We give you the utilities to build html using pure go code in a reusable way (go functions are components) while also providing htmx functions to add interactivity to your app.

CLI tool and library for saving complete web pages as a single HTML file

Using separate pages instead of in-page interactions.

High-performance particle effects for SwiftUI built using TimelineView. Much more accessible than doing something similar using Metal.

You do not have to use generative AI. You may have to do spell checking or grammar checking, and the best versions of these might be generative AI, but otherwise generative AI is an option.

Tebako compiles Ruby applications into concise binaries that run on Windows, macOS, and Linux.

See also: https://terminalwire.com/articles/tebako

Straightforward, ruby-based static site generator. Small surface area that can be easily extended through custom extensions. Could be interesting to use for Pushcart Labs.

Some usage notes about https://github.com/dop251/goja. Could be interesting to use it as a scripting engine connected to PocketBase.

Highlights:

• Design for user needs, not organisational convenience
• Do the hard work to make things simple
• Staying secure means building for resilience
• Start small and optimise for iteration. Iterate, increment and repeat
• Display a bias towards small pieces of technology, loosely joined

Discovery coding is a practice of understanding a problem by writing code first, rather than attempting to do some design process or thinking beforehand. This means that a discovery programmer does not always start with a plan before starting to write code; rather, they think about the situation they are in. What is the tension we are trying to solve with this new code? What are the situations that have given rise to this demand? How do these various bits of the system interact? It is only in the process of writing code and seeing the pushback the code gives that discovery programmers understand and devise a plan forward.

We are destroying software mistaking it for a purely engineering discipline.

Co-to-the-sign

An open-source cross-platform alternative to AirDrop

Good rundown on some things you can do now with html/css features like page transitions, dialogs, etc.

AI is not going to give you this CSS.

😏

Well-reasoned and does a good job of spelling out exactly what risks come from relying on LLMs for anything where accuracy/reliability matters (not just in the context he’s talking about).

The mini size could be a good option if I ever decide to switch from my medium-size Leuchtturm notebooks.

A better top-style resource monitor to show usage/stats for processor, memory, disks, network and processes.

Humans can not accurately describe what they want out of a software system until it exists.
Humans can not accurately predict how long any software effort will take beyond four weeks. And after 2 weeks it is already dicey.

I'm sure there are exceptions that prove the rule, but I tend to agree with these statements.

Lets you put the output from any script/program in your macOS menu bar.

Interesting also that it's written using Wails.app.

Kirby stores your content in simple text files. Folders are pages. Add images, documents and videos and you are ready to go.

Interesting looking CMS. Want to do a deeper dive. The "hooks" plugin feature sounds a lot like a similar idea I've had for other systems but haven't ever got around to implementing.

Also intrigued by the panels/blueprints idea for customizing the admin on a per page type basis.