The other fella covered the more general user-generated approach, but the WefWef app has a way to migrate from Apollo using the JSON export tool they (Apollo) provide. Looks like the grab the JSON dump, parse out the subs, then generate a big list of community search links in-app.
Expanding on that, a potentially good idea to make this as easy as possible is to find a way of having the user export a list of subs from their Reddit account (either by biting the bullet and using the API or developing a user script or browser extension). Allow clients to register an anonymous user ID (to avoid tying identities together too hard) with such a list. Then the clients can update this user with what communities they join via what instances, along with what instances they joined at all.
Then your service would feed them recommendations."Users from /r/programming[,...] tend to join [email protected]" and/or "Reddit users like you usually join the fediverse through programming.dev".
It may be worth DMing some of the Lemmy client developers to see if they'd be interested in such a service or if they have any better ideas. Smart people, them.
If you do end up doing work on this, please do post any cool ideas you have! It's a neat domain space.
Hope you have a great day, good luck!
I'm not a big subscriber to this notion. After working in both of the technologies (and more), and React/Vue is a significant boost in developer productivity compared to jQuery and AJAX. More features, less bugs, a more app-like web experience. Not to mention things like Native or Electron potentially saving on the cost of entirely separate apps.
Further, the resulting assets can be even smaller after minification and bundling as long as you aren't creating one giant blob that gets shipped on every minor, unrelated change and includes all the dependencies and source maps and assets – it's important to remember many bundlers include media files – on production.
I think there's numerous opportunities for improvement to be had (diff-based updates, semver-aware CDN, smarter defaults, more leveraging of things like WebASM and improvement on the standards), for sure, but talk of "the good ole day" of jQuery certainly seems rose-tinted given how much of a mess it was in practice (for me, of course).