Show HN: 300k lines of Java UI code running native in browser at desktop speed

Re:Show HN: 300k lines of Java UI code running native in bro... by fastball on Friday April 05, 2019 @12:09PM (#19583902)

I have never once "optimized solely for V8" (I honestly have no idea what runs better in Chrome vs. Firefox).

All I know is that I build an app as I think makes sense logically, and 100% of the time it runs faster / less hot in Chrome.

JS-heavy apps burn thru CPU cycles far more on FF than in Chrome.

I want to use FF as my daily driver, I really do. But it's real-world performance just doesn't cut it for me, and I don't think you can blame that on people "solely optimizing for Chrome", as V8 was a better engine at the moment of release, when nobody had had a chance to optimize for it.

[ Parent | on HN ]

Re:Show HN: 300k lines of Java UI code running native in bro... by kbenson on Friday April 05, 2019 @12:47PM (#19584417)

Do you develop and test using Chrome, or Firefox, or both? If you aren't testing in Firefox beyond "it displays correctly" but you are using Chrome for your normal development, and testing, you are de-facto optimizing for Chrome, because you'll notice slowness in Chrome and work around if, but that same thing may have been fast in Firefox, but you never noticed. That's what being the market leading browser grants them.

[ Parent | on HN ]

Re:Show HN: 300k lines of Java UI code running native in bro... by bzbarsky on Monday April 08, 2019 @04:44PM (#19608835)

Do you happen to have a link to a specific thing you built that runs faster in Chrome? I'd love to take a look at what's going on there...

[ Parent | on HN ]