Sign in to follow this  
jinzo7

PIXI current versions in the future ?

Recommended Posts

Hello, developers! 

I am wondering about PIXI v.3 or v.4, how much they can live and work on the internet.

Imagine now I start big project on v.3 or v.4. This project should be licensed with little exceptions.

Should I extract the whole code related to PIXI(my view) to be specially maintained over the time?

What is the experience on similar cases?

What is the risk? 



 

Share this post


Link to post
Share on other sites

my personal opinion is that pixiGuys make a lot of effort to alert retroCompatibility.

When a code becomes obsolete, your program works but you get alerted that changes are being made.

so the risks are minor, if you work neatly.
However I think that v.5 will be very different from v.4

these confirmed, but I have read some discussion, and this should not be too difficult to update.
Ideally, it is necessary to work by module, thus during a critical update, only the modules updated need to be modified.
Rarely the integral logic of your application.

 

Share this post


Link to post
Share on other sites

Currently I would go with pixi v4. It is pretty mature library at current point.

Depending on your project the same code will work on v3, v4 and v5 with small modifications. Though if you do something like custom renderers, filters, meshes and so on then you most likely need to do a lot more migration work if you want to change the major version.

Inside a major version I have had no troubles updating.

I have about 5 projects still working nice with pixi v3 and have had no problems from clients and havent done any updates related to graphics to those after they have been released (2-4 years ago). Same story with pixi v4 projects, the graphics part rarely needs updates.

Share this post


Link to post
Share on other sites

Risk is minimal.  Minor updates are usually for specific reasons - a particular feature or bug fix.  So there is often only need to update if such feature or fix directly affects our project, sub-library, or user base.  Generally this is rare for a library as mature and well tested as Pixi.

Major versions (and resulting deprecation) can be very exciting for early adopters but should be considered a "new book" - before opening we should check if we've finished the previous book and pre-identify why the new book is better.

Share this post


Link to post
Share on other sites

Risk is big in my experience, I built an entire framework around PIXI 4.1.something and when later tried to update to PIXI 4.5.something (I think it was 5) all hell broke loose. This was a huge disappointment to me, I was expecting PIXI 5 to do that eventually but not while still in version 4. I did evaluate the changes and found they were deep and numerous to the point that my framework would have to be completely rewritten. problem is I already have a bunch of apps in production and I can't throw so much testing time down the toilet and start over. So I'll stick to 4.1 for now and make the updates myself and as for PIXI 5 I might have later to adapt it to my framework and not the other way around. It's really a trend that I think Apple started with all frameworks nowadays, why being backward compatible when you can simply just not care about it at all. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.