This great piece of technology doesn't belong to them. I would use it if it was owned by some other company that's more fit for the ownership, such as Google, because I know they have a clear business model and know exactly what they will do with the data they gather. But at this point Twitter has 0 trust among developers.
Why would I depend on a piece of technology developed by a company that's struggling to find a way to make money and will probably do whatever is possible to extract value out of its assets? (Which includes spinning it off to oblivion)
Having said that, I'm personally always wary about using an infrastructure piece for free. If my app relies on something, it's pretty important that it not easily go away. I can't count the HN threads of upset developers, frustrated about something being shuttered that was provided free.
Disclosure: I'm the co-founder of https://raygun.com which does mobile crash reporting, and more.
There were some rumors that Twitter has tried to spin off Fabric into another home, but it sounds like potential buyers balked when they saw the costs associated with it.
The prevailing theory is that Twitter originally saw this as a way to collect user data in the mobile app paradigm in the same way that the Twitter "follow" and "tweet" buttons do in the web paradigm. It sounds like it hasn't paid off, though.
In the scheme of Twitter's self-reflection trying to figure out how to cut costs and find what it wants to do, do you feel Fabric fits into it? Do you feel the 'core platform' i.e. the microblogging site fits into it? Should the less strategic one of these be spun out; or should they be less separated?
[1] https://get.fabric.io