5 ms·
Its what they use right now, who knows what is coming down the pipeline?
by thejosh 9y ago
Its what they use right now, who knows what is coming down the pipeline?
- k__ 9y agoI honestly don't know, but using it 1. for their main product 2. for many different products in general and 3. rewriting most it (v16) to be more future proof without public API changes sounds like a pretty save bet.
- coldtea 9y agoNobody. But the fact that they use it now makes it less likely to be abandoned by them that something they don't use (which, while they can't abandon, they haven't adopted either). Besides in 10 years the whole of IT changes. Don't look for "50 year frameworks".