re:
why give an opinion if you don't know the end?
I'd guess Demetri did it because the idea that they are the same product is incorrect.
I was about to post the same corrections, but Demetri beat me to it.
Btw, you're also right in that, for web developers who work stand-alone,
there's no need for source control but there might be a need for remote database design.
*everybody* can use that.

(Even stand-alone developers, who might need to work with a remotely hosted SQL Server.)
There's other, subtler differences, like full option menus being available in Pro, but not in VWD,
just like the Class Designer and Object Test Benches aren't available in VWD, either.
VWD's XML editor has no support for XSLT, either.
Plus, Pro can run macros, and write and consume Add-ins and Install Packages,
and can also use Crystal Reports, which isn't available in VWD, which only has
SQL Server Reporting Services available.
Also, VWD doesn't support remote debugging, whil Pro does,
and there's no 64-bit compilker support in VWD.
There's a complete list of differences in the link Demetri sent:
http://msdn.microsoft.com/vstudio/products/compare/default.aspx
Let's try to keep our posts limited to technical issues, OK ?
Juan T. Llibre, asp.net MVP
aspnetfaq.com :
http://www.aspnetfaq.com/
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en español :
http://asp.net.do/foros/
===================================