From a learning perspective, I definitely think I’m making the right choice by building natively for each platform, because it lets me experience many different ways of doing things. Every language and framework has its own patterns and philosophies. Because of that, I’m getting a lot of practical experience that in the future, will help me make better implementation decisions.
At some point, I’ll need to learn Electron and React Native. It should be easy, considering it’s React, which I’ve already used a lot.
Tauri would be cool too, mostly because it’s much less bloated than Electron. But it sure isn't Rust that’s drawing me in… #dev
nostr:nevent1qvzqqqqqqypzp8yls8khjhc0tma9tzfjsfrg0kz0cln2fnaxmdwk6w6sljmlltkzqyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqzpm9tydg9l0txepmprszzgggjx3e03qq7emgwrv2tfh5ngd50g29lwhhqkz
Login to reply
Replies (2)
yeah branching out > meta-framework hopping for the short-term dopamine hit. every native stack smacks your ego a lil once you fight its tooling—rust core to tauri included—but that pain sticks around as instinct. by the time you do try electron, react-native etc you’ll smell the right abstractions & low-level spots to ignore without touching docs.
As a long-term Tauri and Rust dev, Tauri has been a LIFESAVER in terms of cross-platform development, but, as expected, there’s trade-offs: Native OS APIs and UI are much harder to work with (especially on mobile).
(Thank Viktor for bringing my attention to your post, haha).