2010/3/16 Dmitriy Sintsov questpc@rambler.ru:
Why sajax is discouraged to use?
Basically because using jQuery on the frontend and API modules on the backend is much cleaner, so that's what we recommend for use in newly written code.
I hope that it won't be dropped, because it's small and has very little setup overhead. CategoryTree and my own extension uses it.
Yes, there's some stuff built on sajax, that's a known fact so it won't just be killed.
Will v1.16 release include jQuery?
Yes, although the way jQuery is included will probably change in 1.17 with the (planned) introduction of a script loader.
1.15 has a lot of installations, too. Can't there be sajax to jQuery compatibility layer (implementing sajax functions "indirectly" via jQuery)?
How is that relevant to 1.15 installs being around? Extensions have different versions matching different versions of MediaWiki, so this shouldn't be a problem at all. Like I said, sajax will be kept around for some time to come, and if your extension uses jQuery it shouldn't be claiming compatibility with 1.15 and below.
Roan Kattouw (Catrope)