- 100% free, no subscriptions, no accounts, no cloud
- Local-first: all slicing and toolpath generation runs on your machine
- Works in any browser, even offline once loaded
YES!
I think a new type of open source is emerging centering around what is now possible in browsers. Browsers have a great track record when running legacy projects. Relying on a backend could be a liability for longevity.
I built opal editor myself, a local first open source free markdown editor with these same principles, https://github.com/rbbydotdev/opal
That, my friend, is not how offline works.
You will be required to have internet access in one way or another.
Offline works 100% locally no matter if you have internet or not.
But you have to get the software somehow? Once you get it, it works offline. The same here I guess: once you download the source code/binaries into browser's cache (that can store things indefinitely) it's offline.
Umm, I’m confused about this comment… the concept of a web app that gets saved into browser cache and then can be loaded and used while offline definitely isn’t new. See Photopea etc
probably adaptive milling, which will be in an upcoming release. sharp path changes in harder metals can wear or break tools if you don't go slow, which has other issues.
Part of me wants to be wary. The useful life of industrial machinery such as CNC mills is much longer than the lifespan of websites, so locally-installed software you own is usually a better choice.
But another part of me realizes that everyone is using Fusion360, despite the fact they have a history of taking away features to force people to migrate to paid tiers. So it probably doesn't matter.
But browsers (and browser technologies) have documented track of being fully backward compatible up to the beginnings of WWW, and it's not going to change.
Which actually is much much better than any other environment you can imagine - unless of course you use (and want to use) that one frozen in time 25 year old PC. And pray nothing breaks (y2k bugs and whatnot).
If the software is open source (and works offline) you can have it functional in 10 or 20 more years. And it will be "locally-installed software you own" you want.
For comparison, I was looking at slicer source lately. Slic3r and its popular forks (prusa slicer, Bambu, orca) are using C++ with wxWidgets and boost. Sometimes outdated versions of those libraries at that. But stuff that will work, and totally local.
I have a CNC mill made in 2006. It's still perfectly fine. It should still be fine in 2036. The most significant threat to its existence is the compatibility of OS drivers and software support in CAM tools. That and USB ports getting replaced by something else, which was a problem for earlier-generation machines that used RS-232.
no shared lineage. Cura and Kiri started around the same time (2011/2012), but as completely separate projects. Cura is a C++ desktop app and Kiri has always been 100% browser-based (no cloud, all computation in the browser sandbox). the licenses are different, too. Cura/Prusa/Orca are GPL based and Kiri is MIT.
OT: Why is that Alphabet, Mozilla, Apple, etc can get together to create web standards that allow anyone to create software that works cross-platform - only a browser is needed, but Microsoft, Alphabet, Apple, Canonical, etc can't get together to create standards that allow anyone to create software that works cross-platform?
The API surface becomes the lowest common denominator of all the platforms it supports, possibly with a path to support platform-native features, but probably in a way that’s necessarily not as good as native.
I think we already have plenty of avenue in ‘solutions’ like Electron to let people build bad apps.
Apple make money from the App Store and from selling their hardware, so why should they want to invest on something that let people install software bypassing the App Store or that works on other platforms?
Alphabet make money from ads, so they want web pages, apps on Android and Chrome everywhere.
Mozilla make money from Google.
Microsoft make money from software licenses and subscriptions and from cloud services. They might be interested in cross platform installation.
At the moment what we have is PWA and WASM and icons on the desktop.
The browser is an extremely poor medium to deliver applications. It works, but barely, is a huge resource hog, fragile and it breaks way too often due to a lack of backwards compatibility between browser versions of the same manufacturer. I have a small app that I support and it's been fun to get it to work in the browser (instant cross platform support was indeed the driver) but the experience is still sub-par compared to what I could do on a local application.
There are many projects that try to make cross-platform mobile apps easier, including Google's own Flutter. I haven't heard of them getting much cooperation from the teams working on Android or iOS, though.
At least for stuff that doesn't use device API's much, it seems like websites are the way to go. They're a whole lot easier to build than mobile apps.
The boring answer from Capt. Obvious. Incentive alignment.
That said, WebAssembly might be the trojan horse. While it started as a browser compile target, WebAssembly System Interface (WASI) is extending it beyond browsers into filesystem, networking, etc. etc. etc.
Fingers crossed, we may get cross-platform standards by accident.
this. webkit is intentionally hobbled and years behind the standards. browsers on iOS are forced to use webkit for ginned up security excuses/reasons so that no real browsers that implement full standards can complete with heavily taxed app store spyware.
Am I weird in not being too surprised? It don't have experience with wire EDM but every toolpath generator or slicer I've ever used was just local software.
Also what's weird is that this project seems to be primarily written in javascript. I can't imagine that's a pleasant user experience for generating tool paths...
it's a combination of JS, WASM, and WebGPU. the JIT engines are so much faster than you would imagine, especially if you tune your code right. workers allow for parallel processing on all of your CPU cores. WebGPU, at least in Chrome, is kind of amazing.
For those wondering why having a browser based slicer is useful: teaching. The site mentions this, but I'll add my own experience that having good in-browser software like this is incredibly useful when you have a classroom full of students who a) aren't used to installing desktop software, b) are running a bunch of different operating systems (including chrome os), and c) have firewalls prevents them from installing local software anyway.
I wouldn't want online tools to be come the default (like google docs) but having them as an options is great. (I find onshape and photopea useful in this way as well).
Great tool for a Makerspace - really appreciate the ability to use the same tool for laser cutting, 3d printing, and CNC. These are big jumps for people typically - having a familiar tool would help people transition from one area to another.
Makerspaces and education are two areas of focus. no SW install, fully loads in under a second. through the Onshape integration and ability to run on Chromebooks, it's made its way into high school and university STEM curriculum.
This looks great. I was hoping it would have been a good OrcaSlicer replacement for my FDM printer, but unfortunately it didn't generate any top surfaces (except for the topmost one) for a model I imported in. I didn't know if it was the printer profile (Creality.Ender3) or something else, but it seems I'm still using OrcaSlicer for the time being.
there are desktop builds https://grid.space/downloads.html that run entirely offline. you can also use the center menu to "install" it as a progressive web app.
It says 'local first' doesn't that mean you can run it locally after downloading? That's how I set up pianojacq, just so there aren't going to be a lot of disappointed people that lose their practice logs if I get hit by bus #9.
I bought a bambu p1s recently and it can be used entirely offline.
You can import models to orcaslicer (open source), do your slicing, and export the g code file to SD card.
If you want to skip the SD card, block the printer's mac/ip address at the firewall and set up WiFi. Then send the print directly from orcaslicer.
That being said, my gut says bambu is going to slowly require a persistent connection to the cloud at some point. Maybe they think they are an EV car company.
Yes, you can use the P1S offline, but they've done everything possible to make it hard: crappy micro sd interface without the ability to use folders, USB plug absolutely inaccessible (see if you can even find it) and then, once you've found it it turns out that there is absolutely no way to use it to print with. They push you towards their closed source plugin 'for your benefit'. Fuck that stuff. There is absolutely no way I'm going to run a Chinese built piece of software that I can not inspect on my desktop. FOSS or bust.
I'm not so sure. You've had people insisting that, or how they'll lock it to only their own NFC tagged filaments but lets be real, if they start imposing serious restrictions most purchases would go to other makers.
They make solid enough devices sure, but they dont exactly have a moat that would keep users buying their stuff if it were to start getting locked down. They have far more to lose than they have to gain doing so.
Elegoo printers can be offline - you can run everything from the machine itself, as long as you have your model/s on a thumb drive. Or is that not what you mean?
- 100% free, no subscriptions, no accounts, no cloud
- Local-first: all slicing and toolpath generation runs on your machine
- Works in any browser, even offline once loaded
YES!
I think a new type of open source is emerging centering around what is now possible in browsers. Browsers have a great track record when running legacy projects. Relying on a backend could be a liability for longevity.
I built opal editor myself, a local first open source free markdown editor with these same principles, https://github.com/rbbydotdev/opal
> Works in any browser, even offline once loaded
That, my friend, is not how offline works. You will be required to have internet access in one way or another. Offline works 100% locally no matter if you have internet or not.
But you have to get the software somehow? Once you get it, it works offline. The same here I guess: once you download the source code/binaries into browser's cache (that can store things indefinitely) it's offline.
1 reply →
You're misunderstanding how websites work. You can install it locally on your computer and run it via localhost https://github.com/GridSpace/grid-apps
There's an electron build, although why you'd use it over a native slicer is beyond me.
Umm, I’m confused about this comment… the concept of a web app that gets saved into browser cache and then can be loaded and used while offline definitely isn’t new. See Photopea etc
Surprised this hasn't been shared here before.
Built by my former colleague, Stewart Allen (Co-Founder/CTO of WebMethods, CTO of AddThis, Co-Founder/CPO of IonQ, et al.).
What caught my attention:
- 100% free, no subscriptions, no accounts, no cloud
- Local-first: all slicing and toolpath generation runs on your machine
- Works in any browser, even offline once loaded
- Supports FDM/SLA, CNC milling, laser cutting, wire EDM
- Fully open source: github.com/GridSpace/grid-apps
Refreshing to see a tool that isn't trying to lock you into a subscription or harvest your data.
Any circuit designers? looking to hobby, but what I saw was all proprietary
You mean like PCBs? KiCad is pretty popular.
2 replies →
I've used kiri:moto for several simple CNC projects!
This probably won't scroll to the correct place on the page but there's some images of my project at https://hcc.haus/propmania/#2024-palm-torches and https://static.cloudygo.com/static/Prop%20Making/2024%20Palm...
I used it instead of the terrible closed source Easel App for a CARVEY hobby CNC. For metal milling I find Fusion 360 is necessary.
Curious if you can elaborate on what's missing or failing, to require Fusion 360?
probably adaptive milling, which will be in an upcoming release. sharp path changes in harder metals can wear or break tools if you don't go slow, which has other issues.
Part of me wants to be wary. The useful life of industrial machinery such as CNC mills is much longer than the lifespan of websites, so locally-installed software you own is usually a better choice.
But another part of me realizes that everyone is using Fusion360, despite the fact they have a history of taking away features to force people to migrate to paid tiers. So it probably doesn't matter.
> locally-installed software you own is usually a better choice.
It’s a good thing that’s exactly what this is, then.
> much longer than the lifespan of websites
But browsers (and browser technologies) have documented track of being fully backward compatible up to the beginnings of WWW, and it's not going to change.
Which actually is much much better than any other environment you can imagine - unless of course you use (and want to use) that one frozen in time 25 year old PC. And pray nothing breaks (y2k bugs and whatnot).
If the software is open source (and works offline) you can have it functional in 10 or 20 more years. And it will be "locally-installed software you own" you want.
For comparison, I was looking at slicer source lately. Slic3r and its popular forks (prusa slicer, Bambu, orca) are using C++ with wxWidgets and boost. Sometimes outdated versions of those libraries at that. But stuff that will work, and totally local.
of Kiri? it's in its 14th year. CAM was added in 2016, but the major work on that mode really kicked in around 2024.
I have a CNC mill made in 2006. It's still perfectly fine. It should still be fine in 2036. The most significant threat to its existence is the compatibility of OS drivers and software support in CAM tools. That and USB ports getting replaced by something else, which was a problem for earlier-generation machines that used RS-232.
1 reply →
More open source, browser-accessible tools is a good thing.
That said, aren't Prusa/Orca/etc. all already open-source (and part of the same lineage)?
no shared lineage. Cura and Kiri started around the same time (2011/2012), but as completely separate projects. Cura is a C++ desktop app and Kiri has always been 100% browser-based (no cloud, all computation in the browser sandbox). the licenses are different, too. Cura/Prusa/Orca are GPL based and Kiri is MIT.
I'm not talking about Kiri; I'm talking about the mainstream derivatives of Slic3r.
1 reply →
OT: Why is that Alphabet, Mozilla, Apple, etc can get together to create web standards that allow anyone to create software that works cross-platform - only a browser is needed, but Microsoft, Alphabet, Apple, Canonical, etc can't get together to create standards that allow anyone to create software that works cross-platform?
The API surface becomes the lowest common denominator of all the platforms it supports, possibly with a path to support platform-native features, but probably in a way that’s necessarily not as good as native.
I think we already have plenty of avenue in ‘solutions’ like Electron to let people build bad apps.
Apple make money from the App Store and from selling their hardware, so why should they want to invest on something that let people install software bypassing the App Store or that works on other platforms?
Alphabet make money from ads, so they want web pages, apps on Android and Chrome everywhere.
Mozilla make money from Google.
Microsoft make money from software licenses and subscriptions and from cloud services. They might be interested in cross platform installation.
At the moment what we have is PWA and WASM and icons on the desktop.
You answered the question yourself: There is already a standard that allows anyone to create software that works cross-platform: the browser.
> There is already a standard that allows anyone to create software that works cross-platform: the browser.
Which one exactly ? IE ? Dillo ? Lynx ? Pale Moon ? Firefox version 126 ?
The browser is an extremely poor medium to deliver applications. It works, but barely, is a huge resource hog, fragile and it breaks way too often due to a lack of backwards compatibility between browser versions of the same manufacturer. I have a small app that I support and it's been fun to get it to work in the browser (instant cross platform support was indeed the driver) but the experience is still sub-par compared to what I could do on a local application.
2 replies →
There are many projects that try to make cross-platform mobile apps easier, including Google's own Flutter. I haven't heard of them getting much cooperation from the teams working on Android or iOS, though.
At least for stuff that doesn't use device API's much, it seems like websites are the way to go. They're a whole lot easier to build than mobile apps.
Ah, I'm always up for a tangent.
The boring answer from Capt. Obvious. Incentive alignment.
That said, WebAssembly might be the trojan horse. While it started as a browser compile target, WebAssembly System Interface (WASI) is extending it beyond browsers into filesystem, networking, etc. etc. etc.
Fingers crossed, we may get cross-platform standards by accident.
Given you have two of the same names on both sides of the list, it looks like your question is self-contradictory. Could you clarify?
Apple ain't getting their 30% when you're running shit in your browser.
this. webkit is intentionally hobbled and years behind the standards. browsers on iOS are forced to use webkit for ginned up security excuses/reasons so that no real browsers that implement full standards can complete with heavily taxed app store spyware.
Don’t we have the jvm?
It doesn't have enough levels of abstraction, and, conpared to electron, it uses too few resources to be considered as a viable target by real men.
Simple. It is not in their interest to do this. It is a lot of work, for no revenue.
Am I weird in not being too surprised? It don't have experience with wire EDM but every toolpath generator or slicer I've ever used was just local software.
Bambu Labs ~recently had some drama around requiring an account / harvesting data for their machines. Might be what that's about.
IIRC this was about the machine firmware. Their slicer software is a fork of PrusaSlicer, which is OSS.
Bambu is great hardware but the software (and the firmware) is just terrible.
5 replies →
No, running locally is pretty standard.
Also what's weird is that this project seems to be primarily written in javascript. I can't imagine that's a pleasant user experience for generating tool paths...
it's a combination of JS, WASM, and WebGPU. the JIT engines are so much faster than you would imagine, especially if you tune your code right. workers allow for parallel processing on all of your CPU cores. WebGPU, at least in Chrome, is kind of amazing.
For those wondering why having a browser based slicer is useful: teaching. The site mentions this, but I'll add my own experience that having good in-browser software like this is incredibly useful when you have a classroom full of students who a) aren't used to installing desktop software, b) are running a bunch of different operating systems (including chrome os), and c) have firewalls prevents them from installing local software anyway.
I wouldn't want online tools to be come the default (like google docs) but having them as an options is great. (I find onshape and photopea useful in this way as well).
Great tool for a Makerspace - really appreciate the ability to use the same tool for laser cutting, 3d printing, and CNC. These are big jumps for people typically - having a familiar tool would help people transition from one area to another.
Makerspaces and education are two areas of focus. no SW install, fully loads in under a second. through the Onshape integration and ability to run on Chromebooks, it's made its way into high school and university STEM curriculum.
This looks great. I was hoping it would have been a good OrcaSlicer replacement for my FDM printer, but unfortunately it didn't generate any top surfaces (except for the topmost one) for a model I imported in. I didn't know if it was the printer profile (Creality.Ender3) or something else, but it seems I'm still using OrcaSlicer for the time being.
this does look like a bug in the default Ender 3 profile. easily fixable.
It's a shame they don't have an actual application for a truly offline experience. If they had both, people could have their cake and eat it too.
there are desktop builds https://grid.space/downloads.html that run entirely offline. you can also use the center menu to "install" it as a progressive web app.
It says 'local first' doesn't that mean you can run it locally after downloading? That's how I set up pianojacq, just so there aren't going to be a lot of disappointed people that lose their practice logs if I get hit by bus #9.
Now if we can only get an offline printer…
I bought a bambu p1s recently and it can be used entirely offline.
You can import models to orcaslicer (open source), do your slicing, and export the g code file to SD card.
If you want to skip the SD card, block the printer's mac/ip address at the firewall and set up WiFi. Then send the print directly from orcaslicer.
That being said, my gut says bambu is going to slowly require a persistent connection to the cloud at some point. Maybe they think they are an EV car company.
Yes, you can use the P1S offline, but they've done everything possible to make it hard: crappy micro sd interface without the ability to use folders, USB plug absolutely inaccessible (see if you can even find it) and then, once you've found it it turns out that there is absolutely no way to use it to print with. They push you towards their closed source plugin 'for your benefit'. Fuck that stuff. There is absolutely no way I'm going to run a Chinese built piece of software that I can not inspect on my desktop. FOSS or bust.
I'm not so sure. You've had people insisting that, or how they'll lock it to only their own NFC tagged filaments but lets be real, if they start imposing serious restrictions most purchases would go to other makers.
They make solid enough devices sure, but they dont exactly have a moat that would keep users buying their stuff if it were to start getting locked down. They have far more to lose than they have to gain doing so.
Elegoo printers can be offline - you can run everything from the machine itself, as long as you have your model/s on a thumb drive. Or is that not what you mean?
https://youtu.be/kS-9ISzMhBM
They’re trying to introduce legislation that would require 3D printers to be online so that if you try to print a firearm, it won’t let you…
Granted, today, you can print offline.
Tomorrow? A firmware update might just brick it the next time it goes online or won’t be able to read the grbl
17 replies →
Same with Bambu's. They include microSD slots.
1 reply →
Prusas are easily offline, pop an SD card or USB in and print
And you can inspect their network code and traffic if you want.
All of my printers are offline?
Trivial to firewall them from the internet.
Stop it with “free forever”. It never ever is.
spend 30 seconds reading up first. fork it if you disagree.