It was probably too much overhead to support Works. You’d still need an engineering team to support Works, and it wasn’t a big money maker. Much better to put s

It was probably too much overhead to support Works. You’d still need an engineering team to support Works, and it wasn’t a big money maker. Much better to put some Office features behind a compiler/licensing flag and support one product with different “home” and “professional” SKUs. But I kinda wonder the same thing about Apple’s Pages/Numbers/Keynote. I’m not sure the overhead to maintain those ultimately is worthwhile. It makes me think back on the old ClarisWorks or FileMaker setup where you ostensibly had an external company that made the product, but it was an Apple subsidiary. They could then offer the product for multiple OS’s. I’m not saying that business model was all that successful, but is there a place for an MS works in the time of Google docs?