Skip to main content

Home/ Open Web/ Group items tagged webOS

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Gary Edwards

In Mobile, Fragmentation is Forever. Deal With It. - washingtonpost.com - 0 views

www.washingtonpost.com/...AR2010030402374.html

webkit-html5 OpenWeb-Standards Web-apps OpenWeb-Productivity-Platform

shared by Gary Edwards on 04 Mar 10 - Cached
  • Gary Edwards on 04 Mar 10
     
    I disagree with the authors conclusions here.  He misses some very significant developments.  Particularly around Google, WebKit, and WebKit-HTML5. For instance, there is this article out today; "Google Really is Giving Away Free Nexus One and Droid Handsets to Developers".  Also, Palm is working on a WiMAX/WiFi version of their WebOS (WebKit) smartphone for Sprint.  Sprint and ClearWire are pushing forward with a very aggressive WiMAX rollout in the USA.  San Francisco should go on line this year!   One of the more interesting things about the Sprint WiMAX plan is that they have a set fee of $69.00 per month that covers EVERYTHING; cellphone, WiMAX Web browsing, video, and data connectivity, texting (SMS) and VOIP.  Major Sprint competitors, Verizon, AT&T and TMobile charge $69 per month, but it only covers cellphone access.  Everything else is extra adn also at low speed/ low bandwidth.  3G at best.  WiMAX however is a 4G screamer.  It's also an open standard.  (Verizon FIOS and LTE are comparable and said to be coming soon, but they are proprietary technologies).   The Cable guys are itneresting in that they are major backers of WiMAX, but also have a bandwidth explosive technology called Docsis. There is an interesting article at TechCrunch, "In Mobile, Fragmentation is Forever. Deal With It."  I disagree entirely with the authors conclusion.  WebKit is capable of providing a universal HTML5 application developers layer for mobile and desktop browser computing.  It's supported by Apple, Google, Palm (WebOS), Nokia, RiMM (Blackberry) and others to such an extent that 85% of all smartphones shipped this year will either ship with WebKit or, an Opera browser compatible with the WebKit HTML5 document layout/rendering model.   I would even go as far as to say that WebKit-HTML5 owns the Web's document model and application layer for the future.  Excepting for Silverlight, which features the OOXML document model with over 500 million desktop develop
Gary Edwards

WebKit OS: Why Some Developers Think the Palm Pre Could Upstage the iPhone - 0 views

www.eweek.com/...2

webkit palm-pre webOS

shared by Gary Edwards on 28 Apr 09 - Cached
  • Gary Edwards on 28 Apr 09
     
    Todd Williams, vice president of technology and co-founder of Genuitec, which has been eyeing the Pre and its developer platform, said, "The Pre is the only phone that fully embraces the belief system that mobile Web applications are the way that enterprise mobile content will be delivered going forward. And the mobile Web is the only programming model for the Pre. WebOS is basically a WebKit-based browser that has been expanded into a complete operating system. Thus, the 'native' programming model for the Pre is HTML5/CSS3/JavaScript. There is no other model. Mojo is a JavaScript framework that provides easy integration and access with all 'on phone' content [contacts, calendar, etc.] so applications as rich as any phone's native applications can be built with modern Web technologies."
Gary Edwards

The real reason why Steve Jobs hates Flash - Charlie's Diary - 1 views

www.antipope.org/...hy-steve-jobs-hates-flash.html

shared by Gary Edwards on 30 Apr 10 - Cached
  • Flash is a cross platform development tool. It is not Adobe's goal to help developers write the best iPhone, iPod and iPad apps. It is their goal to help developers write cross platform apps."
  • he really does not want cross-platform apps that might divert attention and energy away from his application ecosystem
  • This is why there's a stench of panic hanging over silicon valley. this is why Apple have turned into paranoid security Nazis, why HP have just ditched Microsoft from a forthcoming major platform and splurged a billion-plus on buying up a near-failure; it's why everyone is terrified of Google: The PC revolution is almost coming to an end, and everyone's trying to work out a strategy for surviving the aftermath.
  • Gary Edwards on 30 Apr 10
     
    Excellent must read!  Best explanation of what is currently driving Silicon Valley.  Charlie puts all the pieces in context, provides expert perspective, and then pushes everything forward to describe a highly probable future.  MUST READ stuff! excerpts:  I've got a theory, and it's this: Steve Jobs believes he's gambling Apple's future - the future of a corporation with a market cap well over US $200Bn - on an all-or-nothing push into a new market. HP have woken up and smelled the forest fire, two or three years late; Microsoft are mired in a tar pit, unable to grasp that the inferno heading towards them is going to burn down the entire ecosystem in which they exist. There is the smell of panic in the air, and here's why ... We have known since the mid-1990s that the internet was the future of computing.  With increasing bandwidth, data doesn't need to be trapped in the hard drives of our desktop computers: data and interaction can follow us out into the world we live in. .....Wifi and 4G protocols will shortly be delivering 50-150mbps to whatever gizmo is in your pocket, over the air. ......  It's easier to lay a single fat fibre to a radio transciever station than it is to lay lots of thin fibres to everybody's front door.... Anyway, here's Steve Jobs' strategic dilemma in a nutshell: the PC industry as we have known it for a third of a century is beginning to die. PCs are becoming commodity items. The price of PCs and laptops is falling by about 50% per decade in real terms, despite performance simultaneously rising in real terms. The profit margin on a typical netbook or desktop PC is under 10%.  At the same time, wireless broadband is coming. As it does so, organizations and users will increasingly move their data out into the cloud (read: onto hordes of servers racked up high in anonymous data warehouses, owned and maintained by some large corporation like Google). Software will be delivered as a service to users wherever they are, via whatev
Paul Merrell

