浏览代码

Update README.md

pull/72/head
Sebastiano Mandalà GitHub 2 年前
父节点
当前提交
24ea0f1a7a
找不到此签名对应的密钥 GPG 密钥 ID: 4AEE18F83AFDEB23
共有 1 个文件被更改,包括 3 次插入0 次删除
  1. +3
    -0
      README.md

+ 3
- 0
README.md 查看文件

@@ -5,6 +5,9 @@ Real ECS framework for c\#. Enables to write encapsulated, decoupled, maintainab

## Why using Svelto.ECS with Unity?
Svelto.ECS wasn't born just from the needs of a large team, but also as a result of years of reasoning behind software engineering applied to game development. Svelto.ECS hasn't been written just to develop faster code, it has been designed to help develop better code. Performance gains is just one of the benefits in using Svelto.ECS, as ECS is a great way to write cache-friendly code. Svelto.ECS has been developed with the idea of ECS being a paradigm and not just a pattern, letting the user shift completely away from Object Oriented Programming with consequent improvements of the code design and code maintainability. Svelto.ECS is the result of years of iteration of the ECS paradigm applied to real game development with the intent to be as foolproof as possible. Svelto.ECS has been designed to be used by a medium-size/large team working on long term projects where the cost of maintainability is relevant. Svelto.ECS can be educative for all kind of developers, but small teams must take in consideration the learning curve/cost of ECS in general and Svelto.ECS in particular.

Svelto.ECS is also fully compatible with DOTS and Svelto.ECS code can be fully burstied and jobified.

Svelto.ECS is compatible with Unity 2019.3.x cycle as long as it's not used with DOTS ECS. If DOTS ECS integration is necessary, Svelto.ECS will always target the last stable unity version using DOTS.

## Why using Svelto.ECS without Unity?


正在加载...
取消
保存