Category Archives: web authoring

Google names its Chrome OS partners – including Adobe

Google has posted a Chrome OS FAQ, in which it lists its partners for the new operating system. This features the usual suspects in terms of PC and hardware vendors – though no Dell as yet – but with one interesting addition. Adobe:

The Google Chrome OS team is currently working with a number of technology companies to design and build devices that deliver an extraordinary end user experience. Among others, these companies include Acer, Adobe, ASUS, Freescale, Hewlett-Packard, Lenovo, Qualcomm, Texas Instruments, and Toshiba.

Adobe is the only pure software company listed. What is the significance? My assumption is that Google intends its Chrome OS to work well with Adobe Flash, needed for compatibility with a zillion web sites out there, and to support multimedia such as the BBC iPlayer. Adobe will also want to get its offline, desktop runtime, called AIR, onto the device; and seeing the company named here makes that even more likely. Put this together with Chrome’s fast JavaScript engine and innovations like O3D – hardware-accelerated graphics for the browser – and my guess is that this will make an excellent platform for Rich Internet Applications and multimedia.

If there is a war between HTML 5 and Flash, Google is more aligned with HTML 5; but that won’t get in the way of excellent Flash support in Chrome OS.

Technorati Tags: ,,,,,

Mozilla takes aim at Flash and Silverlight with Firefox 3.5

I reviewed Firefox 3.5 for The Register. I found the new features unexciting from a user perspective, but not so for developers. The new TraceMonkey JavaScript engine, improvements to the Canvas element, JavaScript threading and various bits of HTML 5.0 make this a more powerful platform for web applications – provided that you workaround the problem of users with Internet Explorer. The arrival of video and audio elements is also worth highlighting:

Another new feature is SVG effects for HTML, including masking, filtering and clipping. The point I made in the review is that this is a shot at Adobe as well as Microsoft. Although it is a long way from a viable alternative to Flash for now, the direction is clear.

That does not mean it will succeed. On the other hand, if Apple, Google and Mozilla pull together in making browser standards rich enough not to need plug-ins for most of the scenarios where Flash is used today, this could disrupt Flash momentum.

What about IE? That’s the big question. Here’s a few questions:

1. Will Microsoft implement these standards or hold back, arguing that Silverlight makes them unnecessary?

2. Will IE retain its market dominance – still over 65% last time I looked, even though it is losing among developers and influencers?

3. Could IE add-ons along the lines of Screaming Monkey for JavaScript and the Mozilla Canvas plug-in that has been discussed pull IE along anyway?

This article by Ryan Paul from last year discusses the issue. He says, why shouldn’t Adobe embrace HTML 5.0 rather than fighting it:

Although Canvas arguably competes with Adobe’s Flash plugin in a certain set of use cases, it’s worth noting that Adobe doesn’t generate revenue from the Flash plugin itself. Adobe cashes in on Flash by selling its powerful authoring tools, which the company could easily extend to support standards-based web technologies.

It’s a fair point; but given the commercial advantages of owning the platform, as opposed to being just another tools vendor, I doubt Adobe would make this shift unless it saw no realistic alternative. Even fully open-sourcing the Flash runtime would be less risky.

You can find Firefox here, and the developer features are described here.

What next for Adobe LiveCycle ES?

Yesterday I met Adobe’s Duane Nickull for a chat about the company’s efforts in SOA. Nickull is a battle-scarred enterprise architect with a deep knowledge of SOA standards, who is now a senior technical evangelist for Adobe. He represents what I think of as the other Adobe: not the company that does things you would not believe in Photoshop, but the one that has created an end-to-end development platform with LiveCycle Enterprise Suite (plus your favourite application server) at one end, and Flex at the other.

It is an aspect of Adobe that deserves more attention. For example, this note in Anil Channapa’s What’s New in LiveCycle Data Services 3 caught my attention:

The LiveCycle Data Services 3 beta supports an acknowledge capability that enables all communications between Flex-based applications for Flash and the LiveCycle Data Services server to be guaranteed. All that you have to do is mark the LiveCycle Data Services 3 beta server destination as reliable.

I think this is huge. As Channapa goes on to note, for developers contemplating ecommerce or financial applications, this is a key feature.

I learned from Nickull that this feature is based on WS-RX and that in general we should expect more WS-* implementations to turn up in LiveCycle ES. RESTafarians will be sceptical, but I suspect this will help Adobe to make inroads into enterprise development.

That said, I do think Adobe has issues positioning and promoting LiveCycle ES. The more glitzy Creative Suite tends to grab all the attention, and indeed accounts for by far the largest slice of Adobe’s revenue. When I attended MAX in Milan last year, I don’t recall any mention for LiveCycle in the keynotes; it was one of those things you had to discover, though there were some excellent sessions on the subject.

