|
|
|
|
|
by trescenzi
125 days ago
|
|
I find this line of thinking so hard to follow. I happen to have worked at FactSet and when I was there we were stuck supporting chromium 18 because it was embedded in the version of the workstation that a partner had signed a contract which prevented them from needing to upgrade the base install. SASS is of course to some extent about functionality. Maybe it will make sense for larger customers to duplicate functionality themselves using AI. I very much doubt we’re anywhere near being able to prompt Claude and get FactSet out but fine we can grant that. The reason SASS is so valuable though is because it allows firms to pass off the costs and risk of maintenance behind SLAs. Why would you want to bring that risk in-house when you can essentially buy insurance against software errors by paying a SASS company? |
|