惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Engineering at Meta
Engineering at Meta
Microsoft Azure Blog
Microsoft Azure Blog
I
InfoQ
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
人人都是产品经理
人人都是产品经理
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
T
Tailwind CSS Blog
MongoDB | Blog
MongoDB | Blog
Google DeepMind News
Google DeepMind News
WordPress大学
WordPress大学
量子位
美团技术团队
大猫的无限游戏
大猫的无限游戏
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Last Week in AI
Last Week in AI
博客园 - 司徒正美
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
小众软件
小众软件
C
Check Point Blog
博客园 - 三生石上(FineUI控件)
N
Netflix TechBlog - Medium
Recent Announcements
Recent Announcements
有赞技术团队
有赞技术团队
月光博客
月光博客

Hacker News: Show HN

PurrrrrFocus: Pomodoro Timer App - App Store Workflow Engine — Multi-Step Orchestration for Bun RapidPhoto: Pro Photo Editor App - App Store GitHub - DheerG/swarms: Achieve extraordinary results with claude code across a variety of tasks SPICE simulation → oscilloscope → verification with Claude Code — Lucas Gerads Show HN: VCoding – A 5 MB native Windows IDE with no dynamic dependencies Show HN: LLMs don't hallucinate because they're bad at math, it's the format GitHub - Agent-FM/agentfm-core: AgentFM is a peer-to-peer network that turns everyday computers into a decentralized AI supercomputer. AgentFM lets you run massive AI workloads directly across a global mesh of idle CPUs and GPUs. Show HN: Tracking Top US Science Olympiad Alumni over Last 25 Years GitHub - Potarix/agent-hub: One place to talk to all your agents Show HN: Runtime security for AI agents(injection,tool abuse, data exfiltration) GitHub - dubeyKartikay/lazyspotify: Terminal Spotify client for macOS and Linux GitHub - the-banana-tool/king-louie: Easy to use GUI Personal AI Assistant. Win/Linux/Mac. Show HN I made my vacation rental bookable by AI agents–no Airbnb, 0% commission GitHub - basteez/jsf-autoreload: maven plugin to enable hot reload on jsf projects uvm32/hosts/host-gdbstub at main · ringtailsoftware/uvm32 GitHub - labsai/EDDI: Config-driven engine that turns JSON into production-grade AI agents. Multi-agent orchestration, 12+ LLM providers, MCP/A2A protocols, RAG, persistent memory, and enterprise compliance (EU AI Act, GDPR, HIPAA). Built on Quarkus. GitHub - glitchnsec/fortyone-oss: AI Executive Assistant Platform Quickstart | Alien GitHub - muxshed/shed: One stream in, or many. Every destination, simultaneously. No cloud middleman, no per-channel fees, no limits. GitHub - ocrbase-hq/ocrbase: 📄 PDF/IMG ->.MD/JSON Document OCR API for PaddleOCR and GLMOCR. Self-hostable. GitHub - impactjo/home-memory: MCP server that lets your AI assistant remember everything about your home. GitHub - Sets88/dbcls: DbCls is a powerful terminal database client that supports various databases GitHub - neptun2000/heor-agent-mcp GitHub - SeanFDZ/macmind: Single-layer transformer in HyperTalk for the classic Macintosh RollQuation: Math Puzzles - Apps on Google Play GitHub - dropbox/witchcraft Show HN: Agent-cache – Multi-tier LLM/tool/session caching for Valkey and Redis GitHub - opentalon/opentalon: OpenTalon is an open-source platform built from the ground up in Go as a robust alternative to OpenClaw LinkedIn™ 职位抓取工具 - Chrome 应用商店
Development minus the hardware
grog_6 · 2026-05-08 · via Hacker News: Show HN

Today, we shipped everything: a complete development environment on the web for embedded development, something that wouldn’t have been possible without simulators.

Here’s what shipped: every project now gets its own isolated NixOS VM, meaning you can bring any build tool, toolchain, or compiler you want with no configuration fights. We also shipped a coding agent that is tightly coupled with the simulator. It can see your register state, memory, and peripheral output in real time, so it actually understands what your firmware is doing.


Simulators

When I started building Simulator86 I realized how far the potential of simulators could be. Hardware is hard. It’s hard because of the constraints that revolve around it, hard because if things fail, their liability will skyrocket. So hard that I’d argue SpaceX would’ve failed without simulators.

To enhance the workflow of any system that has to touch the real world, you’d need a sort of medium that is tolerant of catastrophes, just like having a dev server for your production servers. Launching software bugs to the world typically damages you or costs you user trust, but launching explosives to the world — well, that’s a really bad idea that will probably end in a tricky situation. And because the digital version is already modeled and less detailed than the real one, the ability to bridge between digital and physical is a hard, long, and from-the-depths-of-hell kind of problem to solve.

To build that bridge — also known as a simulator/emulator — the north star is clear: the highest fidelity simulator possible. So how do we create the highest fidelity simulation out there? Simulators are a mixture of infrastructure, modeling, and software architecture problems, but instead of user behavior you benchmark against certain aspects of physics. If you benchmark against users it becomes more like a game, and if you build a game, you haven’t bridged between the two worlds.

But mostly the focus will be on the parts that will have the most impact on what people design in which environment. Now, I’ll ask again: why do they have to be accurate? Because for each 1% of accuracy drop — especially in the cases the simulator was needed for — the usefulness of the simulator for that direction drops. Accuracy and value are closely related in simulators.

For instance, if a physics simulator skips specifics like wind friction, the insights quickly diverge from reality based on how much your system depends on wind friction. If you plan to produce a chip optimized to work in space, it’s going to be tough if you don’t account for cosmic rays, which will cause your chip to flip bits. (Those are just bursts of energy in space.)

To simulate those nitty-gritty details, we are going to trade compute and compatibility for accuracy. More compute allows us to run more interesting scenarios, at scale, on different paths and directions, without the limits of consumer hardware, by delivering to the consumer via a simple interface.

Custom hardware on demand is an interesting thing to have. Many countries face a lack of manual labor, and custom hardware would benefit those in real estate, logistics, etc. But how about we build a simulator so accurate that it allows us to predict the future? Populate that simulator with LLM agents, train them, take them out and put them in a robot — you can’t simply provision 300 robots into the real world, each with a slightly different neural network, and benchmark against all those. That’s probably why Nvidia is constantly pushing Isaac and research papers like GEM on modeling and simulation techniques.

One of the things we’ve been working on is our private cloud optimized for our custom simulators. We spin up and allocate resources for simulation for those specific scenarios, because writing generic simulators — or shipping them as binaries like Isaac, which is mostly designed to target consumer hardware — won’t be enough.

If you think of LLMs as a sort of human simulator, or at least how most people started to think of the human brain after LLMs were released, you can clearly see how a model trained to replicate a human brain is now being used for entirely different things that weren’t known before LLMs.