Re: Alternatives To Foxpro

Don't you use firebug?
Should be named 'foxbug' as it looks and behaves so much like VFP IDE ...

-- thn

I totally agree Thierry... Client side is where the processing is now.. I think it's funny a huge company like Microsoft goes with jQuery.. I love jQuery for taming the DOM .. ajax.. makes some very pretty stuff.. But Microsoft will need more than jQuery in the future. ExtJS 3/4 can do so much more than jQuery.. "I use jQuery and ExtJS 4 together" They are both very friendly to the global "window" object. Javascript needs better debuggers and IDEs.. Hopefully we'll see them in vs2011.. Hopefully javascript projects in vs2011 will have options like "Build for Tablet" or "Build for Desktop" or "Detect the device and render appropriately"...

The server serves data. Client does the rest...

Frankly, I wonder what may be the interest of tracking milliseconds at building strings for a web page and/or JSON weighing around 50k, while data access and under-optimized code are by far more time consuming.

I never had a 'classical' request response time over 200ms with VFP/wConnect, and I see very little .php or .aspx sites doing any better.

IMO, and what I see from current web literature, far more important are topics like grouping, minifying and compressing resources on server side (CSS files, CSS background images, JavaScript), writing scripts just before </body>, and more. The time it takes to output strings is just minor compared to such time savers.

About code optimization, I'm always amazed when I see a coverage report ... and I always say to myself "gush, i could cut the number of instructions by 5!", again and again, each time I SET COVERAGE TO ...

I think we have much more to gain at refining the way we use VFP than spending years understanding another language to reach the same level of efficiency than we have today with VFP.

We are very lucky to have a stable platform and, as written earlier in this thread, the battle is on client side, no longer on server side. Microsoft has understood this too late.

-- thn

I haven't run any tests yet.. And I stopped doing new things .NET way before Microsoft got smart and made the MVC way of doing things.. So if they had Ajax/Json in mind when creating it.. C#/Net may be faster.. I will be going back to .Net when Windows8 VS2011 comes out to buld javascript projects. I currently have vs2010 and latest wconnect....

I'll run a test use

C# connecting to "OLEDB" Sql2008 1000 records "30 fields" ... I'm not going to render any controls.. when the Json is returned I'll using that time as the time completed.

VFP9 sp2 connecting to "OLEDB" Sql2008 1000 records "30 fields" ...

I'll also use

C# connecting to "OLEDB" foxpro tables 1000 records "30 fields" ... I'm not going to render any controls.. when the Json is returned I'll using that time as the time completed.

VFP9 sp2 useing native "Select *" 1000 records "30 fields" ...

Thanks
JimM