I think Adobe should push LiveCycle ES harder, particularly as a business model based mainly on selling a huge suite of design tools strikes me as precarious. Adobe is making a start and has announced a LiveCycle@MAX bundle for MAX 2009 [warning: autoplay sound] in early October.

The LiveCycle ES brand encompasses what used to be Macromedia’s Flex Data Services as well as Adobe’s PDF-oriented software for managing workflow and data gathering. If you look at Adobe’s LiveCycle ES page, it all seems PDF-centric and Data Services is hidden away as the last item under Data capture.

In reality LiveCycle Data Services ES has a lot to offer even if you don’t care a bean about PDF, but that is a fact that is easy to miss. Another positioning issue. Adobe has been over-zealous in its PDF-with-everything strategy.

I also asked Nickull how Acrobat.com fits with with Adobe’s SOA strategy. He said that a move to application hosting would be a logical one, though he implied that it would be geared towards SMEs.

Host your Java application on Adobe’s servers, with built-in LiveCycle Data Services for your Flex client? That makes sense to me.

Technorati Tags: ,,,

Survey ranks developer tools, and reveals what developers care about most

Evans Data has published its 2009 Software Development Platforms survey, to which around 1200 developers contributed, scoring their chosen development tools in eighteen different categories.

The tools covered are Eclipse, Embarcadero’s Delphi, IBM’s Rational Suite, IntelliJ, Microsoft’s Visual Studio, NetBeans, Oracle JDeveloper and Sun Studio.

I was sorry not to see more products covered. Flex Builder Flash Builder, Zend Studio, Aptana and JBuilder would all have been interesting, for example. Each developer only scored the product they actually use (a good thing), so the sample is not as big as it first appears.

I’m also mistrustful of the survey results, particularly when you look at it in detail. For example, one of the categories is “Support for frameworks”.  Visual Studio came top, while Eclipse was last. But hang on: in Visual Studio (for example) are we talking MFC, or .NET Framework? The development experience for each is totally different. And were developers primarily judging on the framework tools, or the framework itself? It is hard to attach much meaning to the scores in this category.

Another flaw: the versions of the products is not specified. That means a weakness may have been fixed in a later version, but the survey does not tell you.

A third flaw: some tools are weak in several categories, dragging down their overall score, but that does not matter to developers who do not use them for that purpose. It is hard to compare like with like.

Still, while I’m wary of the survey overall, I though it brought out some interesting points. One is that developers were asked what features matter most to them. So:

The three things developers care about most (highest priority first):

1. Basic tools (editor/compiler/debugger)

2. Documentation

3. Tool integration

The things developers care about least (lowest priority first):

1. Support for remote development

2. Support for parallel programming (sorry Intel!)

3. App Modeling tools

What about the winners and losers in the survey? I almost forgot. IBM’s Rational Suite came top, followed by Microsoft’s Visual Studio. Eclipse came last, though it still got a decent score, well below its rival NetBeans.

The low ranking for Eclipse (which is nevertheless wildly popular) deserves some comment, particularly as the top tool, IBM Rational Suite, is built on Eclipse. I spoke to Eclipse executive director Mike Milinkovich while researching this Register piece recently. One of the points we discussed was the tension (if there is one, which he disputes) between tools vendors sharing resources to build the best possible platform, and holding resources back to retain commercial differentiation. I’ll write this up in more detail shortly; but it shows why certain areas in Eclipse may not receive the attention they deserve – localization was a specific example.

Another problem with Eclipse is that it is all a bit messy, confusing and hard to manage, particularly in a team where you want every member to have an identical setup. It is still worth it though, for the riches it provides for free.

Adobe “Committed to bringing Flash Player to the iPhone”

Adobe CEO commented during yesterday’s earnings call:

We are also equally committed to bringing the Flash Player to the iPhone, so now we do have a Flash Player 10 version for smartphones. We continue to work with Apple. We need more APIs and cooperation to bring the capabilities of Flash to the iPhone and we think it’s in both of our best interests to make sure that 85% of the top 100 websites that use Flash, that that experience is available to the Apple customers.

The real question is not whether Adobe is committed to this, but whether Apple will allow it. I think the stake are high for Adobe, which is why I have such keen interest. The longer the iPhone remains Flash-free, the more those “85% of the top 100 websites” will question their use of Flash and wonder if they should try to migrate towards more universal HTML and JavaScript technology. On the other hand, if Adobe gets its stuff on iPhone it will give it a further advantage over rival plug-ins like Microsoft’s Silverlight.

I mean, if you build your entire cloud platform around the Flash client, what do you do if the key mobile device out there refuses to support it?

