As many of you know, Knit has stopped receiving updates. It’s an awesome library.
I wanted to ask if Knit is still reliable, or if there are any forks or alternatives currently being developed?
2 Likes
I didn’t get any answers, so I’ll talk on my own.
This post was from 2 days ago, and I had to choose between creating module scripts myself or using Knit.
I preferred to use my own module scripts because the IntelliSense situation is pretty bad. Also, I saw many comments mentioning that it’s outdated.
I would still like to hear other opinions, though.
I’m facing the same dilemma, but it looks like the creator wrote an article addressing this topic: Knit, its history, and how to build it better. | by Stephen | Medium
1 Like
Yes, instead of Knit, require ModuleScripts. There’s really not much more that needs to be said.
If you still believe in frameworks, I’m only aware of one worth using right now: Prvd 'M Wrong (type-safe API, so you’ll get Intellisense). However, it’s not production-ready, and I would prefer to just use my own ModuleScripts, anyways.
1 Like
Yes, instead of Knit, require ModuleScripts. There’s really not much more that needs to be said.
Seems like this is what everyone is saying about this matter recently, but quite frankly this is an unhelpful non answer.
Knit provided not only a framework with useful tools like a end to end networking library, but also served as a standard paradigm for inexperiened devs to follow. Albiet the usage of singletons it imposed was not the most optimal solution to every devs’ needs, it was still a useful crutch.
“Just use module scripts” provides none of that. It lacks the clear structure Knit provided and is the main reason why people are still writing posts like this to this day, despite its creator deprecating the framework and chanting the same unsympathetic line. It’s like taking fire away from a neanderthal because it’s “dangerous” and giving him electricity with no means of harnessing it.
1 Like