zlacker

Probably because Microsoft knows vibe coding is _not_ an actual viable way to build production ready code and does not want to deal with the liability issues of prompting customers to move from a working Excel sheet to a broken piece of software that looks like it works.

In my experience, it's actually quite hard to move a business from an excel sheet to software. Because an excel sheet allows the end user to easily handle every edge case and they likely don't even think in terms of "edge cases"

>>ImPlea+(OP)
You say that, but the crazy people at Microsoft put a COPILOT function into Excel already...

https://support.microsoft.com/en-us/office/copilot-function-...

>>ImPlea+(OP)
> Probably because Microsoft knows vibe coding is _not_ an actual viable way to build production ready code and does not want to deal with the liability issues of prompting customers to move from a working Excel sheet to a broken piece of software that looks like it works.

Whilst you could plausibly argue that Microsoft have spent the past 25 years attempting to stamp them out, this is exactly what VB6 and VBA were.

People built whole businesses on/around these technologies, and people liked them because you could get something working fast. As maligned as they are nowadays they were so widely used because they delivered value.

>>ImPlea+(OP)
Reliability doesn't matter any more, there's no liability for being wrong any more.