Hewlett-Packard Traded WebOS for This: The Autonomy Gamble - 0 views

www.readwriteweb.com/...ett-packard-traded-webos-f.php

HP Autonomy Google cms

shared by Paul Merrell on 21 Aug 11 - No Cached
  • Content management systems today continue to be based on the types of structured database systems about one or two steps more evolved than dBASE. We've known they would be insufficient for the task, but we've put off the problem of composing a new architecture. It's already too late for major IT companies to start that new architecture from square one; if a company has any hope of addressing this colossal, underappreciated problem, it will need to acquire the architectural project in progress. This is what Hewlett-Packard announced yesterday that it intends to do: acquire a software firm whose core product aims to supplant everything we know about databases, both the SQL kind and the Google kind. In its place would come a clustered approach whose goal is no less than to be the central repository for meaning in the world.
  • As CEO Apotheker told analysts yesterday, HP intends to exploit the prospects for using Autonomy's technology as a foundation for a content management system. For now, that CMS would be a project for what, on the surface, seems an unlikely department: the Imaging and Printing Group (IPG). Autonomy describes this technology - which it calls Intelligent Data Operating Layer (IDOL) - as nothing less than a replacement for, a complete substitute for, a revolutionary disruption of, Google.
  • Elsewhere in Autonomy's literature is a monkey wrench it hurls directly at Google, with hopes of messing up its gears. Here, the company attacks the value of Google's page ranking technology in the enterprise: "in many cases, the most popular information is also the most relevant. The importance or popularity of a Web page is approximated by counting the number of other pages that are linked to it, and by how frequently those pages are viewed by other users. This works quite well on the Internet but in the enterprise it is doomed to failure. Firstly, there are no native links between information in the enterprise. Secondly, if a user happens to be an expert, perhaps in the field of gallium arsenide laser diodes, there may be no one else interested in the subject, but it is still imperative that they find relevant information." This is what HP is buying: an opportunity to disrupt Google. If IDOL is every bit the next stage of database evolution that Autonomy makes it out to be, then HP (at least in its executives' own minds) is not surrendering to Google at all, as some consumer publications this morning are suggesting. As HP perceives it, rather than cutting off Google's left arm, it's targeting the gut.
Gary Edwards

Interview: Paul Cotton on Microsoft Participation in the W3C HTML Working Group - W3C Blog - 1 views

www.w3.org/...view_paul_cotton_on_micro.html

shared by Gary Edwards on 10 Mar 10 - Cached
  • As part of a series of interviews with W3C Members to learn more about their support for standards and participation in W3C, I'm talking to Paul Cotton from Microsoft and co-Chair of the W3C HTML Working Group.
    • Gary Edwards
      Gary Edwards on 10 Mar 10
       
      There's the W3C version of HTML5.  And then there's the WebKit version.  WebKit HTML5 is pushed forward by Google and Apple.  The methodology is that the WebKit developers submit innovations and advances back to the W3C HTML5 groups as "proposals".  The key is that WebKit does not wait for approval.  They make the submission and move on. The problem is that waiting for a snake pit of corporate competitors to approve your proposals and include them in the next rev of the specification does not make business sense.  Especially if the competitors are legacy burdened monopolist like Microsoft and IBM.   Google and Apple have to push WebKit HMTL5 forward.  Even Mozilla is now on the WebKit band wagon!  Nokia (QT), the RiMM Blackberry and Palm Pilot webOS are also on board.  The key to WebKit HTML5's success is the incredible marketshare of mobile-smartphone computing, and the pushback across the greater Web mobile-web computing devices are having. Does FaceBook wait for W3C HTML5?  Or do they chase the iPhone with a WebKit HTML5 website configuration and enhancement? That's a rhetorical question :)
Paul Merrell

WebKit and why open standards matter | Open Source - InfoWorld - 0 views

www.infoworld.com/...-why-open-standards-matter-032

Webkit comparisons

shared by Paul Merrell on 09 Oct 09 - Cached
  • Last week I wrote about the benefits of open standards versus open source. I argued that open standards provide greater protection against vendor lock-in than open source alone. I was reminded of this conclusion when reading Peter-Paul Koch's analysis of WebKit implementations. Thanks to Palm's Dion Almaer for pointing out the analysis. Readers know WebKit as the open source Web browser engine used by several mobile and PC Web browsers, including Apple's Safari, Google's Chrome, Palm's WebOS, and the Android Web browser. In fact, Wikipedia lists 19 browsers based on the open source WebKit browser engine. As you read on, keep in mind there is no standard that vendors using WebKit must adhere to or claim certification against. A WebKit-based browser is, well, whatever the vendor wants it to be.
  • Imagine if there were a WebKit standard and a compliance test suite that vendors had to certify against to use the WebKit brand. Customers and developers would gain protection against vendor lock-in that open standards deliver to a much higher degree than open source alone. I'm not naive enough to think that open standards equal "write once, run anywhere." But even if a WebKit open standard could drive a 50 percent improvement in compatibility across WebKit-based browsers, that would be something to write home about.
Gary Edwards

InfoQ: How to Design a Good API & Why it Matters - 0 views

www.infoq.com/...effective-api-design

java api webOS web-api joshua-bloch

shared by Gary Edwards on 01 Jul 09 - Cached
  • Gary Edwards on 01 Jul 09
     
    A video with slide presentation featuring Google's Joshua Bloch. The topic is Java API Summary: A well-written API can be a great asset to the organization that wrote it and to all that use it. Given the importance of good API design, surprisingly little has been written on the subject. In this talk (recorded at Javapolis), Java library designer Joshua Bloch teaches how to design good APIs, with many examples of what good and bad APIs look like.
1 - 7 of 7
Showing 20▼ items per page