Hacker News Reader

Comment by scarface74 | Hacker News Reader

Probably the two most obvious architectural differences are that a) Flutter paints every pixel on the screen, whereas React Native uses

Why is it bad that a framework uses native components?

View on HN

"bad" does not feature in the sentence you quoted, nor in anything OP said.

He spoke as if it's an advantage. I honestly want to know if there is an advantage in redrawing the screen and not using native elements.

He gave an example of something that is not possible without writing native modules for each platform in React Native.

It's not bad for the framework; it's bad in the sense that widgets are similar but not identical across platforms -- if they exist at all. Flutter packing it's own widget layer guarantees uniform behaviour across platforms.

Flutter packing it's own widget layer guarantees uniform behaviour across platforms.

That's not a good thing...,we lived through that already with Java Swing.....

There's nothing bad providing you're using the native language of the platform. With React you have to go through bridge code to communicate with the native controls. So there's a level of indirection to and from the native control. Flutter communicates with its widgets directly so there's no level of indirection. The other major advantage is that it compiles to native code so performance is always going to be superior.

Since flutter paints every pixel on the screen, widgets will work same for every version of OSs. No more support library madness.

Reply on news.ycombinator.com