Microsoft killed FoxPro in 2007. Anyway, here's FoxPro revived
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Microsoft killed FoxPro in 2007. Anyway, here's FoxPro revived
Unofficial Hacker News client; not affiliated with Y Combinator.
rufugee · · focus · HN ↗
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...
sm-silversight · · focus · HN ↗
rufugee · · focus · HN ↗
I would welcome a community effort. There are many (?) companies still relying on FoxPro. Vibe coding a solution is feasible these days. We've vibe-coded a few from FoxPro to Ruby on Rails with great success. I'm no longer stressed about the future... just the timeline.
boredjohnny · · focus · HN ↗
boredjohnny · · focus · HN ↗
rufugee · · focus · HN ↗
boredjohnny · · focus · HN ↗
rufugee · · focus · HN ↗
briHass · · focus · HN ↗
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.
rufugee · · focus · HN ↗