Thread

1. rufugee · 1790120188 · focus · HN ↗

   We run 500 KLOC of FoxPro at my company, daily. It is the engine that fuels a $500M business.

   I hate that it's the hand I'm dealt, but aside from AI rewrites (underway), there's no good answer. It's complicated by our reliance on DBFs.

   I welcome efforts like foxscript and anything else in this space. There are still a significant number of FoxPro apps out there and no one has a good answer. If you are struggling in this space, leave a comment here. I'll reach out to you. Strength in numbers...

   1. briHass · 1790132926 · focus · HN ↗

      DBFs tend to be the easy part, in my experience in a similar company (not as much revenue.) The spec is simple enough that one can write a reader/writer in an afternoon, even before AI.

      My biggest challenge is the speed at which calculation heavy business logic can operate in FP, even on network shares, as long as they're optimized for IOPs not bandwidth. Trying to adapt similar data access patterns to a networked RDBMS will kill you with round trip and connection overhead. Converting that logic to set-based operations or stored procedures means altering logic and all the risks that entails.

      1. rufugee · 1790283529 · focus · HN ↗

         The issue we face is CDX. We have >100 dbfs, and >600 clients hitting them at all times.

Unofficial Hacker News client; not affiliated with Y Combinator.