2 ms·

Dear Lord in heaven, no. Yes, the data language and the application language were all the same language, which led to some awful spaghetti code where data acce

by steverb 12y ago

Dear Lord in heaven, no. Yes, the data language and the application language were all the same language, which led to some awful spaghetti code where data access was strewn all over the place. Then you also get to deal with scaling issues because your db and application logic all run on the same box. But hey, you can still download and run Visual FoxPro from MSDN if want, Source: My team is in the process of slowly strangling a FoxPro application whose only system spec is "what it does".

mamcx 12y ago
That is the description of almost all apps out there. Only with the popularization of MVC is started to be cool to decouple things. I see the same behavior in several codebases and languages (I do mainly business apps and code cleanup). But then, in the case of VFP, you still have a single kind of mess to clean, and a language/API small enough to fit in the head. Now, we are talking for several kind of languages, APIs and paradigms intermixed all around a project (like for example, mix a ORM, Sql, OO, not only python+js+html+css)