Javascript Gains While HTML5 Stalls

Mobile application developers are increasingly moving in the direction of Javascript while at the same time losing their enthusiasm for HTML5. According to a new survey of 6,698 mobile application developers conducted by International Data Corp. on behalf of appcelerator, a provider of tools for building mobile applications, 47.3 percent ranked JavaScript as the most relevant programming language they use today. By comparison, Java came in second at 35 percent while Objective C was third with 32 percent.

Img Credit:

Perhaps more significantly, 88 percent of the developers surveyed found it likely or very likely that in 2014 JavaScript would dominate both client and server side application development.

According to Michael King, director of enterprise strategy for appcelerator, JavaScript is being pulled into the cloud by the rapid embrace of Node.js to build back-end applications. As such, JavaScript now plays a significant role in allowing developers to build browser-agnostic mobile applications that can more easily invoke cloud application services.

As a result, King says, JavaScript is now well on its way to become the “lingua franca” for building mobile computing applications.

Over the last couple of years, JavaScript emerged as a significant force because it allows developers to build robust applications that run inside the browser. JavaScript, which was first widely adopted for use in consumer applications, is increasingly being used to build a new generation of enterprise applications. Looker Data Sciences has developed a business intelligence application written mostly in JavaScript that allows user to leverage a real-time processing engine to directly access multiple sources of Big Data.

While JavaScript is in the ascendency, however, enthusiasm for HTML5 appears to be waning. The number of survey respondents who are “very interested” in building applications using HTML5 fell to 59.9 percent—the lowest level since appcelerator began tracking the specification in April 2011. Interest in HTML5 peaked in July 2012 at 72.7 percent.

There were many issues with HTML5 and the latest release of Apple iOS clearly didn’t help matters, King notes. However, as developers gain more experience with HTML5, it's clear that the proverbial bloom is off the HTML5 rose as a panacea for mobile application development. A big part of that disenchantment is that various browsers support HTML5 differently.

Although there will probably never be a perfect mobile application development scenario, use of these devices on the Web is skyrocketing. Therefore, developers cannot ignore mobile computing, but must understand there’s still a lack of maturity when it comes to mobile computing standards.

Be sure to read the next News Services article: Nutritionix Plans to Launch Nutrition Label Transcription API


Comments (3)


HTML is not a programming language, it is markup to be used by JavaScript or CSS. The article also fails to note that HTML is not at all used server-sode except to build pages for the client. So it is not very fair to compare one to the other. Regardless, client side JavaScript will continue to rely on HTML. It would be more useful to compare a traditional JavaScript library jQuery to, which uses only CSS3 to replace HTML.

I will throw the draft for my upcoming article on HTML5 and JS, the biggest corporate bullying scam in the entire history of the Internet.

Setting the Record Straight

Facebook, Linked, Goko, Wooga, Blossom are just a few companies who broke their teeth on HTML5 and decided to partially or completely dump it, calling it a "failure", their "biggest mistake" with Google calling JavaScript, the programming language on which it is based, a “flawed” language that "cannot be fixed" by merely changing it.

And those are just the few who had either the courage, honesty, corporate duty to shareholders, or business responsibility toward developers to be honest and public about it. Thousands fail silently every day, too embarrassed to admit it publicly, or too small to counter the attack of the water carriers from Apple and the opportunistic HTML5 vendors, when not plain simple fake social personas operated by publicity and marketing staff on payroll, all flooding the web with lies and misleading truth.

Facebook dumped HTML5 saying it is the "biggest mistake" in the company's history. #FAIL

LinkedIn dumped HTML5 saying it was a mistake to adopt it: #FAIL

Goko’s HTML5 game portal went back to beta after failed launch, blowing up on first day. #FAIL

Wooga, the second largest game developer on Facebook, dumped HTML5 after hitting the wall as one of the adopters of Facebook's failed HTML5 platform codename "Spartan". #FAIL,2817,2406187,00.asp

Google recognized that JavaScript, and therefore HTML5, are failures with flaws that cannot be fixed. #FAIL

Technical facts

HTML5 is based on a bogus programming language that's not even one, but an interpreted script. It takes a rocket scientist to hack HTML5 and make it work, rocket scientists most companies cannot afford, and most of the time cannot find even when they can afford them. #FAIL

HTML5 consists in putting band-aids on a chicken dead in the egg, to make it work across browsers on life support. Forget mobile, desktop, TV. Each new destination is more hacking, discrepancies & failures. #FAIL

HTML5 is a failure because of its nature: implementation left to the browser, with vendors free to implement it how, when & if they want. Features might work in 1 browser but not the other, or not work & look the same, or not at all. #FAIL

That is when vendors don't cripple it on purpose, such as Apple executives marking HTML5 bugs not to be fixed by executive order. That is Apple execs ordering Safari mobile engineers not to fix bugs that refrain HTML5 from competing with AppStore & iTunes. #FAIL

As a result, we see mind blowing facts such as iOS7 plagued with HTML5 bugs. Don't tell me Apple does not have the money & talents to avoid that! #FAIL

Corporate Bullying

HTML5 is the biggest corporate bullying scam in the entire history of the Internet & is costing enterprises hundreds of millions. Most HTML5 web "developers" are costing enterprises 2x to 5x more money than Flash/Flex/AIR experts because they spend more time, by multiple folds, to develop apps which mostly fail, do not look right, do not feel right, or do not behave right across browsers and platforms, especially on mobile…. How funny! Compare that with Flash/AIR apps that work the same everywhere from 1 single code base, with 1 team instead of 2 to 4, & all based on a rock solid enterprise class object oriented programming called AS3, not to be confused with AS2 used to build old school Flash animations and ads and just as bad as JavaScript.

Antitrust Scam

It is because Flash / Flex and AIR are too good that Jobs banned Flash as part of its vendetta on Adobe, which pushed for a "develop once, deploy everywhere" business model which is a threat to Jobs' monomaniac and megalomaniac close business model. Flash was banned to protect the artificial supremacy of the AppStore and iTunes. It is because HTML5 / JS are a failure that Jobs, smarter than anyone else, pushed it to serve as a decoy to distract the attention from the vendetta on Adobe and attempt, I repeat "attempt", to assassinate Flash. Fortunately, it triggered a preliminary joint antitrust preliminary investigation of Apple by FTC and EU Commission, and the regulators constrained Apple to support Adobe AIR, a technology used to run Flash apps on the iOS platform. Adobe also learned the lesson and put its money back where its mouth is, making develop once, deploy everywhere a reality again with performances at parity with native apps and 10 fold performance improvement in the browser:

The mobile browser is the only 1 destination where HTML5 makes sense, not because it is good, but because it is a failure, that is how Jobs wanted it. Jobs wanted everyone to fail with it in the browser, left with no alternative since Apple banned not just Flash but also Silverlight & Java, every single serious app technology allowing to compete with native apps from the browser, making everyone fall back to native app & self-enroll for a racketeering 30% tax. He was a genius, I give you that much & he is laughing & finger pointing at HTML5 developers & adopters from the other side all the way to Hell Bank.

Did not I say so three years ago?

In 2010 I told Sheryl Sandberg, COO of Facebook that they will fail by adopting HTML5. A few years later Zuckerberg went on the record to apologize to his shareholders & called it "the biggest mistake" in the company's history, after spending millions in a project codename "Spartan", an HTML5 platform with which they try to take on the AppStore, which failed miserably, failed the company's entry to the mobile market, therefore failing their IPO. They should have read my blog more attentively instead of listening to a bunch of developer kids straight from school.

Html5 APIs require javascript in order to use them, so I'm not sure what the author's point is here.