The idea is very compelling, it solves a real use-case. I will definitely take inspiration from that.

However, the execution is meh. The UX is terrible (on mobile at least) and the code and documentation are an overly verbose mess. The entire project ought to fit in the size of the AI generated readme. Using AI for exploration and prototyping is fine, but you can't ship that slop mate, you need to do the polishing yourself.

▲

haasiy 9 hours ago | parent [-]

I intentionally used AI to draft the README so it's optimized for other AI tools to consume. My priority wasn't 'polishing' for human aesthetics, but rather hitting the 15KB limit and ensuring 100% client-side execution. I'd rather spend my time shipping the next feature than formatting text.

▲

littlestymaar 7 hours ago | parent [-]

First, you're misunderstanding what I mean by “polishing”, I'm talking about making sure it actually works.

Then, improving the signal to noise ratio of your project actually help “shipping the next feature”, as LLM themselves get lost in the noise they make.

Finally, if you want people to use your project, you need to show us that it's better than what they can make by themselves. And it's especially true now that AI reduces the cost of building new stuff. If you can't work with Claude to build something better that what Claude builds, your project isn't worth more than its token count.

▲

haasiy 7 hours ago | parent [-]

I have to stand my ground here. Reducing a complex functionality into 15KB is not just about 'generating code'—it's about an architecture that AI cannot conceive on its own.

My role was to architect the bridge between UI/UX design and the underlying video data processing. Handling frame extraction via Canvas, managing memory, and ensuring a seamless seek experience without any backend support requires a deep understanding of how these layers interact.

Simply connecting a backend to a UI might be common, but eliminating the backend entirely while maintaining the utility is a high-level engineering choice. AI was my hammer, but I was the one who designed the bridge. To say this is worth no more than its token count ignores the most difficult part: the intent and the structural simplification that makes it usable for others in a single line of code.

▲

littlestymaar 6 hours ago | parent [-]

> Reducing a complex functionality into 15KB is not just about 'generating code'—it's about an architecture that AI cannot conceive on its own.

Ironic.

	▲	haasiy 4 hours ago \| parent [-]
		なるほど、そこを引き合いに出すということはオレの反論に返す言葉が無いってことか？ Aiの言葉がトークンがコードが、どうこう言うからあえて母語で伝えてやるよ。しょうもないクレームにAIを使うのは今や世界標準だぜ？皮肉にもｗ