It is very valuable but compaction enables a number of use cases where events are generated in significant quantity or you need to save space, like if you’re implementing event sourcing at thw GUI layer (the event store is basically a journal).

▲

addaon 3 hours ago | parent [-]

But the event store is also your undo stack, then. Keeping it infinite (or deliberately trimming it at application launch) improves user experience.

	▲	throwup238 2 hours ago \| parent [-]
		You can selectively compact the journal to only compact the numerous GUI events leaving domain events uncompacted (I do this for a CAD app I develop)