qudat

6 ms·

31.
by qudat 3mo ago
> I’d say that, in all the ways that matter, I understand the code. Sure, if I had to hand-edit it now, there’d be a serious learning curve. But I won't have to. Famous last words, but point is taken. The non deterministic nature of
32.
by qudat 3mo ago
It’s been great for llm + cli usage on mikrotik
33.
by qudat 3mo ago
The component trees have to be rewritten, only the non-view related JS code can be reused.
34.
by qudat 3mo ago
You can do damage tracking for TUIs. Printing to the terminal is done by moving the cursor and redrawing the line the cursor is on.
35.
by qudat 3mo ago
Very cool! I run a set of ssh-based services over at https://pico.sh and love seeing all the indie web content on HN! Sftp is still very useful even in 2026
36.
by qudat 3mo ago
There’s not much of a difference because open models are distilling from frontier models. If frontier models cease to exist then many of these open models will as well
37.
by qudat 3mo ago
I just use https://tuns.sh which has a handy bash script to make the ssh tunnel simple
38.
by qudat 3mo ago
> My main point is that following the spec doesn't guarantee shell scripts will be portable, which is a common misconception. That feels like a failure in the spec. Your example illustrates it: echo has unspecified behavior that lit
39.
by qudat 3mo ago
This is quite a timely post compared to: https://bower.sh/posix-shell-is-all-you-need This post was thought provoking, I wonder, is the hidden argument here that the posix spec for a shell is not well specified if there is
40.
by qudat 4mo ago
> Bindings are not IPC. The Deno runtime and the rendering backend run as threads / processes inside the same address space (CEF) or coordinated process group (WebView). Calls go through in-process channels, and the backend dispatch
41.
by qudat 4mo ago
Major props to Mitchell (and his family) for these donations.
42.
by qudat 4mo ago
I put my SS in there
43.
by qudat 4mo ago
Anyone know the song that's playing in the demo?
44.
by qudat 4mo ago
I feel like the claims come from wildly different personas and use cases. A 24gb vram, 5 year old titan run 27b at 30t/s and the results are good. I use sonnet and opus at my day job and they are more capable but I can still get the sa
45.
by qudat 4mo ago
I don’t bother with wrappers, why does it need to be easier than git clone + makepkg -i? Then I just update when I need to update
46.
by qudat 4mo ago
Excellent ad campaign by Anthropic
47.
by qudat 4mo ago
Preload is the answer to speed. Basically download the clients db on init and then have cache invalidation strategies. I built starfx to basically perform the data sync aspect of this paradigm https://starfx.bower.sh/learn#d
48.
by qudat 4mo ago
I really like this idea and have been experimenting with it over a week or so. I think there’s an opportunity to use an AST diff system for code forges where you don’t present the user with line diffs in the UI — or at least not as the firs
49.
by qudat 4mo ago
I'm still thinking this through but I was arguing this position to colleagues to some shock: LLM's are a race-to-the-bottom and frontier models will not be able to afford to work on coding specific models (or coding features at al
50.
by qudat 5mo ago
I built https://zmx.sh to make it easier to interact with your terminal sessions programmatically. 1 window = 1 session which might feel like a negative but it makes programmatic access easy and agents can use it just by pointin
51.
by qudat 5mo ago
And a labeling action which requires `pull_request_target`: https://github.com/actions/labeler#create-workflow These types of features are not worth it and need to be removed from the marketplace.
52.
by qudat 5mo ago
Literally the model “mythos” is being marketed towards finding these exact type of bugs used for exploitation. I really don’t understand the argument: are agents not good at findings memory management issues? What’s the gap?
53.
by qudat 5mo ago
My guess is it won’t be worth it to focus specifically on coding models once local small models work just as well or within range. That will naturally close the gap even more
54.
by qudat 5mo ago
Yep. I’m approaching the same problem from a different angle: writing code fast means you aren’t being thoughtful about the features you’re building. I started realizing that after I had kids and spent more time thinking about code than wri
55.
by qudat 5mo ago
Nah. These agents are getting easier and easier to run local. Have you tried Qwen 3.6 27b? It’s insane what it can do compared to its size. Like 100% vibe small projects if you manage context properly. These models are a race to the bottom
56.
by qudat 5mo ago
I don’t understand: just use an agent to find all memory leaks and segfaults. I don’t get the argument if you are gonna vibe code anyway. With unlimited tokens make it a lint rule or auto formatter.
57.
by qudat 5mo ago
We take a slightly different approach for https://pico.sh -- no automatic subscription, but we charge for an entire year. It's great for us because each sub is a year and if someone truly isn't using our services then
58.
by qudat 5mo ago
The entire concept that we need to cater CLIs to agents at all should tell us how far away they are from being “junior devs” or “an intern” and I reject the premise. A lack of structured output has never been a blocker for agents to work, t
59.
by qudat 5mo ago
I don't get it, it looks like they are copying data to the sandbox filesystem why would that impact production data? Because the agent can re-upload the file to s3?
60.
by qudat 5mo ago
Wild example as it has been corrupted by VC money as well. I wouldn’t touch deno either.

More ›