Major VFP News from Redmond - Good and Bad (Sad)
From the comments:
said...
There is nothing good about MSFT discontinuing support for VFP. Have you really tried to work with .BLOAT this product is a JOKE!
To make my case:
1) The OOP implementation used by the smart tag controls mixes programming code that should be in the business tier into the interface layer in the code behind.
2) The debugger is missing from SQL Server. Yeah you can debug SP from .NET if you can get the setup correct and have a ton of luck.
3) Unless you are performing very basic tasks stored procedure functions performance is horrible. Therefore you have duplicate code in your stored procedure.
4) In .BLOAT design a business tier with a data reader object and pass it to the front end to consume. That works well except the front end has to close the data reader created in the middle tier. Again not exactly great OOP principles.
5) Say you have a stored procedure which you want to perform against an entire dataset that requires input parameters.
Common sense would dictate a syntax such as exec mysp (select field1, field2 from mytable) would do the trick ...
Sorry guess what have to use cursor and fetch which is slow and requires a ton of code.
6) In a select statement the field list and group by clause have to match identically, a sql standard right ... well try getting the unique identifier for the row returned by the group by clause.
When do you ever design a report that just had a sum, min or max field. It is a royal pain ... In vfp just change the set enginebehavior.
7) People all excited because ling is supporting a skip clause give me a break that has been in foxpro since the beginning. what is the next coolest feature they are putting into ling SCAN FOR logic.
8) The class designer is all smoke and mirror in VS 2008 ... Where is the visual inheritance of controls? Missing ... Try to tie two classes together in the designer, cant be done need to code it out. The class designer sure has a sharp UI however too bad it functionally blows.
9) Object Security. It does not exist in VS 2008 even if you implement private classes you can just use c# reflection to get at the inner workings of the class. WOW bet no one would figure that out.
10) Object firing order in vs 2008 controls. In VFP events and methods fired in a predictable manner. Just take a list box control in VS.BLOAT and try to determine the event firing sequence it is eratic as best.
11) MVC is supposed to be a big enhancement for VS 2008 only one problem the framework didn't ship. Beside the fact, why must MSFT develop a new programming paradigm every freaking release of .BLOAT. Perhaps if they did it right the first time we would not have a new one stuffed down our throat.
12) MSFT couldn't get ASP forms to be response and eliminate the refresh so instead of fixing the issue they create yet another tool AJAX.
I could go on but you get my point ... I'm sick and tired of people cheerleading MSFT for crap development tools. If MSFT killed off VFP and a suitable replacement development environment existed I would not have a problem with their decision. But basic tasks I can do in foxpro for DOS is freaking missing from .BLOAT. .BLOAT is far from mature and is NOT by any stretch of the imagination data centric and people are applauding MSFT'S decision, this is ridiculous. Instead of wasting time on language such as f# or silverlight they should have incorporated VFP data functionality into VB.NET or ported the language into .BLOAT before killing the product. People make their living writing data application and NOW MSFT does not have a single data centric language I dont get it ...
When are people going to tell MSFT we are tired of this crap !!!
No comments:
Post a Comment