|| If the community is not willing to "step up", then the project isn't worth doing. Sorry, but that's the bottom line in open source development.||
And while true, it demonstrates the biggest weakness of open source development. Some products need big dollars put up front to get off the ground. I would suggest that this is one of them. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ed Leafe Sent: Wednesday, 21 April 2010 10:55 AM To: ProFox Email List Subject: Re: VFP Studio - vapourware ? On Apr 20, 2010, at 8:11 PM, Rick Schummer wrote: > The problem that Craig and Bo faced was the typical Microsoft nonsense of > changing targets. Like nailing jello to the wall. Since it's so typical, it raises the question of the wisdom of continuing to invest in Microsoft solutions. > VFP Studio is using the Visual Studio Shell for the IDE. Basically the guys > would pour a lot of time getting the VFP Studio working, Microsoft would > update the Shell and break everything they did. They would fix and adjust > course and Microsoft would break more stuff, rinse and repeat. Craig and Bo > got sick of wasting time. Once Microsoft decides to firm up the Shell > (hopefully VS2010 is the ticket) they might give it another go. Ah, yes! *This* time Microsoft won't pull the football away as developers run up to kick it! (sorry, Charles Schulz). They've changed! > Another thing is they were looking for help. Lots of people raised their > hand to *use* the final *free* product, but when they ask for help people > sit on their hands. This is the SOP for most open source projects. You have to have people who are willing to trade their time for the eventual product, and for most people, it just ain't worth it. You have to be solving a big enough pain point, and apparently, most VFP devs are happy with the tools they already have. > Then there are those who just complain on public forums > that they are not doing things when in reality there are good reasons to > wait and see what Microsoft is going to do with the Shell. If anything the > guys are bad at making the case public on the Shell problem, but they are > about as busy as people can be. > > Not a lot of incentive from my perspective to get them motivated when the > community is not willing to step up either. If the community is not willing to "step up", then the project isn't worth doing. Sorry, but that's the bottom line in open source development. -- Ed Leafe [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
