> but people who got burned by the change already got burned, and they want to avoid it in the future.
They likely have also put effort into moving to other frameworks, and if those are working out well enough for them there is no point making the effort to go back even with this change reverted.
Same for new projects that went directly elsewhere: unless Unity offers significant benefits (and the project controllers feel that Unity can be trusted not to repeat the rug-pull later) the effort of changing stack are likely not worth it.
They likely have also put effort into moving to other frameworks, and if those are working out well enough for them there is no point making the effort to go back even with this change reverted.
Same for new projects that went directly elsewhere: unless Unity offers significant benefits (and the project controllers feel that Unity can be trusted not to repeat the rug-pull later) the effort of changing stack are likely not worth it.