[quote=]
Why should you use Knit?
- It simplifies Client-Server communication. In knit you will never be interacting directly with remote events. Client functions can be created in services and remote events will be created in the background.
- Unlike Aero Game Framework Knit allows developers to write their bootstrapping code to start and configure Knit, which gives developers the freedom to extend how Knit functions.
- A lot of developers don’t know how to structure their game and a lot of the time I’ve seen developers make an entire game using one script for performance benefits(Viable but not worth it). Knit structures your code using the Service(Script) Controller(LocalScript) Paradigm which scale’s quite well.
- It modularizes your code. Knit Services and Controllers are tables by default meaning you can inject properties that will be assessable from almost anywhere.
[/quote]