111–120 of 166 posts
Earlier quoted context omitted.
>It seems like JavaScript is the new ActionScript Not even close.
Why not?
I was tasked with creating the phone app for the company I work for. Here are the key points: - The project took 2 months for me to learn the sencha framework AND to build the app from scratch (it's live in the app store). - The app performs well on the iphone 4, but the best performance is on the iphone 4S and later. - The Android version is not as smooth. It's significantly slower. This means it's not truly cross-p…
http://jairaj.org/2012/08/27/facebook-for-ios.html
Although I have to admit that Sencha's implementation isn't all that great. If you're going to offer an alternative, at least make it better than the other option.
Earlier quoted context omitted.
Why not?
It's a very strange comparison to me. JS is intrinsically tied to the DOM, HTML and Web technologies, the underlying VM has widely used open-source implementations (V8, WebKit, Gecko), and JavaScript is not controlled by any single company.
The browser itself used to be too slow for many use cases which led to Flash filling in the gap, but thankfully that's rapidly changing with improved JIT VMs and HTML5 standardization efforts (WebRTC e.a.) all leading to the eventual demise of Flash.
Hence; JavaScript is the new ActionScript.
P.S. They're both just ECMAScript flavors so in that sense I would say they're very close ;)
Earlier quoted context omitted.
What mess? HTML/CSS/JS is exceptionally good at building user interfaces. And you're on the right side of technology by attaching yourself to the HTML bandwagon. I would go as far as to say that if you're starting development on a new ("form-based") native app, your first choice should be HTML. You only go native if you have a very good reason to do so.
> HTML/CSS/JS is exceptionally good at building user > interfaces. Except they are not. Even with all the nice tools we have now: backbone.js, CoffeeScript, CSS preprocessors it is still a mess. Just take a look at all those struggling to get sane view management, event binding, notifications, callbacks: it is years behind mature native frameworks which has very little cruft. I really doubt all this mess can be solve…
Something about the premature roots of something evil something.
I have just finished a mobile app in HTML5. Although it works fine on iOS and Android 4.x, it caused many problems on Android 2.x. As Android 2.x still has more than 50% of Android market share it is a platform we cannot ignore. I am sticking to native development for now.
I agree with you. I was going to ask this same questoin. From TFA, they stated above. Well, that really sounds like Mark Zuckerberg didn't know what he was talking about at the beginning of this year!
A lot of people are still on Android 2.X as you have stated, and a lot of people are on slow Android devices. I know several people on ZTE Blades running 2.3 which were available over a year ago for less than £100. Sure, not the snappiest of devices, but usable. What is the HTML5 version going to be like for these users?
Blah blah blah, hardware limitations, you can't limit yourself to lowest denominator etc. But Facebook HAS to support all these users. And it's not just users in the western world. There are millions of users in third world countries who pretty much exclusively access Facebook from mobile phones, usually not the latest spec (or even close) or most up to date s/w version (I doubt many would even know how to update it).
I agree that web apps are the way to go. But it is VERY much going to depend on your target audience.
Earlier quoted context omitted.
What mess? HTML/CSS/JS is exceptionally good at building user interfaces. And you're on the right side of technology by attaching yourself to the HTML bandwagon. I would go as far as to say that if you're starting development on a new ("form-based") native app, your first choice should be HTML. You only go native if you have a very good reason to do so.
> HTML/CSS/JS is exceptionally good at building user > interfaces. Except they are not. Even with all the nice tools we have now: backbone.js, CoffeeScript, CSS preprocessors it is still a mess. Just take a look at all those struggling to get sane view management, event binding, notifications, callbacks: it is years behind mature native frameworks which has very little cruft. I really doubt all this mess can be solve…
Earlier quoted context omitted.
> after all that shamanic dance trying to get all this to work you will wonder, what's the point. Shamantic dance? It's trivial to the point of being a non-factor. You wrap your app in Phonegap, and make json requests to the web if you need data from there. Otherwise, it is stored and runs on the client. > Not many predict that desktop apps will be replaced by web apps soon, but for some reason this a popular view re…
> You wrap your app in Phonegap, and make json requests to > the web if you need data from there. You know what? I think you should try to do all those things you deem so easy, and then we can talk. Or you can google for phonegap success stories. > For most things, desktop apps were replaced by web apps Can you name a few? I was impressed with GMail in 2004, in 2012 I am using Sparrow to read and write my email. > In…
I'm not going to touch the rest of your comments but mutability of presentation is really not the place to wage your battle against HTML/CSS/JS from. Dynamic presentation is really web tech's strong point.
Earlier quoted context omitted.
IMO as soon as you want to support two platforms natively you've nearly doubled your work.
And if you try to support them by doing web based app you quadrupled your work, only it is on the same code base.