Transcript from Seeking Alpha.

Technorati Tags: ,,,

Opera Unite: another way to share, another nightmare for digital rights

I’ve been trying out Opera Unite. This is a web server built into the Opera 10 browser, now in beta. There’s nothing new about running your own web server; one comes free with Windows, and Apache is free for anyone to download and install in a few clicks. The difference with Unite is first that it’s packaged as a set of simple services, such as a chatroom, a note-sharing “fridge”, and a media sharing application; and second, that Opera handles the techie problems of opening firewall ports and sorting the DNS.

I clicked a few links in this informative Reddit discussion and was soon looking at the fridge on someone’s machine out there.

Shortly afterwards, I was enjoying one of their Beatles tracks:

Cool; never mind that the Beatles do not, as far as I know, allow any of their songs on legal download sites like iTunes or Spotify.

Today the UK government is publishing Digital Britain, which is expected to include new proposals for protecting digital rights. Opera’s new product is a reminder of how hopeless that is.

Security is not Unite’s strong point. Although users can protect their content or other services with a password, it is passed as plain text, which means it is vulnerable to network sniffers. Opera has sandboxed services to protect the user’s machine, though as ever bugs could produce security holes.

Developers can create their own services, of course, and there are some interesting possibilities here. One that users will like is the ability to share files such as photos without needing to upload them first.

I doubt Opera will mind much if the service is controversial. It’s great publicity for its minority-usage browser that is otherwise easy to forget.

Microsoft unbundles Internet Explorer from Windows 7 – in Europe, that is

Microsoft is to offer a special version of Windows in Europe. Called Windows 7 E, it will be identical to Windows 7 elsewhere except for one thing:

The E versions of Windows 7 will include all the features and functionality of Windows 7 in the rest of the world, other than browsing with Internet Explorer.  Computer manufacturers will be able to add any browser they want to their Windows 7 machines, including Internet Explorer, so European consumers who purchase new PCs will be able to access the Internet without any problem.  Consumers will also be able to add any Web browser to their PCs, to supplement or replace the browsers preinstalled by their computer manufacturer.

There’s only one reason for this. It’s an effort to comply with EU competition law:

We believe that this new approach, while not our first choice, is the best path forward given the ongoing legal case in Europe.  It will address the “bundling” claim while providing European consumers with access to the full range of Windows 7 benefits that will be available in the rest of the world.

The post linked above is from Microsoft’s VP and Deputy General Counsel Dave Heiner, who notes that Microsoft is keen to avoid a delay in shipping Windows 7 in Europe. In other words, it would rather give up whatever advantage it gets from shipping with IE included, than risk some sort of sales injunction and/or fine which would be hugely costly. It has more pressing problems than its share of the browser market, including competition from Apple and Vista’s poor reputation.

It may be fined anyway, of course, for past misdemeanours in the EU’s eyes.

Personally I have mixed feelings about the EU’s legal efforts in relation to Microsoft. Last time around we got the absurd Windows N, to address a Windows Media monopoly that hardly existed – Apple and Adobe are winning in media, and that’s nothing to do with Windows N, which nobody bought. That said, the EU may have made life better for the Samba folk by forcing the publication of Windows protocols, which is an interoperability benefit. It’s unfortunate that fines go, apparently, straight into EU coffers; the anonymous Mini Microsoft blogger says:

EU: you say "ee-you", I say, "ewwww!" As long as the Microsoft ATM continues shooting out cash fines the EU is going to keep mashing our buttons.

and I see his point.

What are the implications this time around? It’s worth bearing in mind that OEM vendors can already make other browsers the default in Windows. Still, on the face of it this is good for competing browser vendors, though they may find themselves having to pay for prime position in OEM installs. It could be annoying though for users installing or re-installing Windows from shrink-wrap editions, who find they have no browser; presumably Microsoft will include some sort of download utility other than a web browser to get them started.

More interesting questions: how much will this affect the market share for IE, which is already declining, and how much does that matter? Believe it or not, there are reasons to use IE, particularly in a business context where its integration with group policy and the fact that security updates flow through Microsoft update mechanisms are an advantage. Most web sites work well with IE, because they still have to. I expect IE to remain popular in Windows 7; and I expect change to be driven more by a move to web applications which require fast JavaScript or other such features found in rival browsers, rather than by OEM defaults.

There is a war being fought for the next generation of the client, and whether it runs on Flash (Adobe), on Silverlight (Microsoft), on Java (Sun/Oracle), on HTML 5 (Google), on native Windows (Microsoft again), or on OS X (Apple). Unbundling IE from Windows 7 removes a small advantage from Microsoft, but I doubt it will be decisive.

