Andrew Lamichhane
760 posts

Andrew Lamichhane
@azeus333
Full stack dev and Zig enthusiast who loves tinkering with tech and exploring. On a side note, I really like eggs. #FullStack #Zig #TechTinkerer
Chennai, India Katılım Nisan 2022
288 Takip Edilen683 Takipçiler

@ppok24 Yes its a node binary, there's react core components which is not web agnostic I think, and the react Dom for web renders, but for tui they use ink as the renderer
English

@azeus333 technically it's a node binary right? since react is a framework for the frontend (correct me if i'm wrong)
English

@itsabhiyan A single session of claude code might be 300+ mb and when you add mcp into the equation that's just crazy, shipping fast should be priority for any company but they gotta have a set of standards too fr
English

@azeus333 yeah... if it was a startup about AI agentic CLI tool, then may be you could consider, because you NEED to ship fast.
but this just doesn't make sense. from any point of view. People at claude can't be this bad...
English

@itsabhiyan Honestly this is just bad engineering, and all companies and engineers accept it due to its popularity.
Javascript for everything isn't a joke anymore and now we have next js shipping with a compiler
English

@azeus333 yeah... looking at bugs people are facing and all... it shows
and codex took the route of minimalism
claude code took the route of cramming all the features
not testing them properly before shipping
facing consequences
English

@itsabhiyan From what i have gathered it's mostly because of the vast amount of data available on typescript so it's easy to vibe code and ship faster(claude-code, opencode etc)
The approach that codex took is way better, i guess its just poor decision of javascript frankenstein
English

@azeus333 yeah... I never got that reason, and they boast making it faster.
You are building a TUI, not just CLI.
If CLI, it would make sense... to just use for convenience. But TUI doesn't make sense to me.
Not in the slightest. Unnecessarily heavy and slow
English

We can finally retire the 'Java is too slow' meme.
It's 2026 and Netflix is running 3,000–4,000 production services on Java with near-zero GC pauses
Amazing talk!
youtu.be/ucJTPda_zx0

YouTube
English

Fixed the issue. Turns out it was a Gazebo sim bug: camera_info follows the REP 103 standard, but point cloud generation in Gazebo sim doesn’t.
There are two possible approaches:
1. Use a additional frame to make it align with rep 103
2. Use depth_image_proc(i chose this one)

Andrew Lamichhane@azeus333
Okay i don't understand why this is happening, i set the camera according to rep 103(z forward[points to the scene], x right, y down)
English


I also read Karpathy’s recent post on his LLM Wiki / knowledge base approach and I’m tempted to experiment with it as the core of long-term memory combined with a minimal RAG system.
Anyone else playing with similar memory designs? Would love thoughts.
(3/3)
#buildinpublic
English











