←back to thread

324 points onnnon | 1 comments | | HN request time: 0s | source
Show context
fidotron ◴[] No.42729069[source]
This strikes me as curiously defensive, in that Canadian way of praising things that are obviously problematic to draw attention to them.

The wider noise around React Native is seemingly that it works, especially while iterating on things, but it makes the final 20% of work much harder than it already was. As one person put it to me recently “with RN you just have to face the fact you won’t be winning any design awards”.

What really amazes me is how far React Native and web React have separated, to the point using the web one is a complete non event.

replies(1): >>42729162 #
bloomingkales ◴[] No.42729162[source]
I just kinda looked around the Shopify app to get a feel for it. There are a few frameworks that tap into native view switching (transitioning between pages and tabs), which creates most of the native feeling (along with native view components like lists/menus/switches).

I don’t know why the quality of the app feels cheap, but it just feels so (the web views load in with zero ease, they just jank onto the screen. So while you have native screen transitioning, you still have this low quality feeling of a bad nypost article shitting out an ad popup on you. Hard to explain, but that’s my my general feeling).

Regardless, while not impressive, it’s in this non-impressiveness that informs my unwillingness to invest into native or something like Flutter. These apps are too simple to go through the hoops.

Shopify RN app is a good example of a mundane non-sexy tech decision.

Overall nothing beats CSS and JavaScript for UI, but even in 2025 we cannot reliably push 60fps.

replies(2): >>42729715 #>>42731159 #
mdhb ◴[] No.42731159[source]
Flutter does 120fps no problems and has for some time now. Its also a lot nicer to work with Dart than Typescript.
replies(1): >>42732100 #
phist_mcgee ◴[] No.42732100[source]
Entirely subjective and I would disagree with dart. JSX is one of the most important things react ever popularised in the frontend space.
replies(3): >>42732488 #>>42733786 #>>42736445 #
bloomingkales ◴[] No.42732488[source]
Perfect world:

JS and CSS compile to native, somehow.

My ability to do this

function App() () { const items = get(url); render(items) }

Does not exist on native. It's 2025. Why is this?

----

It's because we don't have literate programmers. They don't know how to speak CLEARLY.

replies(1): >>42732508 #
phist_mcgee ◴[] No.42732508[source]
>It's because we don't have literate programmers. They don't know how to speak CLEARLY.

Mate, I think this is a bit of a reach.

replies(1): >>42732551 #
1. bloomingkales ◴[] No.42732551[source]
It's a vent. I don't like writing comprehensive code for simple things. Philosophically, I believe code is a liability. Each line is a problem.

The article alludes to something people do. They wrote a whole lot of code to not write a whole lot of code. These are deep stories.