Just implement an additional back button on the SPA. This is actually not confusing and is done in some places. Navigation buttons within an SPA are common enough.

No, You SPA should have it's own back button within the app. My browser back button should get me out of there no matter what.

Any other way? Just build a web app with emscripten. You can do anything.

For a while GTK had an HTML5 backend so you could build whole GUI apps for web, but I think it got dropped because nobody used it.

I keep coming back to that. Nobody has ever directly seen direct the force carrying particles, only their effects (indirect evidence). The models make excellent predictions, but I still feel like they're "wrong" in some sense.

TDF needs to eject the members who pulled the strings hardest on this - they are plants.

Damn I didn't know I had that much of a tinfoil hat.

That credit goes to whitequark, who quit solvespace maintainership in 2020. The branch lingered and suffered some bit-rot. Then a couple people brought it up to date and fixed a few issues. It seemed like a good idea to merge it to prevent it falling behind even though its not quite up to par with desktop. With the newest release we also opted to put this right on the site (even merged a PR today as a result).

Anyway we owe whitequark most the credit for this one even though we havent heard from her in several years.

That 3MB also includes gnu unifont, the builtin vector font, and the 3js viewer for when you export models to html (viewer gets bundled in the file)

Dune3D is more like Solvespace with a few improvements and bug fixes vs being anywhere near FreeCAD in terms of capability. Improvements include using STEP files in assemblies and having some ability to make Fillets or Chamfers. Bugs fixes would be due to using OCCT for NURBS surfaces - solvespace frequently fails with NURBS boolean operations.

As for overall capability, FreeCAD does everything these others do but also supports lofting and other modeling options, BIM for architecture, I think it does pre- and post- processing for FEA, and maybe some other "big tool" things.

It would, and it has been considered. The sketch elements in solvespace are significantly decoupled from the solid model. That means we could substitute (via wrapper maybe) an OCCT object instead of our SShell class. Then you'd have to change a set of solvespace curves to OCCT curves to make extrusions from them and such. But that would be most of the work.

We do tag all triangles in the mesh with a sketch entity handle for flat surfaces so you can constrain points to a face. I'm not sure how that would be handled. We will also be tagging edges of the solid with sketch entity handles in the future so we can do chamfers and fillets - say by selecting a line entity and applying a modifier to it which gets applied to the NURBS shell. I'm not sure how that would go with OCCT.

But yes I've given a bit of thought to it ;-)

I didn't start Solvespace, but Jonathan was apparently in a DIY mode after developing his take on constraint-based sketching. It's also very easy to go from NURBS curves to NURBS surfaces, the challenge begins at boolean operations which continue to be a source of bugs for us. This is really the only option other than OCCT and the code is small and approachable so I try to make it better.

Or middle mouse button / click the scroll wheel.