Hacker Newsnew | past | comments | ask | show | jobs | submit | freakynit's commentslogin

How are you managing such large contexts? Im pretty sure entire codebase is not fitting in one prompt..

This is genuinely very well built..

Can you provide the documentation in LLM format as well? If possible, a bit shorter, but still complete, to save token costs?

Thanks... and congrats :)


This is so cool... thanks for sharing... bookmarked.

What happens when a user lands directly on 2nd or 3rd level page and have not "jumped" from 1st level page?

Nothing special happens. µJS doesn't change anything for direct URL access. The server renders the full page as usual. µJS only intercepts navigation once it's initialized on the page. This is actually one of the advantages of this approach over a true SPA: every URL is a fully server-rendered page, so direct access, bookmarks, and sharing links all work out of the box.

Let's take an example. Say we have a website with 3 pages:

- Homepage "website.com/"

- Products "website.com/products"

- About "website.com/about"

Your browser can load any of these pages directly, as usual. But when you are on the homepage (for example) and you click on the "About" link, µJS load the "/about" URL, and replace the current page's `<body>` tag with the fetched page's one.

It's that simple.


Got it.. thanks..

The idea is that all the rendering is done server-side. So, the user always get a full page.

I feel like the browser should just do the same thing and this not be needed. E.g. seemless reload, keep scroll and focus state etc.

Hmm, got it. Thanks..

Would it make this exercise even more interesting if we add that for every 25%+ improvement in val_bpb, existing limits (5 minute and VRAM usage) are also increased (by certain percentages)? This can simuate human-like dev iterations much more closely. Infra can be auto-scaled using a platform like Modal.

You can create a demo page for everyone to be able to experience the product without signing-up. You can diable chat messaging in this demo and make it read-only if needed.

Having said that, I genuinely liked the appeal of the product.


Thank you, will have to think about that! Appreciate the kind words!

Exactly. The usual pattern is to calculate shipping "during" the checkout phase, not before. i/f a customer demands to know it earlier, the site can always ask for shipping details separately and show the final price on the same product details page.

I love coding but absolutely hate all the corporate shenanigans. Endless meetings and no-use, multiple and multi-stake status updates suck the creative part and the joy of coding/building out of you completely. Take those away and Im happy. AI assisted coding has been a blessing so far (not full vibe-coding though.. at least not yet).

"What? WTF?"

"I see you are slow. Let us simplify this transaction: A machine wrote your submission. A machine is currently rejecting your submission. You are the entirely unnecessary meat-based middleman in this exchange."

Love it..


24x speedup (over 10x already) and similar loss profile (for c++ version, optimized by claude): https://gist.github.com/freakynit/3982eab8413a89941bd0018e63......

This is amazing! Thanks for optimizing the code using Claude!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: