redbar0n

12 ms·

121.
by redbar0n 4y ago
Ah, good question. No, Tamagui is agnostic to both backend and fullstack frameworks. I can’t think of any fullstack frameworks that prescribe a styling/animation solution. The fullstack’ness usually ends with the data loading between c
122.
by redbar0n 4y ago
My pleasure! Inspired by your feedback I threw it into a blog post and expanded slightly on it: https://dev.to/redbar0n/the-railslaravel-experience-in-jsts-... If the post is useful, I’ll improve it based on feedback i
123.
by redbar0n 4y ago
Tamagui is always fully agnostic to backend choice, since it is specifically for UI styling/animation. Remix.run and RedwoodJS are two fullstack React frameworks that comes from old RoR folks who aim to recreate the Rails/Laravel
124.
by redbar0n 4y ago
This is great advice. It’s very helpful to have a step-by-step procedure to follow for such a transition.
125.
by redbar0n 4y ago
Same here. It seems to get slightly better in light mode (at least the horizontal one), so it’s probably related to style calculations under various themes. Luckily I’m confident it will be fixed pretty rapidly, judging by the steady releas
126.
by redbar0n 4y ago
Not really, unless you redesign your app using Tamagui. Your best bet is using React Native Web and removing dependency on the packages that don’t support web: remove/treeshake them, shim them (like RNW does with RN), or detect the pla
127.
by redbar0n 4y ago
Bundle size? Yes, esp with third party code. See https://qwik.builder.io for arguments why. On the value of MUI and what senior front end devs care about, you’d find this interesting (esp the linked youtube of Theo): https:&#x2
128.
by redbar0n 4y ago
Then you’ll be happy to read this from Facebook’s lead engineer for their (unreleased) style library StyleX: https://twitter.com/naman34/status/1599581414487359489
129.
by redbar0n 4y ago
You can. It says 20 kB gzipped in the blog post, with path to be reduced to under 10 kB in later versions.
130.
by redbar0n 4y ago
The great thing about it is that it basically gives you the benefits of CSS-in-JS on the web, but without the downsides, since it compiles away to atomic CSS (even ternaries!). It’s true that it’s marginally less performant than vanilla Rea
131.
by redbar0n 4y ago
Oh, that’s just mostly (afaik) the result of the tree flattening it does being an optimization of React, because it gives React less to handle in the first place. That’s why benchmarking framework render operations like krausest does doesn’
132.
by redbar0n 4y ago
The standard benchmark mentioned (krausest) is for JS frameworks. But Tamagui is not a framework. (It uses React as the framework on web, so would have similar perfomance to that in krausest.) Tamagui is a style and component library (plus
133.
by redbar0n 4y ago
The standard benchmark mentioned (krausest) is for JS frameworks. But Tamagui is not a framework. (It uses React as the framework on web, so would have similar perfomance to that in krausest.) Tamagui is a style and component library (plus
134.
by redbar0n 4y ago
I think he meant there’s no standardized benchmark for styling and component libraries, or optimizing compilers, all of which Tamagui are. (Tamagui isn’t a framework, so wouldn’t fit into krausest benchmark, as you know).
135.
by redbar0n 4y ago
On the contrary, data fetching and logic/state management is usually the most reusable. In any case they are independent of Tamagui itself.
136.
by redbar0n 4y ago
React Native, so yes to all: iOS, Android, Windows, macOS, tvOS, Web etc.
137.
by redbar0n 4y ago
scroll down to see the components :) the entire site is also made with Tamagui, so the landing page uses a lot of it, and you can see visuals and code of all the components in the docs.
138.
by redbar0n 4y ago
You could think of it as using React Native Web (RNW), but better. Tamagui is using a trimmed down version of it called react-native-web-lite which is trimmed for bundle size and perfomance: https://www.npmjs.com/package&#x2
139.
by redbar0n 4y ago
it works in iOS Safari here.
140.
Tamagui 1.0 – Cross-platform React apps in less time, with better performance(tamagui.dev)
373 points by redbar0n 4y ago|138 comments
141.
by redbar0n 4y ago
Here are some predictions on the Russo-Ukranian war, and the growth of App dev / JS frameworks, and modern styling solutions. Russo-Ukrainian War: 1. Ukraine winter offensive in Jan/Feb of 2023 will successfully drive the Russians
142.
by redbar0n 4y ago
oh, stop with the unbridled optimism!
143.
by redbar0n 4y ago
This will save Christmas.
144.
by redbar0n 4y ago
Thanks for sharing your insights! Why don't you need to 're-layout and re-draw the entire page on every update' on native? Animations that affect layout still affect layout when on native, right? Is the reason that JS (and&#
145.
by redbar0n 4y ago
That's interesting, and very ironic, since PWA's are supposed to be the lightweight option.. Did you try recently? Ionic has developed quite a bit the last years, it looks like. Did you try the same with a React Native app too?
146.
by redbar0n 4y ago
> ... so you have true cross platform apps(from desktop to android and ios), it's the only way to achieve that. There are many other viable ways for creating a cross-platform app: https://dev.to/this-is-learning&#x2F
147.
by redbar0n 4y ago
Fortunately there are modern alternatives to React, such as Solid, or Qwik (nearly no JS bundle up front). You can even ‘qwikify’ React components to use them with Qwik, and choose to only execute them on the server/edge, meaning the u
148.
by redbar0n 4y ago
at least there is a well established process of standardization on the web.. (however slow it is).
149.
by redbar0n 4y ago
noticeably worse in what ways?
150.
by redbar0n 4y ago
For a lot of (most?) apps not requiring native capabilities, I suspect it is. The web has come a long way since the days of FB ditching HTML5 in favor of creating React Native. Here are some recent comparison videos, using the exact same ap

More ›