For me, this is not gonna be a daily driver but more of the one off screenshot browser so that my screenshots look super minimal with no popular browser shell in them :)
Looks cool, but the readme is AI-generated. Absent throwing my own Fable/Astra at this and hoping it finds any bugs, how does one decide whether to trust AI-assisted software these days?
You don’t. LLMs make vibe coding highly customized software that operates exactly as the user wants it super easy, which is awesome. However humans still haven’t caught up to the idea that it doesn’t need to go on GitHub because if it was useful to somebody, they’d have already vibe coded it themselves.
How does one decide whether to trust any software? Not just the small things we do have the source code for, but big things that we don't have the source code for? I don't think this is a new problem.
After a significant number of iterations of testing, and improving it. When we wrote code by hand, something like changing an api endpoint or a simple front end change would still involve dozens of "write code" then "retest manually". This would not only get the work item done, but you would often encounter edge cases or other issues you hadn't thought of when writing/reading the ticket.
When AI can one shot the implementation and testing, it likely only gets 1 round of human testing if you are lucky. Then scale this to an entire AI generated project, the ratio of features to manually run tests is astronomical. In the old days this ratio was inverted, and the tool has been battle tested before reaching any users.
Nothing is foolproof, but signals can go a long way. If an app's UI is poorly considered or comes across as careless for example there's a good chance that its other aspects are like that too.
We used to say, use an open source product and inspect and compile it yourself.
Now endless frameworks and everything make that impossible. So the next step is probably to describe the thing you want to your own AI, in plain English, and have it code it itself.
Of course that will only work until we start using frameworks and everything…sigh.
Also a nice Webkit browser on macOS: https://duckduckgo.com/mac (https://news.ycombinator.com/item?id=33246158)
For me, this is not gonna be a daily driver but more of the one off screenshot browser so that my screenshots look super minimal with no popular browser shell in them :)
https://zen-browser.app/ - if you would like a super minimal daily driver
Looks cool, but the readme is AI-generated. Absent throwing my own Fable/Astra at this and hoping it finds any bugs, how does one decide whether to trust AI-assisted software these days?
You don’t. LLMs make vibe coding highly customized software that operates exactly as the user wants it super easy, which is awesome. However humans still haven’t caught up to the idea that it doesn’t need to go on GitHub because if it was useful to somebody, they’d have already vibe coded it themselves.
How does one decide whether to trust any software? Not just the small things we do have the source code for, but big things that we don't have the source code for? I don't think this is a new problem.
After a significant number of iterations of testing, and improving it. When we wrote code by hand, something like changing an api endpoint or a simple front end change would still involve dozens of "write code" then "retest manually". This would not only get the work item done, but you would often encounter edge cases or other issues you hadn't thought of when writing/reading the ticket.
When AI can one shot the implementation and testing, it likely only gets 1 round of human testing if you are lucky. Then scale this to an entire AI generated project, the ratio of features to manually run tests is astronomical. In the old days this ratio was inverted, and the tool has been battle tested before reaching any users.
Nothing is foolproof, but signals can go a long way. If an app's UI is poorly considered or comes across as careless for example there's a good chance that its other aspects are like that too.
We used to say, use an open source product and inspect and compile it yourself.
Now endless frameworks and everything make that impossible. So the next step is probably to describe the thing you want to your own AI, in plain English, and have it code it itself.
Of course that will only work until we start using frameworks and everything…sigh.
FWIW, I checked and this app uses zero frameworks.
So it can be easily inspected, checked, verified.
What could go wrong?