I am building a tool to manage your image generation inference. It uses ComfyUI as the backend and it allows you to index, search and invoke your workflows.
It makes it super easy to using existing workflows to chain them together into more complex outputs.
I agree with you but the main thing g here, IMO, is the friction with all the alternatives you mention in getting something working.
For example, I've never heard of Automator. I'm familiar with Zapier, I'll have to evaluate the two situations, then I'll find out that might need to find an alternative that runs on Linux and then I'll have to check if....
These are all simple steps but they all use a non-trivial amount of time for the problem their solving
> is the friction with all the alternatives you mention in getting something working
Have you tried to run openclaw? Their own docker container (apparently a compose now (???)) doesn't work for half the versions and the docs are probably the least informative thing you'll ever read.
>I agree with you but the main thing g here, IMO, is the friction with all the alternatives you mention in getting something working.
I would venture a guess signing up for Zapier is easier than getting OpenClaw up and running. Who can get a container running on a Mac but can't sign up for a SaaS product?
Because not even Amazon or Google offers every service that the typical user wants. One has to maintain accounts at a variety of places for email, office, automation, etc, etc.
I was using SyncThing, and it worked, but any time you have an Obsidian vault open on two devices, or shortly after another, you're always thinking about if you're going to have to clean up a bunch of sync conflict files later. And that mental overhead is not worth saving $4/mo.
The conflicts are never hard: it's like a git merge conflict where you just take the latest of every conflict block.
I used multiple sync "solutions" (terrible idea, in retrospect); Dropsync, Syncthing, Drivesync, in addition to paying for Obsidian Sync, because I was delusional about "backing up my data". Huge mistake on my part, I've spent many, many, many hours deduplicating worthless "backups". Agree with "just pay for Obsidian Sync".
I try to selfhost most of my stuff I rely on. Immich, Vaultwarden, etc. I gave up on trying to selfhost sync solutions for Obsidian - Obsidian Sync is just so damn frictionless compared to all other solutions. Also, it feels good supporting the development of Obsidian.
If you don't have the experience you can't provide it with stylistic guidance, or idiomatic patterns or provide examples to direct it.
This leads to the idea that LLMs with existing languages can't really learn new idiomatic patterns.
For new engineers I think new paradigms will emerge that invalidate the need to know the current set of design patterns and idioms. Look at the resurgence of unit tests or the new interests in verification systems.
Package situation on anything that isn't Arch (and I think Fedora) is pretty rough. I installed it from source. It helps that it is a rust application and was up and running in no time
Moved onto Niri yesterday after having to reinstall my PopOS and it just clicked. Like i3wm did all those years ago.
I can focus for hours on end and spend zero mental energy on resizing a window. I had less of that with i3wm but you had to always readjust after a few windows were tiled to your workspace. That final bit of cognitive overload was removed with Niri.
EDIT:
Spec: RTX 3090, Pop OS 24.04 (beta), 4K 43" Monitor,
Niri Installed from cargo build, super easy install, make sure you install xwayland-satellite so that you can run VS Code, Obsidian, Zoom, Blender and other strictly X11 applications
On most projects you end up wiring up a bunch of custom logic to handle your config, which is often injected as environment variables - think loading from a secure source, validation logic, type safety, pre-commit git scanning, etc.
It's annoying to do it right, so people often take shortcuts - skip adding validation, send files over slack, don't add docs, etc...
The common pattern of using a .env.example file leads to constant syncing problems, and we often have many sources of truth about our config (.env.example, hand-written types, validation code, comments scattered throughout the codebase)
This tool lets you express additional schema info about the config your application needs via decorators in a .env file, and optionally set values, either directly if they are not sensitive, or via calls to an external service. This shouldn't be something we need to recreate when scaffolding out every new project. There should be a single source of truth - and it should work with any framework/language.
