Grid: Free, local-first, browser-based 3D printing/CNC/laser slicer

Original Article ↗ Hacker News Discussion ↗

Local-first browser-based CAM and slicer

  • Grid/Kiri:Moto is praised for being free, open-source (MIT), local-first, and browser-based with no accounts or cloud dependency.
  • Supports multiple domains (FDM/SLA 3D printing, CNC, laser, wire EDM), which users see as valuable for makerspaces: same UI across tools lowers the learning curve.
  • Desktop builds and PWA installs are available for fully offline use; source can be self-hosted (including via Docker).
  • Integration with Onshape and Chromebook support has reportedly put it into STEM classrooms.
  • One user hit a bug with an Ender 3 profile (missing intermediate top surfaces); maintainers say it’s easily fixable.

Offline use, DRM, and 3D printer control

  • Several comments emphasize keeping printers offline via SD cards, USB, or firewalled LAN; people don’t trust cloud services after outages (e.g., Fusion 360 export failure).
  • Some brands (Elegoo, Prusa, Bambu) can run offline, but UX varies: complaints about awkward SD handling, inaccessible USB ports, and proprietary network plugins.
  • Strong resistance to proposed laws requiring printers/CNCs to be online to block firearm printing.
  • Concerns include: firmware bricking, “right to repair/use/build,” feasibility of detecting gun models, and chilling effects on hobbyists while criminals bypass restrictions anyway.
  • Some argue such laws are unconstitutional and mainly symbolic; others criticize them as virtue signaling rather than tackling enforcement of existing gun crimes.

Comparisons to other tools and ecosystems

  • Alternatives mentioned: Carbide Create, MeshCAM, Alibre, FreeCAD, Solvespace, Fusion 360 (especially for adaptive milling).
  • Slic3r → PrusaSlicer → Bambu Studio → OrcaSlicer lineage is outlined; many vendor slicers are Orca derivatives.
  • Disagreement over Bambu: some say it’s a legitimate fork contributing back; others describe slow, reluctant source releases, lock-in behavior, and risk to more open competitors.

Browser vs native, longevity, and standards

  • Debate over whether “runs in any browser, even offline once loaded” counts as true offline:
    • Pro: cached/PWA/web-app + open source can be self-hosted for decades; browsers tend to be very backward compatible.
    • Con: browser cache is opaque and fragile; web apps are resource-heavy, lack hard real-time support, and feel less durable than native binaries.
  • Broader tangent on why cross-platform native standards lag the web: misaligned incentives, app-store revenue, and WebKit restrictions are cited.
  • Some see JS/WASM/WebGPU as surprisingly performant for heavy tasks like toolpath generation when carefully coded.