I use a tiling window manager to manage each task (/workflow/issue/ticket) on a separate (visual) workspace with its own isolated container/git worktree that is bound to it.

I name my workspaces to match the task, so it's easy to find all terminal sessions/apps related to one task; then I only have to be able to find a session/app within the task. And i3wm supports tabs, the tab title automatically set by most AI agents and apps to be something helpful, so it's trivial to find.

Thought this is not sth even AI specific, it's not really AI specific, it is just super useful for multi-tasking in general way beyond coding tasks as well. I first started automating this flow 6-7-ish years ago as i3-env: https://github.com/kantord/i3-env thought since I tried to rewrite that a couple times because debugging bash scripts was not so much fun; I'm kinda settling on a well-made and portable system now, though it's not well documented yet.

what do you mean?

They're answering the question posed in the article: No, programmers won't write more efficient code.

They're suggesting that instead, consumers will just be forced to pay more for inefficient SaaS products being run on more expensive infrastructure.

For this incentive to exist, the app needs to be such an obvious memory hog that users start identifying it as the source of the problem.

Even then, a lot is required for most businesses to prioritize this (presumably) temporary issue at the cost of things like: participation in the AI race, other features, bug fixes, new markets etc.

Heck, sometimes software is so inefficient that it costs developer and tester productivity but a fix is not prioritized for years.

Your response suggests that you're only considering native apps where users can view memory usage.

For cloud apps where the costs are largely hidden from users, the user has no way of doing that analysis. I agree with the second part of what you said, though: I expect businesses to just raise their prices in those cases rather than systematically focus on actual difficult engineering problems.

For cloud apps incentives are aligned already. The cost of memory usage falls on the people who are both paying for it and can control it. It's only really on end user devices where it's a problem, and only really on desktop class machines. iOS and Android were built in a RAM starved environment anyway and aggressively kill any non-foreground process that is using too much memory.

tip: your git repo's description (not readme, repo description) does not link the website. It should.

Also fill the Website field in About section.

this looks insanely cool.

One of the most original ideas I have seen on HackerNews in the past few years.

This is interesting (and I've seen it mentioned in some editors), but how do I use it? It would be great if it had bubblewrap support, so I don't have to use Docker.

Do you know if there's a cli or something that would make this easier? The GitHub org seems to be more focused on the spec.

interesting, this is basically what Venkatesh Rao pointed out back in 2013: https://www.ribbonfarm.com/2013/07/10/you-are-not-an-artisan...

Basically we do not rationally analyze what work can be automated and what work is forever safe. We just assume that "sexy work" is safe, and work backwards to figure out how to explain this belief to ourselves.

Such a fascinating blog post! At first I could not believe it was written in 2013. But the more I think about it, the less I understand what he is actually trying to say. Anyway, the point that we (erroneously) see less prestigious jobs as more automatable is spot-on

there might be some gaps (let me know) but you can actually pipe the output to another program.

for instance here's how you'd download all the unread blog posts by combining blogtato and wget:

blog .unread read | wget \ --recursive --level=1 \ --page-requisites \ --convert-links \ --adjust-extension \ --no-parent \ --directory-prefix="$HOME/offline-posts" \ --input-file=-

Oh sweet. I always appreciate having the ability to script this kind of thing.

I was considering adding a full offline mode but here is my thinking: that is actually a feature/concern that would be separately useful, so it should not be baked into blogtato. And there might be already some pretty good options out there.

For instance, `wget` is a pretty widely used HTTP client that is able to mirror links for offline access. Then you can use standard tools such as `grep` to search in all the offline content. And `blogtato` does already have an export feature, so it is almost trivial to write a script that saves all posts for online content.

So perhaps what should be done here is find a user friendly tool for offline access/search for web content and just add some convenience features to `blogtato` so that they integrate very easily.

i do not find the interface of taskwarrior inaccessible at all, i actually really love using it and find it largely intuitive. Not necessarily for doing super complex stuff, but that is not something I ever wanted anyways