Maintaining community is one thing and developing an innovative tech is another.
I really appreciate what XMR does to CryptoNote promotion and development of pools, wallets, etc. However, if you take a look at their recent transaction pool changes, you'll be quite surprised.
Firstly, Monero devs changed the source code so that the transactions could stay in pools forever. This lead to transaction piling up to 250+ transactions in the daemon tx_pools, which were not going anywhere at all and could be stuck for eternity.
Secondly, they took BBR solution to the problem and I assume didn't even bother thinking deeply on what they were adding. The 24h limit for transactions in the pool was a solution but again not a wise one. As there are no wallet notifications, the wallet doesn't know anything about the transactions being reversed. Users, services are not notified on the process at all.
What's more, if there are older daemons in the network, a more interesting case is possible. The transaction is reversed in newer daemons, the inputs are free again for other transactions. But when they're used, the older daemons (which didn't get the transaction out of their tx_pools) have to report double-spending attempts.
This is not how you make critical updates for the currency.
1) Monero developers should evaluate the long term consequences of their commits. Each unthought solution can cause drastic problems in the long run.
2) Monero developers should allow a compatibility window in order to make sure that the network is not split during the update. It's not about "mandatory update" alert on the forum, but a sophisticated approach inside the source code.
And that is why I prefer Bytecoin developers approach. I'm sure they can't ruin the network with one random commit. Can't say the same about XMR devs.
This can be crucial for the exchanges and pools. What if a user withdraws the money and it got stuck and reversed after 24 hours?
If you are right, I assume the service gets the transaction back without any notification about that. Suddenly, there is simply money on the wallet with no other information on the transfer. So the service will have to manually recalculate all the incoming and outgoing transactions to test, who is the transaction owner. The larger your service, the more useless work you should be doing on the daily bases.
That's not too friendly towards the businesses working with Monero for sure.