[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2zhbbsmr0tl6m":3},{"code":4,"message":5,"data":6,"timestamp":26},10000,"success",{"full_name":7,"position":8,"description":9,"language":10,"stars":11,"forks":12,"stars_gained":13,"age_days":14,"hn_threads":15,"one_liner":16,"summary_md":17,"topic":18,"github_topics":21,"license":22,"homepage":23,"updated_at":24,"history":25},"stackedlol\u002Fascii-sharks",4,"ascii shark components in typescript","TypeScript",810,62,151,5,[],"A zero-dependency TypeScript canvas engine that renders animated ASCII sharks and fish for ambient art and playful web pages.","## The problem\n\nThere is a small but persistent demand for ASCII art that is animated rather than pasted into a `\u003Cpre>` block: personal sites, terminal-themed dashboards, demo pages, and little ambient visuals. The README here is thin; it shows one drawn scene, names an `OceanEngine` class, mentions a fish and a shark `kind`, and states zero dependencies. Beyond that, the mechanics are documented mostly by the code itself.\n\n## What's different\n\nMost ASCII animation on the web is done either with hand-rolled `setInterval` string swapping, or by pulling in a full creative-coding library like p5.js and drawing text glyphs manually. This project takes the second path's idea but ships as a component: an `OceanEngine` takes a canvas and a list of entities and handles the drawing loop. That means you get animation and scene composition without a general-purpose engine. The trade-off is scope: this is an art piece and a small library, not a renderer with a documented API surface, and the README does not describe what else `OceanEngine` supports.\n\n## Who it's for\n\nFront-end developers who want an ASCII ocean aesthetic on a page and are willing to read the source to learn the API. It suits side projects, portfolio flourishes, and classroom demos of canvas loops. It is not for anyone needing stable public APIs, accessibility out of the box, or a general 2D animation library — use p5.js or a real game framework instead.\n\n## Cost of adoption\n\nTypeScript project, MIT licensed, and the README's only install path is `npm install && npm run dev`, which suggests it is currently consumed by copying files or by importing from `.\u002Fsrc` rather than from a published package. The snippet imports `.\u002Fsrc` directly, so expect to vendor the source. There are no topics, no homepage, and no stated runtime or platform requirements. Zero dependencies keeps the install small, but the project is five days old, so API stability is unknown.\n\n## Verdict\n\nThe repository was created in October 2026 and has about 800 stars after five days, with the new TypeScript board showing roughly +158 stars per day; that is a spike driven by the visual, not by evidence of production use. Nothing has hit the GitHub trending daily board and there is no Hacker News discussion, so attention is concentrated in one channel. The MIT license and zero dependencies make it cheap to try. Treat it as a charming starter rather than an established library: read `src`, expect the API to move, and do not build anything you cannot easily replace.",{"slug":19,"name":20},"media","Media & Design",[],"MIT",null,"2026-10-25T01:36:48Z",[],1792912793]