Spot the web RSS 2.0
# Wednesday, December 19, 2007

The good folks at Ajaxian.com and I just completed our third annual survey of Ajax tools usage.  The raw data is free for everyone here - you should be able to slice it and dice it anyway you see fit.  The top 10 Ajax toolkits in 2007 are:

Dec2007top10_2

You can check out the top 10 Ajax toolkits from 2006 and 2005 at the end of this blog.

What is interesting about the Ajax market is that it's more diversified in 2007 than it was in 2005 - the number  of toolkits keep growing and jostling position in terms of usage.  Right now there are 241 Ajax toolkits and related libraries listed in the survey. There were about three dozen in 2005 and 170 in 2006.  The number of options is growing.

That's brings up another point: The survey is not limited to Ajax frameworks and toolkits, it also includes some JavaScript libraries commonly used in Ajax development. All of the entries were derived from Ajaxpatterns.org as well as past surveys. There are probably quite a few of these frameworks that have been abandoned and others that were missed, so its not a perfect record of available Ajax toolkits and libraries today.

Prototype and Script.aculo.us are the only toolkits to maintain a lead over the past three years.  However, over all there are no clear winners or losers as even the strongest incumbents (i.e., Prototype and Script.aculo.us) are starting too loose ground. Some frameworks initially popular have faded nearly completely out of the market (i.e., xajax and Rico ) while others have have sprung out of nowhere to become leading tookits (i.e., jQuery and Ext JS).    The changes over the past three years are easy to see in the stack chart at the end of this blog, which shows the market share of the most popular toolkits - notice how they grow and shrink in market share. That means that the market remains immature.

What is astonishing is the nearly complete lack of commercial Ajax frameworks. Backbase has had a lot of success making a comeback after loosing some market share in 2006, but other commercial Ajax frameworks have not been so lucky. 

Spry is growing quickly and may be in the top 10 next year. Spry was left out of the survey for the first day or so and then added in as it was the most popular write in toolkit.  It may have faired better if it was an option from the start. I added up all the write-ins for Spry with picks after the survey was adjusted. The numbers are not great - Spry has about 4% of the market right now

The number of responses were much higher this year (2,619) compared to 2006 (865) and 2005 (763).   The increase is enough to say that Ajaxian.com has become more popular and so has Ajax but you can't go much beyond that. In addition, the entire survey has to be taken with a large licking-block of salt. It's not scientific and probably breaks about 100 rules for best practices when doing a survey.  However, given the limitations of the survey and the surveyor (that's me), it still provides valuable insight to the Ajax toolkit market in general.

Wednesday, December 19, 2007 10:52:22 AM (Jerusalem Standard Time, UTC+02:00)  #    Comments [0] - Trackback
Programming

Which .NET Framework Data Provider to Use?

To achieve the best performance for your application, use the .NET Framework data provider that is most appropriate for your data source. There are a number of data provider options for use in your applications. The following table provides information about the available data providers and which data sources a data provider is most appropriate for.

Provider

Details

SQL Server .NET Data Provider

Found in the System.Data.SqlClient namespace.

Recommended for middle-tier applications using Microsoft SQL Server version 7.0 or later.

Recommended for single-tier applications using the Microsoft Data Engine (MSDE) or Microsoft SQL Server 7.0 or later.

OLE DB .NET Data Provider

Found in the System.Data.OleDb namespace.

Recommended for middle-tier applications using Microsoft SQL Server 6.5 or earlier, or any OLE DB provider that supports the OLE DB interfaces listed in OLE DB Interfaces Used by the OLE DB .NET Data Provider in the .NET Framework SDK.

For Microsoft SQL Server 7.0 or later, the .NET Framework Data Provider for SQL Server is recommended.

Recommended for single-tier applications using a Microsoft® Access database. Use of an Access database for a middle-tier application is not recommended.

ODBC .NET Data Provider

Found in the Microsoft.Data.Odbc namespace.

The ODBC .NET Data Provider is available for download.

Provides access to data sources that are connected to using an ODBC driver.

Oracle .NET Data Provider

Found in the System.Data.OracleClient namespace.

The .NET Framework Data Provider for Oracle, unlike the Microsoft OLE DB provider for Oracle, also supports new Oracle 9i datatypes, as well as ref cursors (useful for running Oracle stored procedures that return result sets). This provider, System.Data.OracleClient, is similar to the .NET Framework Data Provider for SQL Server, System.Data.SqlClient.

The Oracle .NET Data Provider is available for download


The fastest database read mechanism will be ADO.NET Data Readers, as opposed to Data Sets.

Wednesday, December 19, 2007 9:40:12 AM (Jerusalem Standard Time, UTC+02:00)  #    Comments [0] - Trackback
.Net | Programming | Visual Studio
# Tuesday, December 18, 2007

Web design is simpler than ever, and that's a good thing. web 2.0 design means focused, clean and simple design that is all about the content.

Why simplicity is good?

  1. Web sites have goals and all web pages have purposes.
  2. Users' attention is a finite resource.
  3. It's the designer's job to help users to find what they want (or to notice what the site wants them to notice)
  4. Stuff on the screen attracts the eye. The more stuff there is, the more different things there are to notice, and the less likely a user is to notice the important stuff.
  5. So we need to enable certain communication, and we also need to minimise noise. That means we need to find a solution that's does its stuff with as little as possible. That's economy, or simplicity.

How?

There are two important aspects to achieving success with simplicity:

  1. Remove unnecessary components, without sacrificing effectiveness.
  2. Try out alternative solutions that achieve the same result more simply.

Whenever you're designing, take it as a discipline consciously to remove all unnecessary visual elements.

Concentrate particularly on areas of the layout that are less relevant to the purpose of a page, because visual activity in these areas will distract attention from the key content and navigation.

Use visual detail - whether lines, words, shapes, colour - to communicate the relevant information, not just to decorate.

Tuesday, December 18, 2007 10:38:00 AM (Jerusalem Standard Time, UTC+02:00)  #    Comments [0] - Trackback
CSS | Programming | Web 2.0 | Design
Navigation
Archive
<December 2007>
SunMonTueWedThuFriSat
2526272829301
2345678
9101112131415
16171819202122
23242526272829
303112345
About the author/Disclaimer

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2010
Guy Levin
Sign In
Statistics
Total Posts: 63
This Year: 0
This Month: 0
This Week: 0
Comments: 14
Themes
All Content © 2010, Guy Levin