Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
rellfy
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
rellfy
2mo ago
Can't be worse than an Electron app, can it? lol
2.
▲
by
rellfy
3mo ago
You can just build things
3.
▲
Show HN: TIL – a timeline file format with a spiral viewer and editor
(til.rfy.nz)
3 points
by
rellfy
4mo ago
|
1 comments
4.
▲
by
rellfy
4mo ago
Well, I think the author correctly identifies productivity as a vector instead of a scalar. But perhaps a better title would be "Productivity Isn't (Only) About Going Faster"
5.
▲
by
rellfy
5mo ago
I didn’t mean it as fact. “Could turn out that …”
6.
▲
by
rellfy
5mo ago
Well, (in our current understanding) yes, but there may be underlying aspects of physics and the universe that we do not understand that could be the reason consciousness kicks in. It could turn out that LLMs do work similarly to how humans
7.
▲
by
rellfy
5mo ago
Are you implying consciousness is magic? Well, I wouldn't disagree with that really.
8.
▲
by
rellfy
6mo ago
This is a great concept. I fully agree with small, focused and composable design. I've been exploring a similar direction at asterai.io but focusing more on the tool layer than agent layer, with portable WASM components you write once
9.
▲
by
rellfy
6mo ago
I don't think AI coding means you stop being a craftsman. It is just a different tool. Manual coding is a hand tool, AI coding is a power tool. You still retain all of the knowledge and as much control over the codebase as you want, sa
10.
▲
Show HN: Asterbot, AI agent where every capability is a sandboxed WASM component
(github.com)
2 points
by
rellfy
7mo ago
|
0 comments
11.
▲
by
rellfy
7mo ago
I've spent my weekend building asterbot: https://github.com/asterai-io/asterbot Asterbot is a modular AI agent where every capability (such as tools, memory, LLM provider etc.) is a swappable WASM component. Compo
12.
▲
Show HN: Asterbot – AI agent built from sandboxed WASM components
(github.com)
1 points
by
rellfy
7mo ago
|
0 comments
13.
▲
by
rellfy
7mo ago
That's a great idea, it makes a lot of sense for dynamic use cases. I suppose I'm thinking of it as a more elegant way of doing something equivalent to top-down agent routing, where the top agent routes to 2-legged agents. I'
14.
▲
by
rellfy
7mo ago
Yes, I definitely think it's much faster than writing it manually. For a few weeks now, >95% of the code I've authored wasn't written manually. Sometimes you only care about the high level aspect of it. The requirements an
15.
▲
by
rellfy
7mo ago
The lethal trifecta is the most important problem to be solved in this space right now. I can only think of two ways to address it: 1. Gate all sensitive operations (i.e. all external data flows) through a manual confirmation system, such a
16.
▲
by
rellfy
8mo ago
I arrived at a very similar conclusion since trying Claude Code with Opus 4.5 (a huge paradigm shift in terms of tech and tools). I've been calling it "zen coding", where you treat the codebase like a zen garden. You maintain
17.
▲
by
rellfy
8mo ago
In my example above I wasn't referring to AI composing the tools, but you as the agent builder composing the tool call workflow. So, I suppose we can call it AI-time composition vs build-time composition. For example, say you have a sh
18.
▲
by
rellfy
8mo ago
Shell commands work for individual tools, but you lose composability. If you want to chain components that share a sandboxed environment, say, add a tracing component alongside an OTP confirmation layer that gates sensitive actions, you nee
19.
▲
by
rellfy
8mo ago
I really like the capability enforcement model, it's a great concept. One thing this discussion is missing though is the ecosystem layer. Sandboxing solves execution safety, but there's a parallel problem: how do agents discover a
20.
▲
by
rellfy
8mo ago
I agree, that's the main issue with this approach. Long-term, it should only be used for truly sensitive actions. More mundane things like replying to emails will need a better solution.
21.
▲
by
rellfy
8mo ago
I don't think you're being too harsh, but I do think you're missing the point. OpenClaw is just an idea of what's coming. Of what the future of human-software interface will look like. People already know what it will lo
22.
▲
Your Own AI Developer on GitHub
(rellfy.com)
1 points
by
rellfy
8mo ago
|
0 comments
23.
▲
by
rellfy
8mo ago
The only solution I can think of at the moment is a human in the loop, authorising every sensitive action. Of course it has the classic tradeoff between convenience and security, but it would work. For it to work properly, the human needs t
24.
▲
by
rellfy
8mo ago
I don’t think it’s wrong to see it as Anthropic’s constitution that Claude has to follow. Claude governs over your data/property when you ask it to perform as an agent, similarly to how company directors govern the company which is th
25.
▲
by
rellfy
8mo ago
By that same logic, humans would not be able to do anything novel either.
26.
▲
by
rellfy
8mo ago
I think this hasn't been yet achieved because components need to interface with each other easily. This requires a standard that all components implement, from which everything can be assembled together. From that perspective, the idea
27.
▲
by
rellfy
1y ago
n=3
28.
▲
by
rellfy
1y ago
What problems have you had with joins? I have this comment in one of my projects: ``` It is required to mark left-joined columns in the query as nullable, otherwise SQLx expects them to not be null even though it is a left join. For more in
29.
▲
by
rellfy
1y ago
I've always liked the concept of ECS, but I agree with this, although I have very limited experience with Bevy. If I were to write a game in Rust, I would most likely not choose ECS and Bevy because of two reasons: 1. Bevy will have lo
30.
▲
by
rellfy
1y ago
Thanks! That's a good question. Currently, there is one way to do it. The client querying the agent receives JSON-encoded values that are returned from plugin function calls made by the agent. These values are received alongside the ag
More ›