smy20011

That's what you got from 200$ claude sub.

The way Claude did it is fight entropy with entropy.

"Add a static composer into the HTML" <- This seems like something can be done with SSR?

"For faster navigations, we kept the composer mounted between conversations" <- Your SPA should cache this between pages, why fetching it every time? Or you need better routing for your react components.

"cheap first-character check before the regex" <- Should we cache compiled Regex instead?

I think even 1.3 sec to load the front page is unacceptable. Something need to be reworked from basics (SSR, chunk-based rendering) to solve the problem. Focusing on invidual benchmarks may miss the opportunity.

Love to see a blog about it!

Why do the ChatGPT posters always have a lot of dividers? No matter how you change the style, it's always there.

Even if we can proof/disproof any statement in Math (not possible due to halting problem), Human still need to decide which statement to be called "theorem".

The theorem thing is invented by human to help other people better understand Math structure in a easier way.

The good thing is that we no longer consider RAM is free and forced to develop more efficient program (hopefully)

Removed

Do you plan to open source it? Seems like a proprietary app & spec.

Seems fully vibe coded :(

The "What makes it different" feels so AI-generated :(

Nah, if you not feeling fun coding a project, just use your free time on other stuff that you interested in.

OpenClaw IMO, It's a such big mess that only agent can operate it.

Very clean, thank you for posting!

I was wondering to build the same thing but someone already built it. I just need some agent that open/close super fast and don't eat half a gb of memory.

Can we stop treating llms as some conscious being? It's a function of weight + context and you can copy the behavior by copying the context. Therefore, their collaboration behavior is mostly the same.

You can simulate this by having a jj repo with file system watches.

Super cool, thank you for sharing!

> This post is 100% human-written. Claude was used for feedback and to assist with the linker symbol diagram. Cursor was used for feedback and to ensure examples were compilable.

Love this, I hope every blog have the same disclaimer about how AI is used.

It will pay for itself if you spend >300$ per month. I personally wish Waymo have a 399$ per month subscription that give 2 free ride per day so I don't need to own a car just for work.

At least easier to filter I think.

Agree, AI generated articles & comments provide little to none value other than the original prompt. Please just post the original prompt instead.

I will not put it into a ladder. It implies that the higher the rank, the better. However, you want to choose the best solution for your needs.

An outage could cost Amazon ~millions to tens of millions. Most of the time, we want the junior to learn from the outage and fix the process. With AI agent, we can only update the agent.md and hope it will never happen again.

Just multibillion?

It interesting to see that the eval set becoming more and more expensive. Previously we just need to evaluate one test set, right now we need to create a lot of diffs and run a lot of tests.

Nice to see a AI coding tool that not (complete) vibe coded! Well done.

Are we reinventing RPC again? Calling CLI program with JSON sounds like RPC call. The schema feels likes something LSP can provided for such function.

Maybe asking agent to write/execute code that wraps CLI is a better solution.

I think the good thing about it is that if you are given good specification, you are likely to get good result. Writing a C compiler is not something new, but it will be great for all the porting projects.

I miss entering flow state when coding. When vibe coding, you are in constant interruption and only think very shallow. I never see anyone enter flow state when vibe coding.

I think It's not because AI working on "misaligned" goals. The user never specify the goal clearly enough for AI system to work.

However, I think producing detailed enough specification requires same or even larger amount of work than writing code. We write rough specification and clarify these during the process of coding. I think there are minimal effort required to produce these specification, AI will not help you speed up these effort.