# Survey: Features & API-Compatibility

**URL:** <https://discourse.numenta.org/t/survey-features-api-compatibility/5344>\
**Category:** NuPIC Community Fork\
**Tags:** question, community\
**Created:** [January 30, 2019, 3:31pm UTC](https://discourse.numenta.org/t/survey-features-api-compatibility/5344 "2019-01-30T15:31:20Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![breznak](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.numenta.org/breznak/32/1935_2.png) [@breznak](https://discourse.numenta.org/u/breznak)\
**Post date:** [March 28, 2019, 8:13pm UTC](https://discourse.numenta.org/t/survey-features-api-compatibility/5344/23 "2019-03-28T20:13:34Z")

</div>

Follow up,  
we’re discussing dropping support for old features, which will allow us to work better with modern TM and friends.  
Have a look,

> [@Biological Constraints](https://discourse.numenta.org/t/biological-constraints/5687):
>
> In the C++ community fork, we’re considering dropping support for several features which are not biologically plausible, but which may be useful nonetheless. Summary of the features in question: BacktrackingTM This is a variant of the Temporal Memory algorithm. It is specialized for anomaly detection, and on the Numenta Anomaly Benchmark it scores approximately 5% higher than the regular Temporal Memory. It is not biologically plausible. Numenta has stopped working on it in favor of the regul…

---

_[View the full topic](https://discourse.numenta.org/t/survey-features-api-compatibility/5344)._