Recent submissions

Comment · 4 months ago
I run a small makerspace for kids and teens in Norway, and we kept hitting the same wall: the 3D tools we tried were either too fiddly for a 9-year-old or locked behind installs and accounts. So I built Akse — a browser-based 3D modeller for beginners, where the path from idea to a printable STL is as short as I could make it.

It's deliberately limited, but with a rather powerfull 2D Blueprint mode where you draw an outline on millimetre paper and extrude it to 3D. You build by placing and combining primitive shapes (box, cylinder, sphere, cone, pyramid, wedge, torus), set any shape to "hole" mode to cut it out of another. Everything is in real millimetres, so what's on screen matches what comes off the printer. Output is a single STL. That's most of it — no parametric constraints, no assemblies, no fillets. For teaching beginners that's intentional, not a gap.

The obvious comparison is Tinkercad — same space (primitive-based, browser, education-oriented), and I'm not claiming Akse is better. The differences are that it's open source, embeddable as a Svelte component, works in Norwegian as well as English, and is even more stripped down. It mostly exists because I wanted something I could shape around how our workshop actually runs, and put in front of Norwegian-speaking kids without an account or install.

Under the hood it's a Svelte 5 component using Three.js for rendering and three-bvh-csg for the boolean operations; storage goes through a small port interface so it's backend-agnostic, and the standalone version just uses localStorage. It's early (v0.1) and has rough edges. I'd really value feedback on where it trips up first-time users, since that's the entire point of the thing.

Source (AGPL-3.0, with a commercial option): github.com/joachimhs/akse3d

Comment · 2 years ago
This library provides a cache store for Svelte applications that simplifies fetching, creating, updating, and deleting items from a REST API that adheres to the simple-json-api specification. It also supports side-loading of related data and automatic cache management.
Comment · 2 years ago
I find myself implementing similar backend APIs when I develop applications. These APis are more often than not based on REST principles with JSON payloads. As a result, I have publised the start of a simple JSON API spec at http://simple-json-api.com. This specification makes it easy to write both backend and frontend code to handle the data communication between the applications in a uniform manner. This approach makes it possible to write a fairly small amount of code to get advanced functionality on the frontend-data-layer.

While some good API specifications do exist, this project attempts to provide a common middle-ground being not too complex, while broad enough to not be too specific and too complex.

While, for instance, JSON:API is a thorough specification, Simple JSON API aims to provide a much simplified data-structure leaving the server-side specifics out of the specification. At the same time, while specifications such as JSON Web Key (JWK) is too narrow.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton