Yes, and? Other input systems exist (ReWired) that can be used with Unity. Other multiplayer systems exist (PUN) that can be used with Unity. But here we are. This changes nothing about the suffix being (rather, seeming) superfluous.
From the perspective that the ECS concept isn’t an architecture Unity Technologies invented, having “ECS for Unity” does make sense. It still seems out of place, though.
In my opinion it would be unhelpful because DOTS is not a monolithic stack at this point.
DOTS is very unspecific. If someone says, “how do I do this in DOTS” no one is going to understand what they mean. It is a term from before Bust and Jobs became part of the MonoBehaviour ecosystem. I don’t think that anyone at Unity expected Burst or Jobs to become part of the MonoBehaviour ecosystem but that is what happened. It would be best to just drop the term DOTS.
I made a poll earlier and many people are only using Jobs with MonoBehaviour. 20 people are not using ECS correctly or only using Jobs. 44 are using it correctly. So 31.25% of people are not leveraging ECS.
That’s not true. If you search DOTS just enywhere on the intheret. You will land on pages and even Unity blog post and main DOTS page. Each explains exactly what it is. What includes and what it is this tech stack purpose. Which goal is he performance.
Does scripting burst alone means anything? Does jobs? Or even ECS?
It will not. They alone make no sense to anyone besides very norrow low level group of devs and it is unclear, that they are highly compatible, to gain performance.
If I would see them for the first time in such form, I probably wouldn’t even bother with burst, or jobs. I wouldn’t even know, these are compatible.
ECS alone doesn’t mean it can be multithreaded. Unreal has ECS too. It is just way of data and systems handling. So now Unity basically steps down to equalise with Unreal.
People will not be clearly able to connect dots, how to build performant code, if Unity forum structure will be in such mess. It will lead to alienate DOTS performance focus devs, from the rest of Unity community. Just because all is now fragmented all over the place.
As fro MB with ECS, why it is a problem?
It is not like people will try to run ECS, without jobifying them and without burst, just for little gain and so much additional effort.
So what is the point here?
People are for sure using the job system without ECS. At this point why insist despite all evidence to the contrary that many people are doing this. You may not understand why this is the case, but it is the case. Since ECS tends towards far greater changes to your code base then just multithreading a few parts using the Job system.
The ECS user is fundamentally different from the Job system user.
The point is, that we discussing this just because DOTS brought this community together. It brought us here. You, and me and others.
If not for that, we wouldn’t even be discussing it.
Consider this. You joined this community because of capability of DOTS, of how it was promoted and which is fruit of a cumulative work both Unity and our community.
Yes jobs can exists alone, so it is burst and ECS.
We have Entitias. It was even paid, before ECS was announced few years back. But it was very narrow group of people who used it. Very specialized one. And not because of the price tag. Entities was for years. And other ECS APIs. Most of current DOTS devs wasn’t even aware what ECS was before DOTS. Nor burst.
Again, it is DOTS, which has have built this awareness and community knowledge. Not individual components / APIs.
Now we are patriating it. That what worries me.
This is how I strongly feel about it. And that is why I continue to defend my stand.
I do not use those features myself, but don’t the forum features “watch forum” and “follow people” allow you to set focus on what you are interested in? I guess there is no one static structure that would satisfy everyone.
Me included. I liked the old way better and would not be surprised if most early adopters feel this way…we can consider ourselves lucky to spend time on such trivial concerns…Merry Christmas.