[doc] Update README

Author: ptaoussanis

README.md

@@ -10,7 +10,11 @@
 
 ### Modern logging facade for Clojure/Script
 
-Trove is a minimal, modern alternative to [tools.logging](https://github.com/clojure/tools.logging) that supports:
+Trove is a minimal, modern alternative to [tools.logging](https://github.com/clojure/tools.logging).
+
+It's intended for **library authors** that want to emit rich logging _without_ forcing their users to adopt any particular backend.
+
+It supports:
 
 - Both traditional **and structured** logging
 - Both Clojure **and ClojureScript**
@@ -20,7 +24,7 @@ It's TINY (1 macro, 0 deps, ~100 loc), fast, and highly flexible.
 
 It supports any backend including: [Telemere](https://www.taoensso.com/telemere), [Timbre](https://www.taoensso.com/timbre), [μ/log](https://github.com/BrunoBonacci/mulog), [tools.logging](https://github.com/clojure/tools.logging), [SLF4J](https://www.slf4j.org/), etc.
 
-It works great for **library authors** that want to emit rich logging _without_ forcing their users to adopt any particular backend.
+Trove and Telemere offer an identical API and were designed in concert.
 
 ## To log
 
@@ -74,6 +78,17 @@ That's why Trove automatically delays any values that need runtime evaluation, a
 
 This explains the `:lazy_` `{:keys [msg data error kvs]}` arg given to [`truss/*log-fn*`](https://cljdoc.org/d/com.taoensso/trove/CURRENT/api/taoensso.trove#*log-fn*).
 
+## Why structured logging?
+
+The key difference between traditional and structured logging?
+
+- Traditional logging outputs **strings** (messages).
+- Structured logging in contrast outputs **data**. It retains **rich data types and (nested) structures** throughout the logging pipeline from logging callsite → filters → middleware → handlers.
+
+A data-oriented pipeline can make a huge difference - supporting **easier analytics**, **transformation**, **filtering**, etc. It’s also usually **faster**, since you only pay for serialization if/when you need it. In a lot of cases you can avoid serialization altogether if your final target (DB, etc.) supports the relevant types.
+
+The structured (data-oriented) approach is inherently more flexible, faster, and well suited to the tools and idioms offered by Clojure and ClojureScript.
+
 ## Funding
 
 You can [help support][sponsor] continued work on this project and [others][my work], thank you!! 🙏