3 ms·

We used this mess of a library, which provides no clear interface and corrupts data https://github.com/johnbywater/eventsourcing https://github.com/johnbywater

We used this mess of a library, which provides no clear interface and corrupts data https://github.com/johnbywater/eventsourcing https://github.com/johnbywater/eventsourcing

jasonm23 10y ago
I'll go out on a limb here and say it wasn't Event Sourcing that caused the problems. Anything can be ^H^H^H^Hmessed up.
maxaf 10y ago
A faulty implementation doesn't necessarily invalidate the idea. I also strongly suggest looking into statically typed languages. Python is very poorly suited to working with data.
- strictfp 10y ago
  Yes, but even so it's a huge undertaking to build your own event sourcing. Many get burnt.
- deleted 10y ago
  [deleted]
- kbutler 10y ago
  > Python is very poorly suited to working with data. This does not seem to be true, based on widespread industry and scientific use of Python generating, managing, and analyzing data. Perhaps you meant in some specific way, like "Python does not enforce objects' data schema" or some such?