Graphite VS tauri

A tool which looks at this sort of thing which was mentioned here recently:

https://news.ycombinator.com/item?id=44118159

but which didn't seem to get much traction is:

https://pontus.granstrom.me/scrappy/

but it pretty much only works for JavaScript programmers and their friends (or folks interested in learning JavaScript).

Other tools which I'd like to put forward as meriting discussion in this context include:

- LyX --- making new layout files allows a user to create a customized tool for pretty much any sort of document they might wish to work on --- a front-end for LaTeX

- pyspread --- every cell being either a Python program or the output of a program, and the possibility of cells being an image allows one to do pretty much anything without the overhead of making or reading a file

- Ipe https://ipe.otfried.org/ --- an extensible drawing program, this really needs a simpler mechanism for that and I'd love to see a tool in the vector drawing space which addressed that --- perhaps the nascent https://graphite.rs/ ?

https://graphite.rs/ (still early in development) offers node-based editing.

2D Content Creation Tool (Open Source Photoshop?)

I was referring to the link posted to HN: https://graphite.rs/

I love Inkscape so much. I use it every other week to make presentations, slides or just simple graphics when I need it. I illustrated my thesis with it.

Another piece of 2D vector software that I use and recommend is Graphite [1]. It too is open source. Graphite has nodes and can be procedural in nature. Have them both in your graphics toolbox.

[1] https://github.com/GraphiteEditor/Graphite

There is also Graphite (https://graphite.rs/) which, unlike Gimp, has a modern architecture and very ambitious goals (Blender for 2D basically).

If you're interested in either computational geometry, layout/packing/constraints, or functional programming language concepts, those are all the math-related concepts that we're currently interacting with for Graphite, a 2D vector graphics editor that's aiming to become the next Blender (but for 2D instead of 3D). If that sounds interesting, I'd love to help get you started if you want to join our Discord and I can explain the math-related work that we need to get done. Cheers!

Early in the development journey, the decision came to use either Tauri or Electron to build the app. Using one of these frameworks offered a promising way to avoid writing native code for each platform (Windows, macOS, Linux). This meant a crucial choice needed consideration.

Tauri is a desktop application framework that serves as an alternative to Electron. (From Tauri v2, it also supports mobile apps.)

Tauri is a Rust-based library that enables you to build lightweight desktop applications by leveraging web technologies like HTML, CSS, and JavaScript for the UI. You can use any frontend framework of your choice that compiles to HTML, CSS, and JavaScript. Unlike Electron (a JavaScript desktop app development framework), which relies on Chromium and Node.js, Tauri uses the system's native web view.

Then I learned Tauri and used my favourite frontend framework SolidJS with TailwindCSS and DaisyUI to build the UI with MotionOne to add animations and Tauri to build the desktop/web/android/ios app.

tauri dev is incredibly slow

Are the memory benchmarks measured correctly?

This tauri issue suggests the common measurement approach might be wrong

https://github.com/tauri-apps/tauri/issues/5889

Also would be better to have specific startup time instead of "fast" (which is strange since electron is not known for fast startup)

Here is a whole story: https://github.com/tauri-apps/tauri/discussions/4089

tl;dr - Tauri uses platform's default implementation of a webview. On Windows it's WebView2 which reports back to MS.

I mean, most OSes already ship with a WebView component that you can use instead of shipping an entire browser runtime.

Wails does that: https://wails.io/

Tauri also does that: https://tauri.app/

That does help with the needed resources quite a bit: https://github.com/Elanis/web-to-desktop-framework-compariso...

Sadly it doesn’t change the memory usage much so the technology is still inherently wasteful, but on a certain level it feels like a lost battle - because web technologies often feel like the choice of least resistance when you want GUI software that will run on a bunch of platforms while not being annoying to develop (from the perspective of your run of the mill dev).

HTML/CSS can still be used for the frontend even without Electron. Some frameworks use the OS bundled web renderer instead:

- For Rust apps: https://github.com/tauri-apps/tauri

- For Go apps: https://github.com/wailsapp/wails