Difference between SharePoint Workflow and K2 Workflow

From Development and Business Prospective:

	SharePoint Custom Workflow	K2 Blackperal Workflow
1	There are no in-build components by which it will be easy to integrate with SharePoint, Office 2007, and other backend systems.	K2 is built on top of WWF and they have a lot of nice components that make it easy to integrate with SharePoint, Office 2007, and other backend systems.
2	No Real time monitoring for each task.	You can find ‘Flow Diagram’ for the current status in graphical mode. You can also do real time monitoring of each task.
3	We need to write custom code for Error handling.	K2 introduces a ‘BlackPearl Workspace’ site which  manages all for Error handing of each instance, managing workflow permission and tracking workflow process etc.
4	No web parts available for managing Tasks.	K2 Work list web part is available for managing Tasks.
5	No Context Browser available while development.	Here you will get content browser for all. E.g. SharePoint Environment browser, Mail Server Browser, Workflow Server Browser, Workflow process browser and  Function browser etc.
6	No SharePoint Event available while development.	All SharePoint Events available. E.g. : ·         Manage Site and Workspace ·         Manage List/Library ·         Manager Site/List/List Item permission ·         SharePoint Search ·         SharePoint Record Management etc.
7	You can find only ‘Activity’ and you have to write code for each case.	Here you will find Activity with lots of event templates. Just drag them and use them.
8	Settings properties for each activity is not user friendly.	Here everything through wizard process (step-by-step) with nice GUI.
9	InfoPath integration with Workflow will require so many steps.	Here it’s cool to use and easy to interact with InfoPath data fields.
10	Custom Web Forms integrate with WF is very difficult.	Here it’s cool to use through wizard interface.
11	Development is difficult(Less feature, More code).	Development is easy and user friendly(More feature, less code).
12	Deployment is not user friendly	Deployment is easy.