The best Hacker News stories from Show from the past week
Latest posts:
Show HN: Bash Screensavers
A github project to collect a bunch of bash-based screensavers/visualizations.
Show HN: Write Go code in JavaScript files
I built a Vite plugin that lets you write Go code directly in .js files using a "use
golang" directive. It compiles to WebAssembly automatically.
Show HN: Write Go code in JavaScript files
I built a Vite plugin that lets you write Go code directly in .js files using a "use
golang" directive. It compiles to WebAssembly automatically.
Show HN: JSON Query
I'm working on a tool that will probably involve querying JSON documents and I'm asking myself how to expose that functionality to my users.<p>I like the power of `jq` and the fact that LLMs are proficient at it, but I find it right out impossible to come up with the right `jq` incantations myself. Has anyone here been in a similar situation? Which tool / language did you end up exposing to your users?
Show HN: JSON Query
I'm working on a tool that will probably involve querying JSON documents and I'm asking myself how to expose that functionality to my users.<p>I like the power of `jq` and the fact that LLMs are proficient at it, but I find it right out impossible to come up with the right `jq` incantations myself. Has anyone here been in a similar situation? Which tool / language did you end up exposing to your users?
Show HN: MyraOS – My 32-bit operating system in C and ASM (Hack Club project)
Hi HN, I’m Dvir, a young developer. Last year, I got rejected after a job interview because I lacked some CPU knowledge. After that, I decided to deepen my understanding in the low level world and learn how things work under the hood. I decided to try and create an OS in C and ASM as a way to broaden my knowledge in this area.<p>This took me on the most interesting ride, where I’ve learned about OS theory and low level programming on a whole new level. I’ve spent hours upon hours, blood and tears, reading different OS theory blogs, learning low level concepts, debugging, testing and working on this project.<p>I started by reading University books and online blogs, while also watching videos.
Some sources that helped me out were OSDev Wiki (<a href="https://wiki.osdev.org/Expanded_Main_Page" rel="nofollow">https://wiki.osdev.org/Expanded_Main_Page</a>), OSTEP (<a href="https://pages.cs.wisc.edu/~remzi/OSTEP" rel="nofollow">https://pages.cs.wisc.edu/~remzi/OSTEP</a>), open-source repositories like MellOS and LemonOS (more advanced), DoomGeneric, and some friends that have built an OS before.<p>This part was the longest, but also the easiest. I felt like I understood the theory, but still could not connect it into actual code. Sitting down and starting to code was difficult, but I knew that was the next step I needed to take!
I began by working on the bootloader, which is optional since you can use a pre-made one (I switched to GRUB later), but implementing it was mainly for learning purposes and to warm up on ASM. These were my steps after that:<p><pre><code> 1) I started implementing the VGA driver, which gave me the ability to display text.
2) Interrupts - IDT, ISR, IRQ, which signal to the CPU that a certain event occurred and needs handling (such as faults, hardware connected device actions, etc).
3) Keyboard driver, which enables me to display the same text I type on my keyboard.
4) PMM (Physical memory management)
5) Paging and virtual memory management
6) RTC driver - clock addition (which was, in my opinion, optional)
7) PIT driver - Ticks every certain amount of time, and also
8) FS (File System) and physical HDD drivers - for the HDD I chose PATA (HDD communication protocol) for simplicity (SATA is a newer but harder option as well).
For the FS I chose EXT2 (The Second Extended FileSystem), which is a foundational linux FS structure introduced in 1993. This FS structure is not the simplest,
but is very popular in hobby-OS, it is very supported, easy to set up and upgrade to newer EXT versions, it has a lot of materials online, compared to other
options. This was probably the longest and largest feature I had worked on.
9) Syscall support.
10) Libc implementation.
11) Processing and scheduling for multiprocessing.
12) Here I also made a shell to test it all.
</code></pre>
At this point, I had a working shell, but later decided to go further and add a GUI! I was working on the FS (stage 8), when I heard about Hack Club’s Summer of Making (SoM). This was my first time practicing in HackClub, and I want to express my gratitude and share my enjoyment of participating in it.<p>At first I just wanted to declare the OS as finished after completing the FS, and a bit of other drivers, but because of SoM my perspective was changed completely. Because of the competition, I started to think that I needed to ship a complete OS, with processing, GUI and the bare minimum ability to run Doom. I wanted to show the community in SoM how everything works.<p>Then I worked on it for another 2 months, after finishing the shell, just because of SoM!, totalling my project to almost 7 months of work. At this time I added full GUI support, with dirty rectangles and double buffering, I made a GUI mouse driver, and even made a full Doom port! things I would've never even thought about without participating in SoM.<p>This is my SoM project: <a href="https://summer.hackclub.com/projects/5191" rel="nofollow">https://summer.hackclub.com/projects/5191</a>.<p>Every project has challenges, especially in such a low level project. I had to do a lot of debugging while working on this, and it is no easy task. I highly recommend using GDB which helped me debug so many of my problems, especially memory ones.<p>The first major challenge I encountered was during the coding of processes - I realized that a lot of my paging code was completely wrong, poorly tested, and had to be reworked. During this time I was already in the competition and it was difficult keeping up with devlogs and new features while fixing old problems in a code I wrote a few months ago.<p>Some more major problems occurred when trying to run Doom, and unlike the last problem, this was a disaster. I had random PFs and memory problems, one run could work while the next one wouldn’t, and the worst part is that it was only on the Doom, and not on processes I created myself. These issues took a lot of time to figure out. I began to question the Doom code itself, and even thought about giving up on the whole project.<p>After a lot of time spent debugging, I fixed the issues. It was a combination of scheduling issues, Libc issues and the Qemu not having enough (wrongfully assuming 128MB for the whole OS was enough).<p>Finally, I worked throughout all the difficulties, and shipped the project! In the end, the experience working on this project was amazing. I learned a lot, grew and improved as a developer, and I thank SoM for helping to increase my motivation and make the project memorable and unique like I never imagined it would be.<p>The repo is at <a href="https://github.com/dvir-biton/MyraOS" rel="nofollow">https://github.com/dvir-biton/MyraOS</a>. I’d love to discuss any aspect of this with you all in the comments!
Show HN: MyraOS – My 32-bit operating system in C and ASM (Hack Club project)
Hi HN, I’m Dvir, a young developer. Last year, I got rejected after a job interview because I lacked some CPU knowledge. After that, I decided to deepen my understanding in the low level world and learn how things work under the hood. I decided to try and create an OS in C and ASM as a way to broaden my knowledge in this area.<p>This took me on the most interesting ride, where I’ve learned about OS theory and low level programming on a whole new level. I’ve spent hours upon hours, blood and tears, reading different OS theory blogs, learning low level concepts, debugging, testing and working on this project.<p>I started by reading University books and online blogs, while also watching videos.
Some sources that helped me out were OSDev Wiki (<a href="https://wiki.osdev.org/Expanded_Main_Page" rel="nofollow">https://wiki.osdev.org/Expanded_Main_Page</a>), OSTEP (<a href="https://pages.cs.wisc.edu/~remzi/OSTEP" rel="nofollow">https://pages.cs.wisc.edu/~remzi/OSTEP</a>), open-source repositories like MellOS and LemonOS (more advanced), DoomGeneric, and some friends that have built an OS before.<p>This part was the longest, but also the easiest. I felt like I understood the theory, but still could not connect it into actual code. Sitting down and starting to code was difficult, but I knew that was the next step I needed to take!
I began by working on the bootloader, which is optional since you can use a pre-made one (I switched to GRUB later), but implementing it was mainly for learning purposes and to warm up on ASM. These were my steps after that:<p><pre><code> 1) I started implementing the VGA driver, which gave me the ability to display text.
2) Interrupts - IDT, ISR, IRQ, which signal to the CPU that a certain event occurred and needs handling (such as faults, hardware connected device actions, etc).
3) Keyboard driver, which enables me to display the same text I type on my keyboard.
4) PMM (Physical memory management)
5) Paging and virtual memory management
6) RTC driver - clock addition (which was, in my opinion, optional)
7) PIT driver - Ticks every certain amount of time, and also
8) FS (File System) and physical HDD drivers - for the HDD I chose PATA (HDD communication protocol) for simplicity (SATA is a newer but harder option as well).
For the FS I chose EXT2 (The Second Extended FileSystem), which is a foundational linux FS structure introduced in 1993. This FS structure is not the simplest,
but is very popular in hobby-OS, it is very supported, easy to set up and upgrade to newer EXT versions, it has a lot of materials online, compared to other
options. This was probably the longest and largest feature I had worked on.
9) Syscall support.
10) Libc implementation.
11) Processing and scheduling for multiprocessing.
12) Here I also made a shell to test it all.
</code></pre>
At this point, I had a working shell, but later decided to go further and add a GUI! I was working on the FS (stage 8), when I heard about Hack Club’s Summer of Making (SoM). This was my first time practicing in HackClub, and I want to express my gratitude and share my enjoyment of participating in it.<p>At first I just wanted to declare the OS as finished after completing the FS, and a bit of other drivers, but because of SoM my perspective was changed completely. Because of the competition, I started to think that I needed to ship a complete OS, with processing, GUI and the bare minimum ability to run Doom. I wanted to show the community in SoM how everything works.<p>Then I worked on it for another 2 months, after finishing the shell, just because of SoM!, totalling my project to almost 7 months of work. At this time I added full GUI support, with dirty rectangles and double buffering, I made a GUI mouse driver, and even made a full Doom port! things I would've never even thought about without participating in SoM.<p>This is my SoM project: <a href="https://summer.hackclub.com/projects/5191" rel="nofollow">https://summer.hackclub.com/projects/5191</a>.<p>Every project has challenges, especially in such a low level project. I had to do a lot of debugging while working on this, and it is no easy task. I highly recommend using GDB which helped me debug so many of my problems, especially memory ones.<p>The first major challenge I encountered was during the coding of processes - I realized that a lot of my paging code was completely wrong, poorly tested, and had to be reworked. During this time I was already in the competition and it was difficult keeping up with devlogs and new features while fixing old problems in a code I wrote a few months ago.<p>Some more major problems occurred when trying to run Doom, and unlike the last problem, this was a disaster. I had random PFs and memory problems, one run could work while the next one wouldn’t, and the worst part is that it was only on the Doom, and not on processes I created myself. These issues took a lot of time to figure out. I began to question the Doom code itself, and even thought about giving up on the whole project.<p>After a lot of time spent debugging, I fixed the issues. It was a combination of scheduling issues, Libc issues and the Qemu not having enough (wrongfully assuming 128MB for the whole OS was enough).<p>Finally, I worked throughout all the difficulties, and shipped the project! In the end, the experience working on this project was amazing. I learned a lot, grew and improved as a developer, and I thank SoM for helping to increase my motivation and make the project memorable and unique like I never imagined it would be.<p>The repo is at <a href="https://github.com/dvir-biton/MyraOS" rel="nofollow">https://github.com/dvir-biton/MyraOS</a>. I’d love to discuss any aspect of this with you all in the comments!
Show HN: MyraOS – My 32-bit operating system in C and ASM (Hack Club project)
Hi HN, I’m Dvir, a young developer. Last year, I got rejected after a job interview because I lacked some CPU knowledge. After that, I decided to deepen my understanding in the low level world and learn how things work under the hood. I decided to try and create an OS in C and ASM as a way to broaden my knowledge in this area.<p>This took me on the most interesting ride, where I’ve learned about OS theory and low level programming on a whole new level. I’ve spent hours upon hours, blood and tears, reading different OS theory blogs, learning low level concepts, debugging, testing and working on this project.<p>I started by reading University books and online blogs, while also watching videos.
Some sources that helped me out were OSDev Wiki (<a href="https://wiki.osdev.org/Expanded_Main_Page" rel="nofollow">https://wiki.osdev.org/Expanded_Main_Page</a>), OSTEP (<a href="https://pages.cs.wisc.edu/~remzi/OSTEP" rel="nofollow">https://pages.cs.wisc.edu/~remzi/OSTEP</a>), open-source repositories like MellOS and LemonOS (more advanced), DoomGeneric, and some friends that have built an OS before.<p>This part was the longest, but also the easiest. I felt like I understood the theory, but still could not connect it into actual code. Sitting down and starting to code was difficult, but I knew that was the next step I needed to take!
I began by working on the bootloader, which is optional since you can use a pre-made one (I switched to GRUB later), but implementing it was mainly for learning purposes and to warm up on ASM. These were my steps after that:<p><pre><code> 1) I started implementing the VGA driver, which gave me the ability to display text.
2) Interrupts - IDT, ISR, IRQ, which signal to the CPU that a certain event occurred and needs handling (such as faults, hardware connected device actions, etc).
3) Keyboard driver, which enables me to display the same text I type on my keyboard.
4) PMM (Physical memory management)
5) Paging and virtual memory management
6) RTC driver - clock addition (which was, in my opinion, optional)
7) PIT driver - Ticks every certain amount of time, and also
8) FS (File System) and physical HDD drivers - for the HDD I chose PATA (HDD communication protocol) for simplicity (SATA is a newer but harder option as well).
For the FS I chose EXT2 (The Second Extended FileSystem), which is a foundational linux FS structure introduced in 1993. This FS structure is not the simplest,
but is very popular in hobby-OS, it is very supported, easy to set up and upgrade to newer EXT versions, it has a lot of materials online, compared to other
options. This was probably the longest and largest feature I had worked on.
9) Syscall support.
10) Libc implementation.
11) Processing and scheduling for multiprocessing.
12) Here I also made a shell to test it all.
</code></pre>
At this point, I had a working shell, but later decided to go further and add a GUI! I was working on the FS (stage 8), when I heard about Hack Club’s Summer of Making (SoM). This was my first time practicing in HackClub, and I want to express my gratitude and share my enjoyment of participating in it.<p>At first I just wanted to declare the OS as finished after completing the FS, and a bit of other drivers, but because of SoM my perspective was changed completely. Because of the competition, I started to think that I needed to ship a complete OS, with processing, GUI and the bare minimum ability to run Doom. I wanted to show the community in SoM how everything works.<p>Then I worked on it for another 2 months, after finishing the shell, just because of SoM!, totalling my project to almost 7 months of work. At this time I added full GUI support, with dirty rectangles and double buffering, I made a GUI mouse driver, and even made a full Doom port! things I would've never even thought about without participating in SoM.<p>This is my SoM project: <a href="https://summer.hackclub.com/projects/5191" rel="nofollow">https://summer.hackclub.com/projects/5191</a>.<p>Every project has challenges, especially in such a low level project. I had to do a lot of debugging while working on this, and it is no easy task. I highly recommend using GDB which helped me debug so many of my problems, especially memory ones.<p>The first major challenge I encountered was during the coding of processes - I realized that a lot of my paging code was completely wrong, poorly tested, and had to be reworked. During this time I was already in the competition and it was difficult keeping up with devlogs and new features while fixing old problems in a code I wrote a few months ago.<p>Some more major problems occurred when trying to run Doom, and unlike the last problem, this was a disaster. I had random PFs and memory problems, one run could work while the next one wouldn’t, and the worst part is that it was only on the Doom, and not on processes I created myself. These issues took a lot of time to figure out. I began to question the Doom code itself, and even thought about giving up on the whole project.<p>After a lot of time spent debugging, I fixed the issues. It was a combination of scheduling issues, Libc issues and the Qemu not having enough (wrongfully assuming 128MB for the whole OS was enough).<p>Finally, I worked throughout all the difficulties, and shipped the project! In the end, the experience working on this project was amazing. I learned a lot, grew and improved as a developer, and I thank SoM for helping to increase my motivation and make the project memorable and unique like I never imagined it would be.<p>The repo is at <a href="https://github.com/dvir-biton/MyraOS" rel="nofollow">https://github.com/dvir-biton/MyraOS</a>. I’d love to discuss any aspect of this with you all in the comments!
Show HN: Diagram as code tool with draggable customizations
In the past I've used declarative diagram generation tools like Mermaid.js a lot for quickly drawing up things but for presentations or deliverables I find that I have to then move the generated diagrams over to a tool like Lucidchart which allows full control of the organization and customization.<p>Therefore I am now working on this to combine the benefits of both into just one tool which can do both functions.<p>The project is certainly in the early stages but if you find yourself making architecture diagrams I'd love to hear your thoughts on the idea or even a Github issue for a feature request!<p>One of the workflows I'm targeting is when an AI generates the first draft of the diagram (all the LLMs know .mmd syntax) and then the user can then customize it to their liking which I think can drastically speed up making complex diagrams!
Show HN: Diagram as code tool with draggable customizations
In the past I've used declarative diagram generation tools like Mermaid.js a lot for quickly drawing up things but for presentations or deliverables I find that I have to then move the generated diagrams over to a tool like Lucidchart which allows full control of the organization and customization.<p>Therefore I am now working on this to combine the benefits of both into just one tool which can do both functions.<p>The project is certainly in the early stages but if you find yourself making architecture diagrams I'd love to hear your thoughts on the idea or even a Github issue for a feature request!<p>One of the workflows I'm targeting is when an AI generates the first draft of the diagram (all the LLMs know .mmd syntax) and then the user can then customize it to their liking which I think can drastically speed up making complex diagrams!
Show HN: Diagram as code tool with draggable customizations
In the past I've used declarative diagram generation tools like Mermaid.js a lot for quickly drawing up things but for presentations or deliverables I find that I have to then move the generated diagrams over to a tool like Lucidchart which allows full control of the organization and customization.<p>Therefore I am now working on this to combine the benefits of both into just one tool which can do both functions.<p>The project is certainly in the early stages but if you find yourself making architecture diagrams I'd love to hear your thoughts on the idea or even a Github issue for a feature request!<p>One of the workflows I'm targeting is when an AI generates the first draft of the diagram (all the LLMs know .mmd syntax) and then the user can then customize it to their liking which I think can drastically speed up making complex diagrams!
Show HN: Tommy – Turn ESP32 devices into through-wall motion sensors
Hi HN! I would like to present my project called TOMMY, which turns ESP32 devices into motion sensors that work through walls and obstacles using Wi-Fi sensing.<p>TOMMY started as a project for my own use. I was frustrated with motion sensors that didn't detect stationary presence and left dead zones everywhere. Presence sensors existed but were expensive and needed one per room. I explored echo localization first, but microphones listening 24/7 felt too creepy. Then I discovered Wi-Fi sensing - a huge research topic but nothing production-ready yet. It ticked all the boxes: could theoretically detect stationary presence through breathing/micromovements and worked through walls and furniture so devices could be hidden away.<p>Two years and dozens of research papers later, TOMMY has evolved into software I'm honestly quite proud of. Although it doesn't have stationary presence detection yet (coming Q1 2026) it detects motion really well. It works as a Home Assistant Add-on or Docker container, supports a range of ESP32 devices, and can be flashed through the built-in tool or used alongside existing ESPHome setups.<p>I released the first version a couple of months ago on Home Assistant's subreddit and got a lot of interest and positive feedback. More than 200 people joined the Discord community and almost 2,000 downloaded it.<p>Right now TOMMY is in beta, which is completely free for everyone to use. I'm also offering free lifetime licenses to every beta user who joins the Discord channel.<p>You can read more about the project on <a href="https://www.tommysense.com" rel="nofollow">https://www.tommysense.com</a>. Please join the Discord channel if you are interested in the project.<p>A note on open source: There's been a lot of interest in having TOMMY as an open source project, which I fully understand. I'm reluctant to open source before reaching sustainability, as I'd love to work on this full time. However, privacy is verifiable - it's 100% local with no data collection (easily confirmed via packet sniffing or network isolation). Happy to help anyone verify this.
Show HN: Tommy – Turn ESP32 devices into through-wall motion sensors
Hi HN! I would like to present my project called TOMMY, which turns ESP32 devices into motion sensors that work through walls and obstacles using Wi-Fi sensing.<p>TOMMY started as a project for my own use. I was frustrated with motion sensors that didn't detect stationary presence and left dead zones everywhere. Presence sensors existed but were expensive and needed one per room. I explored echo localization first, but microphones listening 24/7 felt too creepy. Then I discovered Wi-Fi sensing - a huge research topic but nothing production-ready yet. It ticked all the boxes: could theoretically detect stationary presence through breathing/micromovements and worked through walls and furniture so devices could be hidden away.<p>Two years and dozens of research papers later, TOMMY has evolved into software I'm honestly quite proud of. Although it doesn't have stationary presence detection yet (coming Q1 2026) it detects motion really well. It works as a Home Assistant Add-on or Docker container, supports a range of ESP32 devices, and can be flashed through the built-in tool or used alongside existing ESPHome setups.<p>I released the first version a couple of months ago on Home Assistant's subreddit and got a lot of interest and positive feedback. More than 200 people joined the Discord community and almost 2,000 downloaded it.<p>Right now TOMMY is in beta, which is completely free for everyone to use. I'm also offering free lifetime licenses to every beta user who joins the Discord channel.<p>You can read more about the project on <a href="https://www.tommysense.com" rel="nofollow">https://www.tommysense.com</a>. Please join the Discord channel if you are interested in the project.<p>A note on open source: There's been a lot of interest in having TOMMY as an open source project, which I fully understand. I'm reluctant to open source before reaching sustainability, as I'd love to work on this full time. However, privacy is verifiable - it's 100% local with no data collection (easily confirmed via packet sniffing or network isolation). Happy to help anyone verify this.
Show HN: Play abstract strategy board games online with friends or against bots
Thought I would post in celebration of 1 year of my website being online. I've been working on it on and off and currently the website allows users to play Hex, Tumbleweed, Amazons, and Connect 6 against friends or against practice bots. I've been a long time player of some of these games and I felt for a long time that the world could use a few more popular abstract strategy games compared to Chess or Go.<p>If you try it, let me know what you think. I'm always looking for new games or new features to add :)
Show HN: I built a tech news aggregator that works the way my brain does
An honest to god, non-algorithmic reverse chrono list of tech news that passes my signal-to-noise tests, updated hourly.<p>A lightweight a page design as I've been able to keep; simple, clean, fast. No commercial features or aspirations - this is a passion project, something I've been fooling around with on and off for decades.<p>There's a "Top" view too with an LLM edited front page & summary, and categorized views for a large number of topics - see the Directory. A few more buried features to explore, but the fundamental use case is pop in, scan, exit - fast and concise.<p>Your feedback would be appreciated!
Show HN: Cadence – A guitar theory app
Hello HN, I just released this music theory and ear training mobile app for guitar which I've been working on for a bit more than a year on the side.<p>The idea was to make something for the eternally "intermediate" guitarist (myself included). There are a lot of beginner apps which rely on learning songs, toolkits which give you a bunch of stuff with no explanation but not many in-between apps to actually learn and practice more generic and somewhat advanced stuff.<p>The app contains short lessons, recaps and most importantly challenges (visual, audio and pure theory) along with a very complete library.<p>The challenges are made for practicing, they will get increasingly harder and getting to the max score is supposed to be quite hard. The idea being that you have to repeat them regularly until your brain has integrated the info and it flows naturally rather than being a one time quick dopamine shot. This is partly inspired by how language learning apps work.<p>It has no ads, a lifetime purchase option and you can use it without an account if you don't care about multi-device sync or backing up your progress.<p>Android: <a href="https://play.google.com/store/apps/details?id=com.apizon.cadence.android">https://play.google.com/store/apps/details?id=com.apizon.cad...</a><p>iOS: <a href="https://apps.apple.com/us/app/cadence-guitar-theory/id6747011447?platform=iphone">https://apps.apple.com/us/app/cadence-guitar-theory/id674701...</a><p>(This is my second and last post about this sorry for spam. My first post a few weeks ago didn't get any views and posting on a saturday might not have helped...)
Show HN: I'm making a detective game built on Wikipedia
Hi HN!
Worked on this side project for a while and wanted to share it. It's free to play.
Show HN: I created a cross-platform GUI for the JJ VCS (Git compatible)
Personally, I think the JJ VCS (<a href="https://github.com/jj-vcs/jj" rel="nofollow">https://github.com/jj-vcs/jj</a>) hit a point some time in this past year where I find it hard to find a great reason to continue using git. Over the years I've cobbled together aliases and bash functions to try to improve my git workflow, but after using jj, which works with ~any git repo and integrates great with Github repos, all of the workflow issues I ran into with git are not only solved, but improved in ways I couldn't manage with simple scripts.<p>One example is the op log, which lets you go to any point in your repo's time and provides simple undo and redo commands when you want to back out of a merge, didn't mean to rebase, etc.<p>Because I have a pretty strong conviction that JJ is at this point a cleaner and more powerful version of git, my hopes are that it continues to grow. With that, it seemed a proper full-featured GUI was missing for the VCS. There's some plugins that add some integration into VS Code, and there's one in the works to get Intellij support working, but many of the constructs JJ provides in my opinion necessitate a grounds-up build of a GUI around how JJ works.<p>Right now, [name-redacted] is an MVP in an open beta. I did my best to support all of the core functionality one would need, though there's many nice-to-haves that I am going to add, like native merge support, native splitting, etc. Most of this will be based on feedback from the Beta.<p>I'm really grateful for the great community JJ has built, alongside the HN community itself in the countless VCS-based posts I've read over the years, and am hoping for lots of input here during Beta under real usage - the goal is to be a full-featured desktop GUI for the VCS, similar to many of the great products that are out there for git.
Show HN: Playwright Skill for Claude Code – Less context than playwright-MCP
I got tired of playwright-mcp eating through Claude's 200K token limit, so I built this using the new Claude Skills system. Built it with Claude Code itself.<p>Instead of sending accessibility tree snapshots on every action, Claude just writes Playwright code and runs it. You get back screenshots and console output. That's it.<p>314 lines of instructions vs a persistent MCP server. Full API docs only load if Claude needs them.<p>Same browser automation, way less overhead. Works as a Claude Code plugin or manual install.<p>Token limit issue: <a href="https://github.com/microsoft/playwright-mcp/issues/889" rel="nofollow">https://github.com/microsoft/playwright-mcp/issues/889</a><p>Claude Skills docs: <a href="https://docs.claude.com/en/docs/claude-code/skills" rel="nofollow">https://docs.claude.com/en/docs/claude-code/skills</a>
Show HN: Duck-UI – Browser-Based SQL IDE for DuckDB
I built Duck-UI, a web-based SQL editor that runs DuckDB entirely in your browser via WebAssembly. No backend required.<p>The Problem: Every time I needed to query csv, parquet, or even to play with SQL, I had to either:
(a) spin up a Jupyter notebook
(b) use the CLI
(c) upload to a hosted service.<p>Friction at every step (TOO MUCH to load a csv or even to test some sql (study)...<p>The Solution: DuckDB's WASM runtime lets us run SQL analysis client-side. Load CSV/JSON/Parquet files from disk or URL, write SQL, get results instantly. Data stays on your machine.
What It Does:<p>SQL editor with autocomplete & syntax highlighting
Import CSV, JSON, Parquet, Arrow (local or remote URLs)
Query history, keyboard shortcuts, theme toggle
Persistent storage via OPFS (data survives browser refresh)
Optional: Connect to external DuckDB servers
One-liner Docker deployment or Node 20+ dev server<p>Technical Details:<p>DuckDB compiled to WASM; query execution in-browser
OPFS-backed persistence
Apache 2.0 licensed
Runs on Chrome 88+, Firefox 79+, Safari 14+<p>Use Cases:<p>Learning SQL without setting up databases
Ad-hoc data exploration (CSV → SQL in seconds)
Quick prototyping before shipping to production
Privacy-conscious workflows (no data leaves your browser)<p>GitHub: <a href="https://github.com/ibero-data/duck-ui" rel="nofollow">https://github.com/ibero-data/duck-ui</a>
Live Demo: <a href="https://demo.duckui.com" rel="nofollow">https://demo.duckui.com</a>
Quick Start: docker run -p 5522:5522 ghcr.io/ibero-data/duck-ui:latest<p>Would love feedback on:
(1) Use cases I'm missing
(2) Performance bottlenecks you hit
(3) Features that would make this your default SQL scratchpad.