Jump to content
Search Community

Will you drop legacy browsers?

massic80 test
Moderator Tag

Warning: Please note

This thread was started before GSAP 3 was released. Some information, especially the syntax, may be out of date for GSAP 3. Please see the GSAP 3 migration guide and release notes for more information about how to update the code to GSAP 3's syntax. 

Recommended Posts

Hi all,

I was wondering whether GSAP will drop support for legacy browsers.

I never dug into its source code, but since it's compatible with ancient browsers, I figure out there is margin for optimizing it even more by dropping the support for them.

I was thinking of something like jQuery did: a version for older browsers, another one for the latest (I know it would be harder to maintain).

You probably already considered the possibility to drop them and you also probably already optimized the code in order to trim away whatever is not needed for current browser on landing instead of on the fly, but I'd like to know your position about this topic :)

Link to comment
Share on other sites

Great question. Yes, I'm working on 2.0.0 and plan to drop IE8 support which will allow me to drop some legacy code and lighten up the files a bit. I do not expect 2.0.0 to ship for a while, though, since my plan is to rework a bunch of things and add features too. It'll likely take several months. 

 

Is there anything in particular you wish we'd do (or not do)? What prompted the question?

  • Like 3
Link to comment
Share on other sites

Thanks for the answer :)

There is no particular trigger for this question: I was just figuring out the complexity of your code, the several browser-exceptions you were applying, the difficulties of any amend by keeping in mind any legacy browser; all of this, above all, while keeping the first place in performance leaderboard :)
Trimming IE8 (and IE6, as far as I can read on Draggable docs!)  would save bytes, time, CPU cycles and above all neurons :)

  • Like 1
Link to comment
Share on other sites

Ha ha. Cool. Yeah, we definitely place a huge priority on performance. Dropping IE8 (and earlier) probably won't result in much of a performance gain because we structured things in a way that minimized its impact. But I'll certainly feel good about dropping that legacy code ;)

  • Haha 1
Link to comment
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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...