Live data from Hacker News

Apache Cordova: after 10 months, I won't using it anymore

geekcoder.org

81–90 of 96 posts

Re: Apache Cordova: after 10 months, I won't using it anymore

#81
post #70
post #62

Can anyone using Xamarin chime in as to whether the situation there is better?

Well you are getting native app with xamarin, so it must be better.

I heard a talk lately by two students that came to the result that it was a lot time consuming to debug. You have to get from native-code failures to your JS implementation. But I didn't try it myself by now.

Re: Apache Cordova: after 10 months, I won't using it anymore

#82
post #17

This is a very bad article. The real problems with Cordova are: * Core functionality is broken between releases. If you ask in the IRC support channel, they will even tell you not to update if things work well! What if I need a new feature? * Documentation is absurdly horrible or even plain wrong. I have been told several times to refer to the source code to find out how something works. * If you face any problem, ch…

I think it was a great article. A lot of people go in with the assumptions that the author has. At my last position we used Cordova. Like you, I was against it from the beginning because it is so unlike native. Yet many are under the impression that using Cordova means writing half the amount of code and/or taking half the amount of time that it would take to write separate iOS and Android apps. They think it's possible for reasons specified in this article (generally: that experiences are native-like and development is not harder than native); namely:

- that it can be like native; I regularly heard from management "What is so difficult about CSS? Why is it taking so long to build widget X?"

- that there is no reason why it can't be fast; I regularly heard from management "iPhones have >1ghz processors after all -- why can't it be faster?!"

- that the plugin ecosystem is bad -- "Why can't we just do X? Why do we have to build this?"

I agree with your criticisms as well. The lack of documentation, plugins, breaking between releases, and general help is surely lacking. But this is by no means a "bad article."

Re: Apache Cordova: after 10 months, I won't using it anymore

#83
post #58
post #12

Hmmm, I note in his closing para: "Facebook wrote a good article when they have decided to switch from a web app to a native one." A three year old blog post from Facebook. Now the circle has turned with React and React Native…

So full circle that Facebook went C++ with their latest app. http://www.computerworld.com/article/2935408/app-development...

Interesting; looks like a hybrid approach:

"Counting by lines of code, roughly one-third of the codebase on each platform is shared C++ code."

Source: https://code.facebook.com/posts/498597036962415/under-the-ho...

They are using a custom version of Djinni for cross-platform support.

Looks like Microsoft is going down a similar path with Visual Studio:

https://www.visualstudio.com/en-us/features/cplusplus-mdd-vs...

Re: Apache Cordova: after 10 months, I won't using it anymore

#84

On performance, the new WKWebView on iOS (with Nitro JS + GPU rendering, including WebGL), and the Chromium webview on Android 5.0+ (or Crosswalk for Android 4.0+, similar features all round), radically changes the performance story. It's almost identical to the system browsers now. Facebook's comments about HTML5 were back in the dark ages when the webviews generally used horribly slow software rendering and didn't…

the facebook app used to be slow partly due to the fact that the devs working on it had no idea what they were doing (at the time, Facebook really stepped up their game lately).

The dev team at my ex company built a demo to show that the same app could have been made to perform acceptably using the right strategies.

https://www.sencha.com/blog/the-making-of-fastbook-an-html5-...

Re: Apache Cordova: after 10 months, I won't using it anymore

#85
post #12

Hmmm, I note in his closing para: "Facebook wrote a good article when they have decided to switch from a web app to a native one." A three year old blog post from Facebook. Now the circle has turned with React and React Native…

The team at facebook wasn't exactly the best at squeezing performance out of the browser to be fair. Their article was a little misinformed. I think they have learned a lot since then.

Re: Apache Cordova: after 10 months, I won't using it anymore

#86
post #36

HTML5 is working for Instagram and Apple Music, I don't think many people would say they're inherently slow.

Instagram and Apple Music aren't running through an abstraction layer than brings it's own variable overhead. It's not a good comparison.

I don't think of Cordova as much of an abstraction layer. They just expose things to the `window` global.

Re: Apache Cordova: after 10 months, I won't using it anymore

#87

I tried Cordova three weeks ago, on my Nexus 10 (Android 5.1.1). I wanted to have a native UI, so I tested angular-material and Polymer. I wasn't too happy with the result, due to stuttering animations kind of ruining the UX. Having a shared C++ code base and the respective native UI code works perfectly fine for me, so I wouldn't use Cordova again. I don't see why I should. I'm just as productive there as I am with…

react canvas renders at 60fps

https://github.com/Flipboard/react-canvas

Re: Apache Cordova: after 10 months, I won't using it anymore

#88

FUD. Ever heard of WebSQL for storing your data? After 10 months, you should have been able to work around nearly anything you mention in your article.

WebSQL is deprecated in both the latest versions of Chromium for Android and in iOS 9.

Re: Apache Cordova: after 10 months, I won't using it anymore

#89

FUD. Ever heard of WebSQL for storing your data? After 10 months, you should have been able to work around nearly anything you mention in your article.

WebSQL is deprecated in both the latest versions of Chromium for Android and in iOS 9.

Re: Apache Cordova: after 10 months, I won't using it anymore

#90
post #82
post #17

This is a very bad article. The real problems with Cordova are: * Core functionality is broken between releases. If you ask in the IRC support channel, they will even tell you not to update if things work well! What if I need a new feature? * Documentation is absurdly horrible or even plain wrong. I have been told several times to refer to the source code to find out how something works. * If you face any problem, ch…

I think it was a great article. A lot of people go in with the assumptions that the author has. At my last position we used Cordova. Like you, I was against it from the beginning because it is so unlike native. Yet many are under the impression that using Cordova means writing half the amount of code and/or taking half the amount of time that it would take to write separate iOS and Android apps. They think it's possi…

Non-engineers are the biggest problem building HTML5 apps.

Everyone from VPs, Directors, to HR knows HTML, and they all have opinion about how it should be. They all want you to build a Facebook like app with 2 developers and works on all platforms.

Post reply on HN