From bd9b61bba3b2f985daabeb1f9af87e64c7f83608 Mon Sep 17 00:00:00 2001
From: "CodeSmile-PC\\CodeSmile"
 <42713966+CodeSmile-0000011110110111@users.noreply.github.com>
Date: Fri, 26 Jan 2024 09:49:14 +0100
Subject: [PATCH] small readme change

---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index 0551fdc7..6ff696d9 100644
--- a/README.md
+++ b/README.md
@@ -10,6 +10,8 @@ The AssetDatabase is [heavily fragmented into verbosely named, losely related st
 
 Developers commonly employ a trial-and-error approach. Trivial tasks take much longer than estimated. Edge-cases remain to be discovered later. There is a real risk of data loss due to a simple mistake. Cargo-cult and copy-pasta programming needlessly degrade editor performance.
 
+That's what most editor tools are based on, unfortunately.
+
 You'll find such bad examples even in popular Asset Store tools used by big game studios! 
 
 A clean start with a consistent API is the best way to solve these issues, speed up development of editor tools, ensure scripts will not fail for users or other editor platforms.