Lightroom :: 4.0 File Handling / Step Backward Or Forward?

I am not a big fan of the entire way that Lightroom 4.0 hands changes at all and Adobe needs to address this problem because it is just that, an problem. We can use the catchy verbiage "non destructive" because it sounds nice but the fact is that it is cumbersome from a resource perspective and UI perspective.  It adds extra steps to the workflow and this in turn takes away from the experience of users.  The entire workflow should be reexamined and the code, rewritten.
 
Lets just look at how Picasa handles this issue.  When I click "Save" or better yet "Save All", every picture that I have edited is saved with the changes that I have made to them.  A new folder is then created and named "Originals" where I can find the original files that I have edited. That’s it. Plain and simple.  My files are intact and I can now go and find them in my well-thought-out folder hierarchy where I can then do what ever I want from emailing to a client to sending them to Flicker, Facebook, Google+ Galleries, where ever I choose.  There is no thought put into this process.
 
Adobe has a lot to learn from this free app. Currently, in Lightroom 4, I have to go back through the 300 pictures I just took, find the 40 that I have edited, then "Ctrl+Click" to select only them, find my folder in my file directory, create a new folder, and finally export a new set of pictures with the changes that I wanted to send out to my client 10 minutes ago. 
 
Both processes achieve the same thing and the things that we all want which are our original files are still intact and untouched and our new files with the changes are in the folder where we found them.  The difference is that Adobe chose a much less elegant way to go about this.  More advanced? Yes, but sometimes, as and coder will tell you, simpler is faster, safer, and better.
 
Now, I also stated that from a resource perspective this is also poorly conceived.  I am referring to the fact that now I have to maintain a database in which changes are tracked that is always running in the background.  It is common knowledge that databases are susceptible to corruption when not properly managed and even the simplest snag in the application, power surge while an I/O process is running, or if my computer hangs up, all my changes are gone.  What if I want to switch computers?  Do I also need to manually go in several times a month and backup my database to a separate directory?
 
Will I lose all of my changes that I did not publish?  Maybe, maybe not but it is now something else I have to worry about which ultimately takes away from my experience in the application.
 
Simpler is better and this is one step backwards, not forwards.At a minimum, give me the option to save the changes and don’t manage your users like a child.