Incidentally, I expect this unbundling to be mostly cosmetic. The IE executable, iexplore.exe, is a wrapper round other components in Windows that pretty much have to remain, otherwise lots of applications which rely on them would break. The presence of these components does no harm to other browser vendors though, so gives them no reason to complain.

Local SQL support in Safari vs Google Gears: what is happening?

Today I installed Safari 4.0, and one of the features which caught my eye is its local database support. No, it’s not new, but perhaps has not received the attention it deserves. The feature lets you use a local SQLite database from JavaScript, both online and offline, and works on the iPhone 2.0 and higher (2.1 for offline support) and in Safari 3.1 and higher. The API is rather simple. windows.openDatabase returns a database object, and you then work with methods like transaction.executeSql, reading the results in a callback function. Security restrictions mean that access to the database is restricted to pages served by the domain from which it was created. Apple has more information in its Safari Client-Side Storage and Offline Applications Programming Guide. Safari’s local database features implement the HTML 5 W3C Web Storage API.

It’s a great feature, and strengthens Safari on the iPhone as an application runtime that avoids the hassles of the App Store. Does it have wider value? A problem is inconsistent support across other browses. Microsoft’s IE8 supports DOM Storage (key-value pairs), which is also part of the HTML 5 standard, but not SQL. FireFox also supports DOM Storage, but its SQLite support is restricted to components and extensions only.

A possible reason for the lack of wider SQL support is that Google has its own implementation in Gears, which works in Safari and FireFox on the Mac, in IE and Firefox on Windows, and in Firefox on Linux. One place you cannot install Gears though is on the iPhone. A possible solution is to create a wrapper API that uses HTML 5 on Safari and Gears elsewhere; Malte Ubl has done some work on this, for example.

Personally I’d like to see the HTML 5.0 specification more widely supported, since along with the iPhone issue, not everyone wants to install Gears. I would have thought it could be added to both Chrome and FireFox relatively easily; but would be interested to know what is planned.

Technorati Tags: ,,,,

BBC seeks web response from unconnected users

This really needs a cartoonist. I thought I should grab it before it gets changed.

“The BBC was surprised by the lack of response to its latest Internet survey”

The serious point: now you have another reason not to trust web surveys.

Update: The BBC’s form is not completely daft: it says “at home” and you might be on the Internet at work or in a café. Still, that’s going to be unrepresentative of the 30% – it is exactly the sub-set which is already proven to be Internet users, whereas we most want to hear from those who are not and need to be “persuaded to go online”. Thanks to @rupertg and @putsimply on Twitter for the correction.

Technorati Tags: ,,

Will Microsoft respond to the JavaScript speed challenge?

While people argue about JavaScript performance in Chrome vs Safari vs FireFox, there’s one fact that is beyond dispute. Microsoft’s Internet Explorer 8 is hilariously slow in comparison. On Apple’s figures, IE8 is 5.9 times slower on its i-Bench JavaScript test and 7.7 times slower on the SunSpider test.

You may hardly notice this in normal browsing. It most likely takes longer to download the JavaScript than to execute it. In fact, download speed is still the most significant factor in browser performance, and changing your browser will do nothing to change that (though different approaches to caching might).

This could change though, if more web applications appear that make heavy use of JavaScript. Google Wave could be an example. In fact, this seems to be Google’s game plan: make the browser (backed of course by the Internet) the operating system. The larger these web applications become, the more difference that JavaScript performance will make.

Offline is another interesting case, enabled in Chrome by the Gears add-on. In this scenario, content is served locally so browser performance has a better chance to shine.

The big question: will Microsoft step up to the challenge and fix JavaScript performance in IE? The company could do so relatively easily, either by using one of the open-source engines (unlikely) or by applying its existing knowledge of just-in-time compilation, used to good effect in .NET and Silverlight, to JavaScript in the browser.

The horns of Microsoft’s dilemma: improve JavaScript and undermine the advantage of Silverlight, which runs code much faster. Don’t improve it, and see market share continue to decline in favour of faster browsers.

The right thing to do, of course, is to fix the JavaScript engine; but companies do not always do the right thing – and Microsoft may still be comforted by its 65% market share for IE. That’s false comfort; the share is in long-term decline.

Incidentally, I’ve noticed that Google, while not exactly taking the gloves off, is stepping up its promotion of Chrome. When I go to youtube, which is the 3rd most popular web site in the world according to Alexa, I now see this on every page, if not using Chrome:

I don’t always see an ad on the Google home page itself – Alexa’s number one site – though occasionally I do see this on the right:

All very low-key; but I reckon we’ll see Google step-up its campaign as Chrome itself gets better and the Mac version appears. With Apple, Google, Mozilla and of course Opera all gunning for Microsoft, it would take extraordinary complacency not to respond.