-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: PixiJS v8 Support #209
Comments
I have too much other stuff going on to do that I'm afraid. Also, I don't really see the need of PixiJS 8 I general, why would I go with that instead of v7? (At least in the areas I'm working with). I guess it's to support WebGPU, but not sure if there is anything else? |
Mostly because v8 is a complete rewrite and they likely won't do any further major work on v7, so it will eventually code rot. There are a lot of optimizations in the new code and API. WebGPU is interesting because it offers some more possibilities. I also work with @pixi/react and that's being moved with a complete rewrite from v7, so I'll eventually have to make the transition myself. I get being busy though. I'm still working through a bunch of upgrades myself, but I was curious if there was interest here. |
Yes, I will definitely use v8 later. But right now v8 doesn’t really offer any new features (as far as I know) compared to v7. I’ll stick with v7 for a while more for the production apps. WebGPU works in all major browsers nowadays? |
I'm not entirely certain on the browser support front, but one thing I am looking into is React Native's WebGPU rendering layer, which would allow me to stop needing to use a WebView with RN once I get it working. |
With the new massive rewrite of PixiJS 8, it seems a good amount of work will need to be done to support the new paradigm. Is this project still maintained, and if so, what would it take for v8 support? I might be interested in collaborating on this if there is interest.
The text was updated successfully, but these errors were encountered: