What I want you to do is this:
- Install playwright and chromium headless to take screenshots of https://explainers.blog/posts/why-is-the-sky-blue/ and interact with the page to deeply understand its style, aesthetics, tone, interactivity, visuals, fonts, etc.
- Make comprehensive notes of what you observe so you can implement EXACTLY that when building your explainer
- Then on the topic provided below plan to build an explainer with similar length, quality, interactivity, writing style, fun, informative as the article given - produce animations in svg (or otherwise) and interactions as necessary. Similar colour scheme but fun/vibrant/happy. Be very very creative. Act like an expert UI/UX designer who can build stunning explainers. Target it for intelligent hacker-news reader.
- Get your plan verified by codex
- Produce page one small change at a time. Don't output big chunks in one go. But pay extra attention to number of sections and length of the explained. I want it to be as comprehensive as possible (don't skimp on length)
- Keep testing what you produce via playwright on chromium headless.
After you’re finished with index.html, can you check via chromium that all animations, diagrams and interactions that they match with their captions and are visually ok (not too small, large, overlapping, etc.). Sometimes there are factual errors in what the caption or text says and what the diagram suggests.
I try my best to push ML things into WebGPU and I think it has a future, but performance is not there yet. I have little experience with Vulkan except toy projects, but WebGPU and Vulkan seem very similar
I agree. I don't understand there are so many software engineers who are excited about this. I would only be excited if I was a founder in addition to being a software engineer.
This is hilarious, 5 years ago I built a very similar cli tool based on the same idea and with the same name (whosthere but in Polish, ktotu [0]). I wonder if you used AI to generate the project and the idea
Congrats for the execution, it looks more complete and feature rich and Go is a better choice for sure
Performance is not there yet, honestly. I haven’t focus on running things fast, but it’s one of next directs steps I’ll take. The problem with running it in a browser is that we need to find a way to run the PyTorch itself in a browser and to my best knowledge it’s not there yet. I’m looking at it to close the gap, feel welcome to reach out to collaborate if you’re interested!
reply