vergessenmir

I think we are all waiting for the open weights or local model releases.

They're both harnesses, pi + cron/event trigger is 90% openclaw

it's fast for the classes

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

The other thing is the

Just pay for the sync. I used to juggle with git, rsync, inotify etc and other tools

Its one of the few subscriptions where it actually feels like money well spent

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

See my comment above (moved from i3wm) but my spec is

RTX 3090, Pop OS 24.04 (beta), 4K 43" Monitor,

Nvidia cards worked out the box with no problems

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

Harbor has its pain points but it is infinitely easier to get up and running compared to crufty Artifactory.

One glaring omission is lack of support for proxy docker.io without the project name i.e pulling nginx:latest instead of /myproject/nginx/nginx:latest

The workaround involves URL rewrite magic in your proxy of choice

I don't get it, what does this do?

Is there any notable properties of this implementation, are some parts slower, faster etc

get work done, look younger and slice off the first 5 years of your experience because it is "not relevant". I look about 10-12 years younger so I am able to slip under the radar but it makes me wonder how my peers who look visibly their age fare? The job market is london, sector: Hedge funds, asset mangement tech etc.

Go is great for concurrency. Not quite there for agent support. The problem isn't performance or message passing it's the agent middleware i.e logging, tracing, retries, configuration

You need a DSL either supported in the language or through configuration. These are features you get for free in python and secondly JavaScript. You have to write most of this yourself in go