Can Event Sourcing be avoided?

After producing my first app with Event Sourcing it was obvious that everything needs much more thinking than plain CRUD apps. This is actually great as a learning experience, but tedious to support and convince others to join.

Being honest I do like Event Sourcing but I do want to keep my apps as simple as possible. Specially if can get away with shameful lazy architecture as far as my coding crimes are restrained-hidden in an independent service.

I am reading as much as I can about the downsides of Event Sourcing to make sure I use wisely this powerful tool. The funny thing is that although I grasp the involved complexity and some some other downsides, I normally wish these two requirements:

1. Support "undo"


2. Sync changes with offline clients

There are plenty of frameworks where I could get immediately both features, but Event Sourcing looks more like the only reasonable way to implement both features in a framework independent way. Therefore I am finding very hard to avoid using Event Sourcing, because it can ease my way into both with plain independent architecture.

Is there any easier strategy to attain such features without marrying myself to a single tool/library/framework?