Myth debunking: WebViews suck, everything should be native

Re:Myth debunking: WebViews suck, everything should be native by kendallpark on Sunday June 12, 2016 @10:34AM (#11888247)

All my mobile dev friends cry, native, native, native!

On the desktop, I use both Slack and Atom on the regular and haven't had any issues. (Or at least, not since since they did some optimization of Atom.)

I'm curious how React Native's "learn once, write twice" philosophy will play out in this ongoing native vs webview argument.

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by jonhohle on Sunday June 12, 2016 @11:10AM (#11888410)

Atom was notorious for not being able to open moderately sized files earlier in its life: https://github.com/atom/atom/issues/307

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by bjterry on Sunday June 12, 2016 @12:44PM (#11888943)

I regularly have issues with Slack's desktop app using a tremendous amount of CPU and memory given the functionality it's offering.

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by dham on Sunday June 12, 2016 @03:22PM (#11889807)

My coworker has a Mac Pro with 64GB of ram and regular posts screenshots of Slack and Spotify using 20GB + of ram. Granted he never closes those app ever, until they become a problem.

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by ch4s3 on Sunday June 12, 2016 @01:38PM (#11889222)

Same. I regularly notice it using upwards of 1.5GB of ram.

[ Parent | on HN ]

Re:Myth debunking: WebViews suck, everything should be native by wyager on Sunday June 12, 2016 @12:12PM (#11888745)

Atom is horrendously slow. The only reason I use it over sublime is that it has better plugins.

[ Parent | on HN ]