The best Hacker News stories from Show from the past day
Latest posts:
Show HN: Chili3d – A open-source, browser-based 3D CAD application
I'm currently developing Chili3D, an open-source, browser-based 3D CAD application. By compiling OpenCascade to WebAssembly and integrating Three.js, Chili3D delivers near-native performance for powerful online modeling, editing, and rendering—all without local installation. Access it here:<p><a href="https://github.com/xiangechen/chili3d">https://github.com/xiangechen/chili3d</a><p>Features:<p>Modeling Tools: Create basic shapes (boxes, cylinders, cones, etc.), 2D sketches (lines, arcs, circles, etc.), and perform advanced operations (boolean operations, extrusion, revolution, etc.).<p>Snapping and Tracking: Precisely snap to geometric features, workplanes, and track axes for accurate alignment.<p>Editing Tools: Modify (chamfer, fillet, trim, etc.), transform (move, rotate, mirror), and perform advanced edits (feature removal, sub-shape manipulation).<p>Measurement Tools: Measure angles and lengths, and calculate sums of length, area, and volume.<p>Document Management: Create, open, and save documents, with full undo/redo history and support for importing/exporting STEP, IGES, BREP formats.<p>User Interface: Office-style interface with contextual command organization, hierarchical assembly management, dynamic workplanes, and 3D viewport controls.<p>Multi-Language Support: Built-in i18n support with current languages including Chinese and English.
Show HN: Chili3d – A open-source, browser-based 3D CAD application
I'm currently developing Chili3D, an open-source, browser-based 3D CAD application. By compiling OpenCascade to WebAssembly and integrating Three.js, Chili3D delivers near-native performance for powerful online modeling, editing, and rendering—all without local installation. Access it here:<p><a href="https://github.com/xiangechen/chili3d">https://github.com/xiangechen/chili3d</a><p>Features:<p>Modeling Tools: Create basic shapes (boxes, cylinders, cones, etc.), 2D sketches (lines, arcs, circles, etc.), and perform advanced operations (boolean operations, extrusion, revolution, etc.).<p>Snapping and Tracking: Precisely snap to geometric features, workplanes, and track axes for accurate alignment.<p>Editing Tools: Modify (chamfer, fillet, trim, etc.), transform (move, rotate, mirror), and perform advanced edits (feature removal, sub-shape manipulation).<p>Measurement Tools: Measure angles and lengths, and calculate sums of length, area, and volume.<p>Document Management: Create, open, and save documents, with full undo/redo history and support for importing/exporting STEP, IGES, BREP formats.<p>User Interface: Office-style interface with contextual command organization, hierarchical assembly management, dynamic workplanes, and 3D viewport controls.<p>Multi-Language Support: Built-in i18n support with current languages including Chinese and English.
Show HN: I made a 3D networked open world automation game with no game engine
Over the last 4 years I've been developing Skyformer, including making all the art. Technical features include:<p>- OpenGL for graphics, OpenAL for sound, GLFW for input<p>- Terrain rendered using techniques inspired by REDengine 3 with a custom terrain/world editor.<p>- Networking framework for co-op with TCP + custom binary protocol<p>- Immediate mode UI framework, SDF text rendering<p>- Cascaded shadow mapping with soft shadows.<p>- Weather simulation (with my own fake physics)<p>- Dynamic skydome<p>- Water based on Gerstner waves<p>- Swept-sphere collision detection and response<p>- Soft-particles / transparency<p>- God rays<p>- Grass rendering<p>- FXAA, SSAO, Bloom<p>- etc.<p>You can ask me anything and let me know if you have any feedback. Thanks!
Show HN: I made CSS-only glitch effect
Show HN: Glowstick – type level tensor shapes in stable rust
Hi HN,<p>In the past few years I've become more interested in machine learning. Since I'm sure the same is true for many here, I wanted to share this project I've been working on: glowstick uses type-directed metaprogramming to keep track of tensor shapes in Rust's type system and determine which operations are permitted or not at compile time.<p>I find Rust has a lot of strengths when it comes to ML applications, but waiting until runtime to find shape related issues feels a bit strange since normally I don't run the code all that often while developing. Given Rust has fancy types available, I figured I'd try my hand at using them to address this.<p>I've added integration crates for the two ML frameworks I use most frequently, candle and burn, and included examples of implementing llama 3.2 in each using typed shapes for much of the model internals and inference loop. Mixtures of static and dynamic dimensions should be supported well enough for most applications at this point, though there are of course still improvements to be made.<p>Any feedback is appreciated!
Show HN: Somo – a human friendly alternative to netstat
Show HN: Somo – a human friendly alternative to netstat
Show HN: Munal OS: a graphical experimental OS with WASM sandboxing
Hello HN!<p>Showing off the first version of Munal OS, an experimental operating system I have been writing in Rust on and off for the past few years.<p><a href="https://github.com/Askannz/munal-os">https://github.com/Askannz/munal-os</a><p>It's an unikernel design that is compiled as a single EFI binary and does not use virtual address spaces for process isolation. Instead, applications are compiled to WASM and run inside of an embedded WASM engine.<p>Other features:<p>* Fully graphical interface in HD resolution with mouse and keyboard support<p>* Desktop shell with window manager and contextual radial menus<p>* PCI and VirtIO drivers<p>* Ethernet and TCP stack<p>* Customizable UI toolkit providing various widgets, responsive layouts and flexible text rendering<p>* Embedded selection of applications including:<p><pre><code> * A web browser supporting DNS, HTTPS and very basic HTML
* A text editor
* A Python terminal
</code></pre>
Checkout the README for the technical breakdown.<p>Demo video: <a href="https://streamable.com/5xqjcf" rel="nofollow">https://streamable.com/5xqjcf</a>
Show HN: Munal OS: a graphical experimental OS with WASM sandboxing
Hello HN!<p>Showing off the first version of Munal OS, an experimental operating system I have been writing in Rust on and off for the past few years.<p><a href="https://github.com/Askannz/munal-os">https://github.com/Askannz/munal-os</a><p>It's an unikernel design that is compiled as a single EFI binary and does not use virtual address spaces for process isolation. Instead, applications are compiled to WASM and run inside of an embedded WASM engine.<p>Other features:<p>* Fully graphical interface in HD resolution with mouse and keyboard support<p>* Desktop shell with window manager and contextual radial menus<p>* PCI and VirtIO drivers<p>* Ethernet and TCP stack<p>* Customizable UI toolkit providing various widgets, responsive layouts and flexible text rendering<p>* Embedded selection of applications including:<p><pre><code> * A web browser supporting DNS, HTTPS and very basic HTML
* A text editor
* A Python terminal
</code></pre>
Checkout the README for the technical breakdown.<p>Demo video: <a href="https://streamable.com/5xqjcf" rel="nofollow">https://streamable.com/5xqjcf</a>
Show HN: Munal OS: a graphical experimental OS with WASM sandboxing
Hello HN!<p>Showing off the first version of Munal OS, an experimental operating system I have been writing in Rust on and off for the past few years.<p><a href="https://github.com/Askannz/munal-os">https://github.com/Askannz/munal-os</a><p>It's an unikernel design that is compiled as a single EFI binary and does not use virtual address spaces for process isolation. Instead, applications are compiled to WASM and run inside of an embedded WASM engine.<p>Other features:<p>* Fully graphical interface in HD resolution with mouse and keyboard support<p>* Desktop shell with window manager and contextual radial menus<p>* PCI and VirtIO drivers<p>* Ethernet and TCP stack<p>* Customizable UI toolkit providing various widgets, responsive layouts and flexible text rendering<p>* Embedded selection of applications including:<p><pre><code> * A web browser supporting DNS, HTTPS and very basic HTML
* A text editor
* A Python terminal
</code></pre>
Checkout the README for the technical breakdown.<p>Demo video: <a href="https://streamable.com/5xqjcf" rel="nofollow">https://streamable.com/5xqjcf</a>
Show HN: Most users won't report bugs unless you make it stupidly easy
Most feedback tools are built like people actually want to report bugs. They don’t. Unless you make it dead-simple, or better yet - a little fun.<p>After shipping a few SaaS products, I noticed a pattern: Bugs? Yes. Bug reports? No.<p>Not because users didn’t care but because reporting bugs is usually a terrible experience.<p>Most tools want users to:<p>* Fill out a long form<p>* Enter their email<p>* Describe a bug they barely understand<p>* Maybe sign in or create an account<p>* Then maybe submit it<p>Let’s be real: no one’s doing that. Especially not someone just trying to use your product.<p>So I built Bugdrop.app - It’s a little draggable bug icon that users can drop right on the issue, type a quick note, and they’re done. No logins. No forms. Just context-rich feedback that your team can actually use — with screenshots, browser info, even console logs if they hit an error.<p>And weirdly? People actually use it. Even non-technical users click it just because "the little bug looked fun."<p>I didn’t want to build another "feedback suite". I just wanted something lightweight, fast, and so stupidly simple that people actually report stuff. If you've ever had a user say “something’s broken” and then ghost you forever, you probably get where I’m coming from.<p>What I’m most proud of? People are actually using it. And their users? They’re actually reporting stuff. Even non-technical ones.<p>Would love to hear if you’ve faced similar problems, and if this feels like something that would’ve helped in your own projects. Not trying to sell you anything — just sharing something I built to scratch my own itch.
Show HN: Most users won't report bugs unless you make it stupidly easy
Most feedback tools are built like people actually want to report bugs. They don’t. Unless you make it dead-simple, or better yet - a little fun.<p>After shipping a few SaaS products, I noticed a pattern: Bugs? Yes. Bug reports? No.<p>Not because users didn’t care but because reporting bugs is usually a terrible experience.<p>Most tools want users to:<p>* Fill out a long form<p>* Enter their email<p>* Describe a bug they barely understand<p>* Maybe sign in or create an account<p>* Then maybe submit it<p>Let’s be real: no one’s doing that. Especially not someone just trying to use your product.<p>So I built Bugdrop.app - It’s a little draggable bug icon that users can drop right on the issue, type a quick note, and they’re done. No logins. No forms. Just context-rich feedback that your team can actually use — with screenshots, browser info, even console logs if they hit an error.<p>And weirdly? People actually use it. Even non-technical users click it just because "the little bug looked fun."<p>I didn’t want to build another "feedback suite". I just wanted something lightweight, fast, and so stupidly simple that people actually report stuff. If you've ever had a user say “something’s broken” and then ghost you forever, you probably get where I’m coming from.<p>What I’m most proud of? People are actually using it. And their users? They’re actually reporting stuff. Even non-technical ones.<p>Would love to hear if you’ve faced similar problems, and if this feels like something that would’ve helped in your own projects. Not trying to sell you anything — just sharing something I built to scratch my own itch.
Show HN: Most users won't report bugs unless you make it stupidly easy
Most feedback tools are built like people actually want to report bugs. They don’t. Unless you make it dead-simple, or better yet - a little fun.<p>After shipping a few SaaS products, I noticed a pattern: Bugs? Yes. Bug reports? No.<p>Not because users didn’t care but because reporting bugs is usually a terrible experience.<p>Most tools want users to:<p>* Fill out a long form<p>* Enter their email<p>* Describe a bug they barely understand<p>* Maybe sign in or create an account<p>* Then maybe submit it<p>Let’s be real: no one’s doing that. Especially not someone just trying to use your product.<p>So I built Bugdrop.app - It’s a little draggable bug icon that users can drop right on the issue, type a quick note, and they’re done. No logins. No forms. Just context-rich feedback that your team can actually use — with screenshots, browser info, even console logs if they hit an error.<p>And weirdly? People actually use it. Even non-technical users click it just because "the little bug looked fun."<p>I didn’t want to build another "feedback suite". I just wanted something lightweight, fast, and so stupidly simple that people actually report stuff. If you've ever had a user say “something’s broken” and then ghost you forever, you probably get where I’m coming from.<p>What I’m most proud of? People are actually using it. And their users? They’re actually reporting stuff. Even non-technical ones.<p>Would love to hear if you’ve faced similar problems, and if this feels like something that would’ve helped in your own projects. Not trying to sell you anything — just sharing something I built to scratch my own itch.
Show HN: Most users won't report bugs unless you make it stupidly easy
Most feedback tools are built like people actually want to report bugs. They don’t. Unless you make it dead-simple, or better yet - a little fun.<p>After shipping a few SaaS products, I noticed a pattern: Bugs? Yes. Bug reports? No.<p>Not because users didn’t care but because reporting bugs is usually a terrible experience.<p>Most tools want users to:<p>* Fill out a long form<p>* Enter their email<p>* Describe a bug they barely understand<p>* Maybe sign in or create an account<p>* Then maybe submit it<p>Let’s be real: no one’s doing that. Especially not someone just trying to use your product.<p>So I built Bugdrop.app - It’s a little draggable bug icon that users can drop right on the issue, type a quick note, and they’re done. No logins. No forms. Just context-rich feedback that your team can actually use — with screenshots, browser info, even console logs if they hit an error.<p>And weirdly? People actually use it. Even non-technical users click it just because "the little bug looked fun."<p>I didn’t want to build another "feedback suite". I just wanted something lightweight, fast, and so stupidly simple that people actually report stuff. If you've ever had a user say “something’s broken” and then ghost you forever, you probably get where I’m coming from.<p>What I’m most proud of? People are actually using it. And their users? They’re actually reporting stuff. Even non-technical ones.<p>Would love to hear if you’ve faced similar problems, and if this feels like something that would’ve helped in your own projects. Not trying to sell you anything — just sharing something I built to scratch my own itch.
Show HN: NanoTS – Fast, embeddable, tiny time series database
eye wateringly fast. :)
Show HN: Let’s Bend – Open-Source Harmonica Bending Trainer
Hi HN,<p>I built a simple harmonica practice app that shows real-time pitch and bending targets for each hole. It helps blues harp players visualize their technique and improve intonation.<p>No tracking, no ads, open source (MIT).<p>The app is available on F-Droid and GitHub. You can find more details here:
<a href="https://letsbend.de" rel="nofollow">https://letsbend.de</a><p>Feedback welcome!
Show HN: Let’s Bend – Open-Source Harmonica Bending Trainer
Hi HN,<p>I built a simple harmonica practice app that shows real-time pitch and bending targets for each hole. It helps blues harp players visualize their technique and improve intonation.<p>No tracking, no ads, open source (MIT).<p>The app is available on F-Droid and GitHub. You can find more details here:
<a href="https://letsbend.de" rel="nofollow">https://letsbend.de</a><p>Feedback welcome!
Show HN: Let’s Bend – Open-Source Harmonica Bending Trainer
Hi HN,<p>I built a simple harmonica practice app that shows real-time pitch and bending targets for each hole. It helps blues harp players visualize their technique and improve intonation.<p>No tracking, no ads, open source (MIT).<p>The app is available on F-Droid and GitHub. You can find more details here:
<a href="https://letsbend.de" rel="nofollow">https://letsbend.de</a><p>Feedback welcome!
Show HN: Mustardwatch: Detect what files a program uses, rerun when they change
Show HN: Cpdown – Copy any webpage/YouTube subtitle as clean Markdown(LLM-ready)
TL;DR: I built a Chrome extension that copies webpage content or YouTube subtitles as clean, clutter-free Markdown with one click (or a shortcut). It even shows the token count, making it super handy for LLM prompts!<p>Hi, HN!<p>I often copy information from the web into my notes (Obsidian) or to feed context to LLMs for summaries/translations. So I built cpdown, a browser extension for this.<p>cpdown lets you convert any webpage/youtube subtitle into clean Markdown and copy it to your clipboard with a single click (or a keyboard shortcut).<p>Here are the key features:<p>* Intelligent Content Extraction: Uses Mozilla's Readability or Defuddle (by the Obsidian devs!) to strip away ads, sidebars, and other noise, focusing only on the main article content.
* Clean Markdown Conversion: The extracted HTML is then neatly converted to Markdown using the Turndown library.
* Token Count for LLMs: It calculates and displays the token count of the copied text using tiktoken. This is super handy for knowing if you're within limits before pasting into LLMs like ChatGPT or Claude.
* YouTube Transcript Copying: On YouTube video pages, it can copy the full transcript in Markdown format, automatically adding the video title as an H1 header.
* Customizable Options: You can choose your preferred content extractor (Readability/Defuddle), opt to wrap copied content in a code block, and more.<p>cpdown is completely free and open-source, built with WXT, React, and TypeScript.<p>You can grab it from the Chrome Web Store or check out the source code on GitHub. I'd love to hear your feedback, feature requests, or any suggestions!<p>* Chrome Web Store: <a href="https://chromewebstore.google.com/detail/cpdown/knnaflplggjdedobhbidojmmnocfbopf" rel="nofollow">https://chromewebstore.google.com/detail/cpdown/knnaflplggjd...</a>
* GitHub: <a href="https://github.com/ysm-dev/cpdown">https://github.com/ysm-dev/cpdown</a><p>Thanks for checking it out!