backwards compatibility
2 stories filed under backwards compatibility on Beyond Market Intelligence. The newest of them: “Microsoft retires COPILOT function while keeping its Copilot feature alive” and “Self-contained schemas make your data readable across past, present, and future tools.”. Microsoft's decision to retire the COPILOT worksheet function on 14 September is striking, precisely because the company rarely abandons backward compatibility. Data formats usually die because they can't evolve. Acme AI is the next-generation, AI-powered spreadsheet platform built to replace Excel and redefine how analysts, data scientists, and enterprise teams work… The list below is every backwards compatibility story on Beyond Market Intelligence, newest first.
Microsoft retires COPILOT function while keeping its Copilot feature alive
Microsoft's decision to retire the COPILOT worksheet function on 14 September is striking, precisely because the company rarely abandons backward compatibility. The Copilot feature itself remains, so this isn't a retreat from AI assistance. It's a targeted removal of a function that likely saw limited, awkward adoption. Have you used it? If so, for what? I'm curious whether anyone genuinely relied on it, or if it was always a novelty.

Self-contained schemas make your data readable across past, present, and future tools.
Data formats usually die because they can't evolve. Seph Gentle thinks that's a solvable problem. His experimental format, Schemaboi, embeds self-contained schemas directly into file headers, so data stays readable without external definitions. It's a practical nod to HTML and HTTP's enduring adaptability. The focus on forward, backwards, and sideways compatibility means formats can shift without central coordination or data loss. That is a genuinely useful idea.