BetaMax was fantastic (all technical people said so).

The DotCom revolution was fantastic (the infallible financial gurus of Wall Street said so).

MS Bob was fantastic (BillyG said so).

Each version of SQL Server is so fantastic that there's always a new release in progress and publicized well before the latest one ships.

It's a strange world we live in.



>It's ok when a product is fantastic. But there's a danger with the mentality you describe.
>
>The problem is that if the new product is not fantastic but still the majority uses it then just because of the herd movement it'll become fantastic no matter what. I mean if so many developers use it it must mean something. Then it can't be that bad.
>
>From that point it's hard to know if the product is really fantastic or not because the developers are going to push it at all cost. They're not crazy everyone wants to earn a living even if they work with less than perfect tools.
>
>We should'nt change a developers tool just because it's new but because there are real advantages to make the switch.
>
>To those that want to reply to tell me how FANTASTIC .Net really is as a reminder you should know that I never used .Net. It could be fantastic but because of what I just said before I don't think that what you'll tell me will make a big difference. I'll just call that the corruption factor <vbg>
>
>
>
>>Just my 2 cents, but, I like using vfp because it is different. There's something about completely following the herd mentality(.NET) that I just don't like...
>>
>>>Rod,
>>>
>>>I realize that I can't go on for 10 years with VFP but right now I don't see why I'd change anything in that department. It's not that bad yet.
>>>
>>>>Denis,
>>>> Your choice of VFP may matter in the future. Here's a couple of questions
>>>>
>>>> 1. Are you building a product that will be used in an IT setting ?
>>>> 2. Are you using DBF's ? If the answer to 1 is .TRUE. then it will matter
>>>> very much. The UI might not matter but the data structure does matter.
>>>> 3. Do you plan on selling out eventually ? If so it does matter.
>>>> If a company is looking at your code they are probably gonna say What
>>>> is this VFP stuff? Where can I find developers. Etc...
>>>> 4. Do you ever want to hire employees to work on this stuff? Where is the
>>>> new pool of VFP talent gonna come from ?
>>>>
>>>>Just a couple of ideas
>>>>
>>>>Thanks
>>>>Rodman