Why THNK over something else?

Here are a few reasons why I think THNK isn't just "reinventing the wheel"

## It isn't reinventing anything

THNK cannot really be reinventing the wheel since it is a framework unique in it's space: GDevelop. There are no real multiplayer frameworks for GDevelop. Sure, you could technically use a JavaScript framework like Colysseus, but that is a totally different tool that is way less integrated with GDevelop, and that most users will either not be able to use or use it to a limited degree through a wrapper maintained by a third party. Even if there is trust, a community, and years of time for the code to be polished and improved in the JS framework, will that be the case with the third party wrapper? A JS multiplayer framework is simply not adapted to GDevelop, and trying to force it into GDevelop will just make you lose 99% of the benefits of using a well known framework. Since there is currently no other kinds of frameworks usuable with GDevelop out there, I would argue THNK is exploring an unexplored niche of multiplayer frameworks.

## THNK is innovating

THNK is not trying to replicate what other frameworks do. While some common concepts are applied in it too, THNK has some features that can only be achieved with it's unique position as a GDevelop framework. For example, a feature of THNK is Singleplayer mode: when you switch to a scene built with THNK, it will work in singleplayer by itself automatically.

It then only takes an action to start a server and another to connect a client to that server and play together, allowing to make a game that supports both multiplayer and singleplayer without having to create duplicate scenes with and without multiplayer or something.

As a sidenote, a framework like Colysseus simply can't do that because it is just a JavaScript Client-Server communication framework for games, it doesn't know anything about how you run your rooms on the client, or if/how you want to add a singleplayer mode to your multiplayer game.

## There is nothing wrong with reinventing the wheel

The way you worded your tweet, it seems that you are connoting reinventing the wheel badly. IMHO, that's a shame you think so! Despite the fact that I argued here against THNK reinventing the wheel, I think that many reinventing the wheel is a very good thing, it's what leads to innovation.

Sure, if you are working on a project with a deadline, you won't want to reuse a maximum of building blocks. When every minute counts you cannot afford to waste time recreating something, when someone already made something similar that's close enough. Re recreating the wheel in that context may not be the best idea.

That doesn't mean that, outside of that context, reinventing or taking a new take on an already existing concept is bad! Would you say that all the modern JS Frameworks should not have been used by anyone since they are reinventing the wheel, as we already had jQuery as an established JS Framework? Would you say that nobody should ever have used anything else than MySQL because all other databases are just reinventing the wheel, as MySQL stores data just fine and it's popular?

Everyone creating new alternatives to existing things, with different solutions to different problems aimed at different people, is a healthy process of innovation and there is nothing wrong with it.