For example, corfu [0] versus company [1]. Company works with capf, but you can also write your own backends for it (specific to company). Corfu also works with capf, but all backends are capf functions instead of a corfu specific backend.

Another good example is eglot [2] versus lsp-mode [3]. Eglot is actually packaged with Emacs now.

There's also other stuff, like vertico [4] (and others that are recommended to download) versus helm/ivy.

I also want to mention that packages that hook into Emacs more don't necessarily mean that they're better. From my POV it's more like you get a lot more things for free and the documentation you dive into will be Emacs specific instead of package specific. It all comes down to preference.

Vertico/Counsel/Orderless is very nice, but Helm and Ivy are fully featured (I always forget how much Helm has for you).

I use corfu, eglot, and vertico now. I have thought about going back to helm and company, especially since I was very familiar with company's backends for a long time.

[0]: https://github.com/minad/corfu

[1]: https://github.com/company-mode/company-mode

[2]: https://github.com/joaotavora/eglot

[3]: https://github.com/emacs-lsp/lsp-mode

[4]: https://github.com/minad/vertico

In practice we're seeing the biggest waves of development in years. r/emacs gets daily, daily! announcements of new packages. Many of them, if not most, are not some AI-sloped trash - they are very useful. Some package makers go above and beyond - even though vibe-coded, they still show good design decisions, proper tests, hand-written documentation. Canvas stuff most likely wouldn't be possible without LLMs.

This is a good thing. Custom environments should be either minimal or upstream. Anybody should be able to sit down next to you and help you hack out a change. The more unusual/custom your environment is the less productive that is, and this more than balances out any possible gain you can make from custom setups. (don't forget to account for your cost to learn elisp and then make the changes!)

Somebody needs to make the correct setups. However most of us have better things to do.

I wouldn't dismiss the help of lower friction of entry. Lots of recent Linux and neovim users due to how easy it is to debug an issue or edit a config now.

The larger the regular userbase, the more chances people gradually go deeper into the system.

I haven’t been all-emacs all-the-time for ages (I jumped back to the other editor after years of emacs), but hasn’t that super-elite group always been relatively small? We have to hope that the best of the next generation are going to self-select and be curious (and hopefully get the support they need from the established old guard) despite AI. We have to hope that the kids (no matter their age) will be alright.