summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author zaaarf <zaaarf@proton.me>2023-08-22 11:17:01 +0200
committer zaaarf <zaaarf@proton.me>2023-08-22 11:17:01 +0200
commit5020013b23b388e91bac03a931df8c1f17d58223 (patch)
treebf41ee0b52bc850c6222089c9bf26052f6343551
parentc5ef196aac41b6b9198c22432a07e38a3ae365ea (diff)
chore: readme update
-rw-r--r--README.md9
1 files changed, 3 insertions, 6 deletions
diff --git a/README.md b/README.md
index 267ed9c..17a9b2c 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,5 @@
-# Geb!
-GEB (short for _Generative Event Bus_) is an event bus leveraging annotation processing to achieve maximum possible speed.
+# Geb! Processor
+This is the processor behind [GEB](https://github.com/zaaarf/geb)'s magic.
## The trick
There is no trick, it's just basic metaprogramming.
@@ -8,7 +8,4 @@ Suppose that you have a simple event system, with annotated listeners receiving
That works, of course, but it's not that fast. Ah, if only you knew in advance, such as at compile time, who's going to get called with what... oh, wait, you do.
-GEB is just a basic event bus in itself; the actual magician is the processor, who writes into each event direct calls to all subscribers, to take as little time as possible.
-
-## What's with the name?
-"GEB Bus" kind of sounds like "Jeb Bush" and I think it's very funny. Please clap. \ No newline at end of file
+The processor then writes at compile time direct calls to all subscribers into the events, to take as little time as possible.