Recent submissions

Comment · 3 months ago
Comment · 4 months ago
what do you mean?
Comment · 4 months ago
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.

Comment · 7 months ago
tip: your git repo's description (not readme, repo description) does not link the website. It should.
Comment · 7 months ago
this looks insanely cool.

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

Comment · 8 months ago
This is not the technical solution you want, but I think it provides the result that you want: https://github.com/devcontainers

tldr; devcontainers let you completely containerize your development environment. You can run them on Linux natively, or you can run them on rented computers (there are some providers, such as GitHub Codespaces) or you can also run them in a VM (which is what you will be stuck with on a Mac anyways - but reportedly performance is still great).

All CLI dev tools (including things like Neovim) work out of the box, but also many/most GUI IDEs support working with devcontainers (in this case, the GUI is usually not containerized, or at least does not live in the same container. Although on Linux you can do that also with Flatpak. And for instance GitHub Codespaces runs a VsCode fully in the browser for you which is another way to sandbox it on both ends).

Comment · 8 months ago
oh no! but that makes sense. I did post it on Lobste.rs myself
Comment · 8 months ago
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.

Comment · 8 months ago
honestly, I interpreted your comment as "Taskwarrior is unusable shit" since it had a pretty negative tone and came from a user named throwaway27448.

Actual accessibility is a different topic. Honestly I don't know much about the a11y of CLI apps in general. Is there something that makes Taskwarrior bad in that regard? Is it about the way it forms things like list outputs or tables?

Comment · 8 months ago
nope! why?
Comment · 8 months ago
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=-

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton