At 04:28 PM 1/29/2008 +0100, Eyvind Axelsen wrote: > >> True, but we all rely on the tools we use, and to code everything in > >> assembler is not something you'd want. ... > > What the hell does assembler have to do with anything? > >Come on now, Ed, that was a simple analogy that most should be able to >follow. Most tools allow for abstractions and/or code generation for >complex features. In that respect, code ... > >> Python is a platform as well,
Well, you need to be careful with terms - pretty much all software terms are "made up" so you gotta be very careful in usage. "Platform" has a pretty specific meaning in the computer world (at least I thought it did). A programming language is not considered a "platform". And, by the way, Assembler is actually a programming language too. I think the term you were looking for was "machine code" as in "... you wouldn't want to write everything in machine code..." ... > > Well, duh! So will we all. But at least until those events, going > >with a non-proprietary solution doesn't lock you into it when things > >change in the future. > >Yes, everything dies, and I, for one, believe that there is more future in >the .NET platform than there is in Python, though there is no one true >answer to that. Actually, if you had started out in Python years ago, you would not have had the same "forced" upgrade costs as you have with Windows tools. Hmm... I suppose that's sort of apparent - Python cost ~ 0, Win tools ~ thousands? (for a team of developers). And since a single vendor does not "control" Python, you won't get a "oh... time to change... you must redo your .Net projects in .More$4MS..." >Did I ever mention that he should limit what he is checking out? And, >while we're at it, could please provide examples of something that would >work equally well within a limited time frame from Fox (possibly utilizing >COM, if required) for a complex web service? What is on the "consumer" side of things? As an example, several systems I've deployed have a VFP rich client on the desktop, and a VFP "server" component at the central office. The desktops communicate to the central office over the web - basically using "http" as the web service. The central office gets the request and transmits data back, which the desktop application correctly interprets and uses. The desktops can work completely independently if no Internet connection is available (of course, the specific central-based messages/functions are not available at that time). We used WestWind WebConnection as our go-between piece on the central server. We do NOT use xml to pass data back and forth - we use more efficient formats where possible and generally compress them into .zip format as well. Some of the messages we exchange pass complete databases (hundreds of tables), or simple "Yes/No" responses. Now, if you're talking about a web service to be consumed by the masses, then the above approach would not be for you. I would also suppose that most MS-generated results would not be advisable either since the consumer could we be a non-MS piece of software. -Charlie _______________________________________________ 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.
