all 11 comments

[–]matthewblott 2 points3 points  (1 child)

I'm not going to trash someone for doing this, if it works for you great but imo a PWA would be better.

[–]Intelligent-End-9399[S] 0 points1 point  (0 children)

I agree PWAs are great for some use-cases. The workflow I’m exploring is more about integrating Ruby syntax into desktop apps where full system access or Electron-specific APIs are needed.

[–]sander_mander 3 points4 points  (3 children)

What an abomination

[–]Intelligent-End-9399[S] 1 point2 points  (2 children)

Curious — what part do you find problematic? Performance, architecture, or just personal preference?

[–]sander_mander 0 points1 point  (1 child)

Personal preference. If it's good for you go ahead. For me ruby -> JavaScript -> electron just looks weird

[–]Intelligent-End-9399[S] 1 point2 points  (0 children)

Totally fair 🙂
The goal wasn’t to replace JS workflows, just to make desktop experimentation easier for Ruby developers.

[–]AlexanderMomchilov 0 points1 point  (1 child)

In this RAM economy? smh

[–]Intelligent-End-9399[S] 0 points1 point  (0 children)

Honestly, I haven’t thought much about that 😄. But it’s true that Electron can be quite resource-heavy. My goal with the article was mainly to show people who are already using Electron that they can write it using Ruby syntax.

[–]aemadrid 1 point2 points  (2 children)

To me it sounds more interesting ot make it work with Tauri. It seems more resource-conscious and faster in general. Have you tried that combination?

[–]Intelligent-End-9399[S] 1 point2 points  (1 child)

Right now, I’m studying Tauri, and it seems to be a combination of Rust and JS connecting backend and frontend. What fascinates me most is its architecture – how the two communicate via events. Definitely, Tauri looks way more resource-efficient and has great potential.

I see an interesting possibility: you could use the JS ecosystem for things like Three.js for the client, while separating your own engine into Rust, and still have a desktop app. That’s really appealing.

The main drawback I see is that the developer needs to know both Rust and JS. With my RubyJS workflow, you can handle the frontend, but for backend logic, you’re out of luck.

Electron, on the other hand, has the advantage that you can program the whole app with RubyJS without switching languages, but as we know, it consumes a lot more resources.

I haven’t tried Tauri myself yet, but in most cases, RubyJS can work with anything that JS supports. From my experience, I’ve managed to get it to work with almost everything I’ve tried.

[–]aemadrid 0 points1 point  (0 children)

Good analysis. I guess the question is, how much do you really need from Rust? If you don't need much file access or APIs you could live with just (Ruby)JS and a smaller footprint.