SharePoint 2010 vs 2007

Microsoft Office SharePoint Server 2007	SharePoint Server 2010
Office client required to view and edit documents uploaded to document libraries (Download and open)	Office Web Application enables Word, PowerPoint, Excel and Visio documents, using Silverlight or HTML with JavaScript (Depending on Browser Support)
No Co-Authoring Capability	Co-Authoring Capabilities available for Word, PowerPoint (with client software) and Excel (Available over the web)
Lot of post backs	Fewer post backs for default actions – more Ajax usage
No inherent support of Ajax or Silverlight	Fully supported
Static themes. You just pick a theme and its applied across the site, no preview	You can select a theme , customize it and preview before applying it on the site
No bookmarking, tagging or rating capability	Its all there
Content Types scoped to site collections	New concept of having a Content Type hub which can be shared across web applications
Media files would have to be downloaded before playing	Progress download feature available (not streaming)
BDC used to store info in SharePoint	BCS reads data real-time (with some caching for performance)
5 million item limit in document library	10 million
Views are CAML driven	Views XSLT based
To query a list we had to use CAML	Queries via LINQ, JavaScript and Silverlight API's
No restriction for installation	Ability to prevent people from installing SharePoint (Managed at the AD level)
Shared Services scoped to Farm	Shared Services architecture changed to make it more flexible and ability to share across farm
Profile synch could be done by anyone	Additional permission check for account to carry out profile synch
Basic web Analytics	Web analytics capability enhanced
Search results are static	Clicking on a search result affects the search results for the other searches for the same keyword
To limit issues with rogue code that could bring down the server, CAS had to be defined /maintained for different applications. This was not easy to do and Admins used to say – no code allowed	Sandbox available that restricts the scope of code. Deployment is also easy, the code just needs to be uploaded by the site admin, no need for intervention from the SharePoint farm admin to run scripts on the server
People with contribute access could upload .aspx pages in a document library. It was possible to restrict, however it would restrict everyone from uploading .aspx pages	People with contribute access cannot load .aspx pages
Contributors could edit tool pane parameters	Not editable by contributors
Explorer view on browser	Opens up Windows explorer with web dav access
Simplistic Mobile Page OOTB	Able to create richer mobile pages using OOTB features
Usage of outlook for offline access	SharePoint Workspace used for offline access – more capability eg. ability to synch up lists (even external content from BCS)
Not possible to have a common document ID that is associated with a document regardless of which document library it moves into	Document ID can be defined and associated to the document regardless of where it is located(within the site collection)
To upload a document or page, one needs to go to that appropriate site/subsite and library and upload	Content organizer moves document to appropriate libraries based on metadata rules which can be defined
When a file with a same name is uploaded, it creates a new version	Option to have another version or append a unique ID to the document being uploaded
Fixed layout with defined web part zones where web parts can be placed	More "Fluid" UI; ability to place web parts without having web part zones
Retention policy allows only delete or invoke workflow by default	Multiple other options – eg send to another library etc
EBS – to store docs out side SharePoint, possible but not easy to configure	RBS -  managed by SQL
Requires Server OS to install(32 or 64)	Can be installed on Win 7 (64 bit) and Win 2008 (64 bit)
No field validations	Field validations available
Workflows created in SPD or VS.Net – not possible to move a workflow developed in SPD to VS.Net	Workflows can be defined in Visio, Imported to SPD with rules added and then moved to VS.Net
Table based layouts	Div Based layouts (better for accessability)