[03:05:31] <wm-bb>	 [telegram] <mahir256> The current recommended framework for client-side UI elements is OOUI (jquery.ui having been deprecated), yet there is a fair amount of discussion in some circles about switching to Vue. Should existing jquery.ui gadgets and userscripts thus be rewritten with Vue in mind?
[05:32:52] <wm-bb>	 [telegram] <amire80> Not an official answer, someone may know something more precise: jQuery and OOUI are indeed being deprecated, but VERY SLOWLY. Most of the development is still done in these two. The day on which jQuery won't be loaded on all pages is probably many years away.
[05:33:43] <wm-bb>	 [telegram] <amire80> Vue is indeed starting to enter, but no one is totally certain how and when.
[05:35:18] <wm-bb>	 [telegram] <amire80> So now is probably a good time to start thinking and talking about rewriting gadgets in Vue, and maybe even trying to do it, but probably not to actually deploy it.
[05:37:28] <wm-bb>	 [telegram] <amire80> To the best of my knowledge, Vue is not loaded on all pages, at least yet. Also, it's not entirely clear which version will we use. There were some debates about it last time I checked.
[05:39:26] <wm-bb>	 [telegram] <amire80> The project that is using Vue most actively is, again AFAIK, version 3 of Content Translation. It's not yet deployed anywhere, but it hopefully will be very soon. See https://www.mediawiki.org/wiki/Content_translation/CX3
[05:40:07] <wm-bb>	 [telegram] <amire80> I think that something in Wikidata was also done with Vue, but not entirely sure.
[05:42:43] <wm-bb>	 [telegram] <amire80> So if you are involved in developing gadgets, start playing with it, and discuss it at https://www.mediawiki.org/wiki/Content_translation/Vue.js 
[05:42:44] <wm-bb>	 [telegram] <amire80> . But don't expect a big full migration right away.
[06:50:54] <wm-bb>	 [telegram] <Thecladis> Considering how js frameworks change all the time 😅
[07:27:24] <wm-bb>	 [telegram] <lucaswerkmeister> +1 to everything Amir said :)
[07:27:59] <wm-bb>	 [telegram] <lucaswerkmeister> Wikidata things using Vue include "Data Bridge" and "Tainted References" (no links bc phone)
[07:29:41] <wm-bb>	 [telegram] <lucaswerkmeister> and the Vue-powered OOUI successor is / will be called WVUI iirc (we don't use it yet in Wikidata, though no doubt we'll eventually switch to it instead of our own component library)
[09:32:41] <wm-bb>	 [telegram] <Thecladis> Wikidata is not exactly the best example of a frontend with some pages barely loading 😅 And the more complete items are the worst it gets 😅
[09:36:32] <wm-bb>	 [telegram] <lucaswerkmeister> …do I dignify this with a response, or is trashing other people’s hard work just your idea of a nice christmas morning and I should leave you to it? (re @Thecladis: Wikidata is not exactly the best example of a frontend with some pages barely loading 😅 And the more complete items are the worst it gets 😅)
[09:36:43] <wm-bb>	 [telegram] <lucaswerkmeister> I guess I’ll write something for the benefit of the other 446 people in this chat
[09:37:06] <wm-bb>	 [telegram] <lucaswerkmeister> the parts of the Wikidata frontend you’re complaining about are not written in Vue.js, in fact they largely predate any public release of Vue.js
[09:37:55] <wm-bb>	 [telegram] <lucaswerkmeister> eventually more of the Wikidata frontend will be written in Vue, and hopefully it will be much more performant and generally nicer and everything by that point
[09:38:01] <wm-bb>	 [telegram] <lucaswerkmeister> but we’re not there yet
[09:38:22] <wm-bb>	 [telegram] <Thecladis> I by no means intend to trash someone's hard work. (Okay, I sometimes do, but only regarding some particular extensions and Wikibase isn't one of them). But as an end user I end up with some pages being unusable on my computer, so...
[09:38:44] <wm-bb>	 [telegram] <Thecladis> But that is good to know if Vue indeed is to mitigate that
[09:45:04] <wm-bb>	 [telegram] <Thecladis> (As to the Catholic Christmass morning, well, I definitely do not act upon my idea of what some holiday days are supposed to be like, not sure what that was supposed to be about)
[10:00:52] <wm-bb>	 [telegram] <lucaswerkmeister> I may have overreacted a bit there, sorry
[10:01:25] <wm-bb>	 [telegram] <lucaswerkmeister> but if I’m not supposed to talk about how we’re trying to improve the frontend while there’s still technical debt elsewhere in the stack, I won’t have opportunity to talk very much at all (:
[10:25:15] <wm-bb>	 [telegram] <Thecladis> Thank you. I did as well.
[10:25:16] <wm-bb>	 [telegram] <Thecladis> Well, as long as improvements are improvements, and not just from the code maintenance but also usability perspective, that is something which is definitely good and definitely to be talked about 😊