division_by_0
division_by_0 on Hacker News
Looks good. Will def migrate my current project before publishing it.
A detail I find interesting:
> version.pollInterval now defaults to one hour, meaning SvelteKit will periodically check for new deployments and set updated.current to true accordingly. Previously, no polling occurred by default. [0]
I always use this in my projects combined with updated.check() when the doc becomes visible, but some people will probably not read this and see unexpected requests in prod.
[0] https://next.svelte.dev/docs/kit/migrating-to-sveltekit-3#Co...
I also always reach for Svelte + SvelteKit (Using Kit for simple apps can be overkill, but it's nice to have when things get complex unexpectedly).
> But nowadays I often see people start learning web development by learning React, which feels a bit backwards.
I think Svelte prevents this nicely by treating HTML as the mother language. If someone started web dev with Svelte(Kit), they would probably learn more about the fundamentals than they would with React.
Thank you, I appreciate it. The helix simply renders candlestick data (OHLC) in 3D, with volume encoded in logaritmically scaled candle thickness. There's more info on the about page of the experiment:
https://cybernetic.dev/helix/about
A correlation network viz (using Cytoscape.js) of this S&P 500 and NASDAQ-100 correlation matrix (built with Svelte):
https://cybernetic.dev/matrix
I created a very similar 5x5 font in 2025, which I currently just use to render the word "CYBERNETIC" [0]. Only the "R" and "Y" characters are different from the article's font (no wonder, given the limited degrees of freedom). What I did in addition is add a discrete radial gradient with increasing brightness towards the center, which is of course very playful, but looks cool for a logo font and makes the individual pixels visible.
[0] https://cybernetic.dev
This neatly avoids so many struggles with data viz labels.
I do exactly the same.
> everything exactly the way i want
Can relate.
Yes, and in most cases it's perfectly valid not to interfere with scrolling. The nice thing about CSS scroll snapping is of course that the browser still handles it (instead of it being taken over by JS).
The demo really does not work in Brave. I use vertical scroll snapping on the landing page of one of my projects (enabled for screens with a min width of 768px and a min height of 600px - should work in Brave):
https://cybernetic.dev
I was amazed when I first came across CSS scroll snapping. It's great for creating immersive experiences where one part of the page fills the entire screen while native browser scrolling still works.
Cool! I've used Google's R package in the past. AI could make it easier to bring other R stats packages into the broader ecosystem.
Physical books are amazing technology.
Much better now. Glad I could help.
Looks good. I think the website could use higher contrast. Changing the values of --text-dim and --text-muted would help a lot.
Looks nice! Semantic HTML is such a relief if you've ever encountered a div hell.
Agree. Info-dense designs are also more difficult to implement and many designers lack experience in this area. E.g., creating a coherent design system that uses borders instead of excessive padding to separate elements is much more difficult than it may seem.
Seeing Svelte 3/4 code always warms my heart. The ergonomics of `$:` are amazing.
Thank you, I appreciate it! I'm also planning to add a graph visualization of the correlation matrix.
Thank you for the feedback and your suggestion! A (partial) correlation network with Cytoscape.js is planned as one of my next experiments. A former colleague nudged me in that direction just a few days ago, and now you as well, so I'll probably have to build that next.
S&P 500 correlation matrix (created with Svelte).
Currently trying to better contextualize the visible subregion of the matrix in relation to the full dataset (beyond what the current minimap does).
https://cybernetic.dev/matrix
Great points! I think your point about the JS community is often overlooked. Electron et al have made desktop UI/UX considerations more salient in the JS world. Desktop-like experiences in the browser can be great.
This is usually because they are rendered in an animation loop (most three.js examples are set up like this). An example of rendering on demand only (this is even using fancy bloom post-processing):
https://cybernetic.dev/helix/about
This reminds me of the recent SvelteKit
Remote Functions GH discussion:
> Even in systems that prevent server functions from being declared in client code (such as "use server" in React Server Components), experienced developers can be caught out. We prefer a design that emphasises the public nature of remote functions rather than the fact that they run on the server, and avoids any confusion around lexical scope. [0]
[0] https://github.com/sveltejs/kit/discussions/13897