solvespace VS tauri

Can second this!

However, I would recommend https://solvespace.com! It hits a sweet spot between features vs complexity/learning effort.

We use rebase on solvespace, along with sensible squashing so most commits along master are pretty self contained. You can see the clean history here:

https://github.com/solvespace/solvespace/commits/master/

I changed a behavior to the "more standard" one because it felt obviously right. This was a 3 line change. But the was enough backlash right there in the pull request. So I spent a couple hours remembering how to add a configuration option to keep the old way for those guys:

https://github.com/solvespace/solvespace/pull/1425

> If you like Linkage, you might also like Solvespace.

No, I mean Brent Curry's Linkage[1] bicycle design software, not David Rector's Linkage Mechanism Designer and Simulator[2].

You should read Wikipedia article.[0]

N.B. About SolveSpace, as I'm its experienced user[youtube,patreon], I may say next: yes, it could be used for bike mockup, as any other CAD, but it still has a lot of limitations and even does not export correct STEP files yet[3], and in FreeCAD such STEP could fixed only partially.[video]

So, for serious 3D CAD work I highly recommend use FreeCAD (and LibreCAD for 2D CAD work) instead of SolveSpace, and use SolveSpace only as a helper tool like a calc or as a notepad for noting ideas.

About Linkage Mechanism Designer and Simulator, it is only useful for planar (2D) kinematics analyze, and if You are looking an alternative for it take a look on Pyslvs[4], that is in part based on SolveSpace's solver.

[0] https://en.wikipedia.org/wiki/rattleCAD#History

[1] https://bikechecker.com/

[2] https://blog.rectorsquid.com/linkage-mechanism-designer-and-...

[3] https://github.com/solvespace/solvespace/issues/206

[4] https://github.com/KmolYuan/Pyslvs-UI

[video] https://www.youtube.com/watch?v=F3LJMeqUDrU

[youtube] https://www.youtube.com/@appsoft

[patreon] https://patreon.com/app4soft

C++ this file covers all the math for working with NURBS curves and surfaces:

https://github.com/solvespace/solvespace/blob/master/src/srf...

There is a lot more in other files - triangulation, booleans, creation - but the core math functions are there in very readable form.

>> Maybe somebody has statistical survey of how much of the existing deployed CPU core count is typically used?

My guess is very few cores are used on average. I did some testing with Solvespace to see which build options contributed most to performance:

https://github.com/solvespace/solvespace/issues/972

Obviously using OpenMP for multi-core was the big win. But what's not shown is that in typical usage (not the test I ran) if you're dragging some geometry around it will use all cores (in my case 4 cores / 8 threads) at about 50 percent utilization. That percentage probably drops as more cores are thrown at it due to Amdahl's Law. In other words, throwing double the cores at it will give a good boost to a lot of code that is already taking less than half the time (wall clock time, not CPU time).

We added OpenMP to a number of functions for significant performance gains. And in fact, any remining single-thread operation that gets the parallel treatment is likely to have a significant impact on overall performance since that is where most of the time is spent now. At this point we're more focused on features and bugs.

Algorithmic improvements are possible and I'd like to do those in the future, but they are much harder to do than sprinkling some #pragmas around critical loops. That will improve the scalability though, where multithreading really did not.

Hi, dear Tauri! Long time no see. I published my first post, Developing a Desktop Application via Rust and NextJS. The Tauri Way almost a year ago. Since then, Tauri has become stronger. I'm happy about that! And now, I am very pleased to make a useful contribution to the Tauri community. As a full-stack developer, I frequently face situations where I need to start a DB-based UI project as fast as possible. It's stressful if I need to start the project from 100% scratch. I prefer to keep some boilerplates on hand, which will save me time and nerves and will be the subject of this article.

Hey Thanks!

Just electron & vite. I might actually migrate off electron, Tauri (https://tauri.app/) seems to be getting more stable and it's gotten great reviews.

I think this is the boilerplate I used though https://github.com/cawa-93/vite-electron-builder.

Well the great thing about WebAssembly is that you can port QT or anything else to be at a layer below -- thanks to WebAssembly Interface Types[0] and the Component Model specification that works underneath that.

To over-simplify, the Component Model manages language interop, and WIT constrains the boundaries with interfaces.

IMO the problem here is defining a 90% solution for most window, tab, button, etc management, then building embeddings in QT, Flutter/Skia, and other lower level engines. Getting a good cross-platform way of doing data passing, triggering re-renders, serializing window state is probably the meat of the interesting work.

On top of that, you really need great UX. This is normally where projects fall short -- why should I use this solution instead of something like Tauri[2] which is excellent or Electron?

[0]: https://github.com/WebAssembly/component-model/blob/main/des...

[1]: https://github.com/WebAssembly/component-model/blob/main/des...

[2]: https://tauri.app/

Welcome to the 2nd episode of our series “Building with Tauri”, where we chat with developers who build amazing projects and products using Tauri.

Tauri seemed like the "thing" I should switch to because everybody loves Rust (heh), and because it ships significantly smaller apps.

First of all, I will be using npm as my package manager but feel free to use whatever you prefer. Find more info here.

Today I'm talking about Tauri! Do you know all the various tools that allow you to develop native applications starting from web languages? They often need an intermediate compilation, in the middle of which you end up encountering various problems not always transparent and directly solvable with a language mostly detached from native development. On the other hand, there's still the ease of developing attractive and easily usable interfaces, which are more difficult to develop with low level languages.