Like any technology, both ForSource and Git have their respective downsides. Here are a few potential drawbacks for each:

ForSource:

- It is a proprietary system, which means that you may be limited in terms of customization and flexibility.
- It may not be as widely supported or integrated with other tools as Git is.
- Some users have reported issues with stability and performance when using ForSource, although this may depend on the specific project and hardware setup.

Git:

- The learning curve can be steep, especially if you're new to version control or command line interfaces.
- While Git is compatible with a wide range of projects and programming languages, it may not be optimized for use with Unreal Engine projects in the same way that ForSource is.
- Large binary files (such as game assets) can be more difficult to manage with Git than with other version control systems.


In terms of why I might recommend Git over ForSource, it really depends on the specific needs of your project and team. Git is generally more widely used and supported in the software development community, which means that it has a larger user community and more resources available for learning and troubleshooting. Additionally, Git's flexibility and compatibility with many different types of projects could be advantageous if you work on multiple projects or use a variety of programming languages. That being said, if you are primarily focused on Unreal Engine development and prioritize ForSource's unique features (such as Blueprint merging), it could be a good choice for you.
spam fails_task lang_mismatch pii not_appropriate hate_speech sexual_content quality toxicity humor helpfulness creativity violence