See phab:T241180 - does it mean after migration from jQuery UI and MediaWiki UI to OOUI, we will migrate all special pages to Vue.js?
Topic on Talk:OOUI
We don't know yet. Possibly we'll be able to re-tool OOUI to use Vue.js, possibly we'll create a new library for the same use cases, possibly something else. We're still at the exploratory stages.
What @Jdforrester (WMF) said, we're currently exploring and evaluating different paths. In the short-term we're commited to continue development and maintainenance of OOUI as it's used widely in our ecosystem. When alternatives have been reached a production-ready level, it will highly-probable be deprecated.
Will there be an attempt to remove jquery from ooui and switch to vanilla javacript?
No. We're already exceedingly sparing in where we use jQuery (only when it's faster than falling back to writing bespoke wrappers around native methods). As MediaWiki isn't planning to get rid of jQuery ever, the work to remove the last few uses when it's always around in the main environment for which we've built it isn't worth it.
There seems to be a push to remove jquery from existing software (like github did). What exactly is the point of doing this? Is it really much slower in terms of execution and loading up the jquery file ? I'm debating whether I should try to remove jquery from my wikipedia setup. The thing is that I use OOUI rather extensively (dialogs and forms) and I'd have to say goodbye to OOUI. I feel like OOUI is too complicated, large and slow to load. My gut tells me I should stop doing anything with OOUI for the time being. I tried to use OOUI as much as possible instead of using other third party libraries, but I find it annoying that I have to load the entire thing just to infuse a form and get a modern look.
As I said, we aren't planning to get rid of jQuery from MediaWiki. Attempting to do so on a third party installation is very likely to go poorly. I would not advise it.