Skip to content

Commit 4e9ea0f

Browse files
Update README.md
amended typos all over
1 parent f972253 commit 4e9ea0f

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -16,13 +16,13 @@ If you are using **v4**, please keep doing that!
1616

1717
If you're happy to try **v5** please file issues in here, don't expect me to react out of tweets, and thank you for helping me out with use cases I couldn't even think about.
1818

19-
**v5** is a rewrite from scratch based on another library (which is *Python based*) that works perfectly fine **but** it doesn't have a reactivity storey fully attached yet.
19+
**v5** is a rewrite from scratch based on another library (which is *Python based*) that works perfectly fine **but** it doesn't have a reactivity story fully attached yet.
2020

21-
This reqrite feels good, it avoids unnecessary loops, but it's also naively based on *signals* for everything that ways easier to control before ... *a whole render* each time, never atomic, never considering edge cases around conditional arrays and what not.
21+
This rewrite feels good, it avoids unnecessary loops, but it's also naively based on *signals* for everything that was way easier to control before ... *a whole render* each time, never atomic, never considering edge cases around conditional arrays and what not.
2222

23-
I understand now that signals are in everyone is going to use signals for everything, as a distributed shared state of everything you are doing, but as a person that alaywas provided libraries to keep it simple, I couldn't even think about some of the scenarios you are "*abusing*" signals for, so my deepest apologies if the current state of **v5** cannot meet your expectations, I've tried my best, and rushed a little bit, with this release, but all the ideas behind is where I want to go from now on.
23+
I understand, now that signals are in, everyone is going to use signals for everything, as a distributed shared state of everything you are doing, but as a person that alaywas provided libraries to keep it simple, I couldn't even think about some of the scenarios you are "*abusing*" (no offence, my shortsighting) signals for, so my deepest apologies if the current state of **v5** cannot meet your expectations, I've tried my best, and unfortunately rushed a little bit, with this release, but all the ideas behind represent where I want to go from now on.
2424

25-
Again, apologies for not delivering like I've done before, be assured all the dots will be soon connected in a better way, or at least one that works reliably 👋
25+
Again, apologies for not delivering like I've done before but be assured all the dots will be soon connected in a better way, or at least one that works reliably 👋
2626

2727
- - -
2828

0 commit comments

Comments
 (0)