charlesfrisbee
I agree code as source of truth is a must and GUI is not necessary for authoring, everything I built (Snake, Pong, the RISCV CPU) was done headlessly in node with the help of Claude working to a spec just using the @simten/core lib on npm.
I just built a readonly ui-layer on top with the hope of making it more accessible to students/learners starting out in the space, the main features being able to visually scrub between cycles and drill down into the internals of an abstracted component. I also have a Verilog import thing I've been working on to allow learners to visualise and poke around in the browser
I was also heavily inspired by the Steam game 'Turing Complete' but wanted something code based to not need to manually wire in the GUI. Thanks for taking a look
People are kidding themselves thinking they fully understand what is going on at a deep level for 3-4 (or more) parallel tasks constantly context switching. It's also an anxiety-inducing way to work and has led to a proliferation of agent management tools enabling max efficiency.
Focusing on systems thinking/observability/knowing when NOT to build something/using agents to fix/learn new things quickly seem to be where I see devs still bringing the most value compared to any other cowboy.
Show HN: Think Turing Complete, but you write the circuits in TypeScript (WIP)
Show HN: An interactive Snake circuit you can take apart, no CPU
Show HN: Simten – design hardware in TypeScript and simulate it in the browser
I mostly wanted to prototype hardware ideas quickly, with as little as possible between writing a circuit and watching it run. There are already solid embedded HDLs in general-purpose languages i.e. Chisel (Scala), Amaranth (Python), SpinalHDL. They all also have their own simulators, but they live inside the JVM or Python toolchains. I wanted something I could open in a browser and just start...