I would have to disagree with your statement. As a developer who uses Roblox-TS, it isn’t a framework at all. It’s a compiler that converts Typescript into Roblox Luau. Which, of course, does not stop you from using Knit within Roblox-TS.
The benefits of using Knit are apparent once you use it. It follows the idea that the main scripts controlling your code are singletons (Controllers and Services). Those who have previously used AeroGameFramework (or Flamework for Typescript users) should be somewhat familiar with this concept. However, the client has access to certain functions and data the developer intentionally exposes within a service, which allows the client to call server functions far more intuitively. Knit follows Roblox’s style of Singletons, and you can retrieve services and controllers using:
// Service:
Knit:GetService("ServiceName")
// Controller:
Knit:GetController("ControllerName")
There are also in-built packages that would be very useful for developing (such as Janitor, signals, table utility, and more). It’s also much easier to read as it splits your game into very readable singletons. I’d recommend any Roblox developer that codes in Lua to use Knit.
However, as a Roblox-TS user, I prefer Flamework (another framework) over Knit as it is designed explicitly for TS and follows TS guidelines better.