Who made the bright decision not to include the design view in SPD 2013?

That just wipes out most of the Power Users out there. 

Does someone have another option?

I can't believe that Microsoft would neglect so many SPD users who do not have a programming background.

Here is a justification from MS to remove Design view

http://blog.sharepoint-videos.com/sharepoint-designer-2013-data-view-web-part-list-view-web-part-design-view-is-gone/

If you are a Power User who loves working with and creating no-code solutions on SharePoint, you are the one most affected by this change. There is no replacement for the functionality lost in any other product that I know of so far. SharePoint Designer was it and now there is none! In SharePoint 2013, there will be no other built in functionality that will let you manage these no-code solutions visually. If you know of something I dont, I would love for you to comment about it below.

I have been using SPD Designer 2007 for designing my team's SP site and l loved it as I can customize the look a lot. Now my company upgrades the SP site to 2013 and I'm excited to learn the SPD 2013 but to find out the Design view is gone!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I don't have any programming background, so Code view doesn't work for me at all. I am screwed now as I won't be able to keep or recreate the customerized look for my team's SP site. :(((((( What can I do??????

I totally agree with Mel that I CANNOT believe MS would take out the design view. That's the main reason for people don't know how to write code to use SPD!!!!!!!!!!!!!!

I am totally blown by this also!  Not to mention that it seems like all aspects of Designer seems to be 'dumbed down' a lot, and whoever figured that it was a good idea to remove the design and split view: should be fired!!!  

I mean: I am a programmer and given the messy code Designer generates in the first place: using the design view in conjunction with Split view was the only way to efficiently find elements in any given page....

Removing Design View is one of the most retarded thing MSFT has done. Why?

I completely agree. I edit a SharePoint Wiki, and the loss of Design View is going to slow down my process by at least 20%, = 450 hours per year x my billing rate...

Agree!