We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
This is partly covered by #3533, partly already exists (the actual DB table storing individual keywords which IIRC was new in v10), and partly I'll add new issues for.
I don't want us to add filtercode autocompletion, just because that is a level of IDE I think is beyond what we're aiming for, and would set a very high bar to meet consistently across the product.
I don't want us to add filtercode autocompletion, just because that is a level of IDE I think is beyond what we're aiming for, and would set a very high bar to meet consistently across the product.