Re: [WebDNA] WebDNA vs. PHP code examples
This WebDNA talk-list message is from 2008
It keeps the original formatting.
numero = 101123
interpreted = N
texte = I think what your really interested in, is to code the best way in both languages. (even here you will get arguments as to what is right) Also it gets complicated you can't just say I coded this simple example and that is why we are better. There are issues, like the use of frameworks etc. not including depth of programmers and how quickly someone can take over your work, if your not around to continue updates or they just want to be able to replace you quickly should you disappear or just not work well with them or they with you. We have taken over php code that is not very object oriented, its just one long line of if-thens creating what is called spaghetti code and had to recode the whole smear. Other times the programmers well documented their methodology and it was easier to understand, but this is an issue with any language you choose. That is unless you're just trying to convince your customer and you're not really looking to do an in depth study of the pros and cons. In my mind the advantage that webdna has is that someone who isn't a programmer can do some complex things. They can build a quick database and deploy an application accessing that data. Is the data format right? Is it scalable? Well sometimes these question are less important when your trying to find out if something is even of interest and taking the time to build it for use by a million users a second is just not warranted. If you were building a brand new "ebay" I would say webdna is not your language, but if your going to build a quick interface into your backend support system or create one from scratch then it may be the way to go. Then it may work perfectly well until you've proven its worth and then some. At that point you can program it for greater use using your system as a basis for how the new program will function. On Oct 12, 2008, at 3:55 PM, Will Starck wrote: > If anyone has any code snippet examples of a few lines of code in > WebDNA vs. > something much longer that would be required in PHP code you post them > please? > > Thanks, > > > Will Starck > ------------------- > NovaDerm Skincare Science > http://www.novaderm.com > wjs@novaderm.com > 817-717-7377 > > > > -----Original Message----- > From: Donovan Brooke [mailto:dbrooke@webdna.us] > Sent: Sunday, October 12, 2008 12:29 AM > To: talk@webdna.us > Subject: Re: [WebDNA] a major shift in strategy? > > Meyers, David E. wrote: > >> Strategy? Think marketing and business not tech. >> >> I have been a WebDNA fan since I bought the original plug-in for 5 >> grand > over ten years ago. I have no where near the programming and "tech" > ability > of those that I see commenting on the talk lists - in fact, half of > the talk > list comments are greek to me. I continue to contract out to some true > WebDNA experts that have been with the software for years. I will > share the > observations that I shared with Smith Micro - who I feel we all agree > mismanaged and had little care for supporting WebDNA. >> >> As stated by Olin - Creating, managing, extending, modifying,? >> searching > and editing databases is about as easy as it gets. Bottom line - it > is VERY > simple and VERY powerful. Hell, I'm a designer and I have managed to > create > some pretty powerful solutions (even without the support of my > contacted > friends). >> >> In my graduate schools days, I had a genius of a professor who was > extremely successful (and quite wealthy) - he did nt have to teach, > rather > he chose to do so - he pointed out to students that companies and > products > will exist by falling into one of the following categories - They > will: >> >> Fail. (or) >> Survive. (or) >> Thrive. >> >> WebDNA has survived. >> >> I have shared this rather controversial position before privately, >> but > this time I throw it to the public forum and let you guys think > about it. >> >> WebDNA will never thrive as long as Php and MySQL is available for >> free > -snip > > > > Hi David, > I don't know if you realize it, but you made the case of exactly why > WebDNA > will > thrive, then you go on to say it won't. ;-) > > This subject, of course, has been the longest debate of the list to > date... > but the fact > is that we've pretty much nullified the "PHP is free" argument. A PHP > solution, in my opinion > will always cost more than a webdna solution.. especially now. The > cost of > WebDNA is > trivial at this point when you consider everything. PHP is free? > Hmmm, tell > that > to programmer that you are paying. Tell that to the database > company, or the > "solution" that you choose to use with it. Labor cost for a > developer, or > the > time it takes to "build stuff" drowns any perceived intial cost of the > product... > especially now. > > So, though there will always be plusses and minuses of different > solutions, > I > generally disagree... > > I think Christophe said it best: > > "Imagine you have two ways to reach the top of a mountain, a quick and > comfortable > cable car for 10 dollars and 15 minutes, or a long, winding mountain > pathway, free, but a > rough lengthy walk" (which would you choose) > > Anyway, I find it suprising that we are still having discussions > like this. > Everybody say it with me... > > WebDNA Has Been Rescued. > WebDNA is back on it's way Up. > > :-) > > I say, lets just finally realize this and focus on making cool stuff > with > it. > > Donovan (getting back to late night WebDNA programming on a > Saturday night) > > > > > > > > > -- > Donovan D. Brooke PH/FAX: 1 (608) 291-2024 > ---------------------------------------------- > VP > WebDNA Software Corporation > 16192 Coastal Highway > Lewes, DE 19958 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list
. > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ Robert Minor Director of Internet Services ------------------------------------------------------------ Cybermill Communications http://www.cybermill.com http://www.merchantmaker.com Providing Ecommerce and interactive website development and hosting services on Macintosh, Windows NT, *nix, and AS/400. Complete ddos proof hosting solutions and network services.
Associated Messages, from the most recent to the oldest:
I think what your really interested in, is to code the best way in both languages. (even here you will get arguments as to what is right) Also it gets complicated you can't just say I coded this simple example and that is why we are better. There are issues, like the use of frameworks etc. not including depth of programmers and how quickly someone can take over your work, if your not around to continue updates or they just want to be able to replace you quickly should you disappear or just not work well with them or they with you. We have taken over php code that is not very object oriented, its just one long line of if-thens creating what is called Spaghetti code and had to recode the whole smear. Other times the programmers well documented their methodology and it was easier to understand, but this is an issue with any language you choose. That is unless you're just trying to convince your customer and you're not really looking to do an in depth study of the pros and cons. In my mind the advantage that webdna has is that someone who isn't a programmer can do some complex things. They can build a quick database and deploy an application accessing that data. Is the data format right? Is it scalable? Well sometimes these question are less important when your trying to find out if something is even of interest and taking the time to build it for use by a million users a second is just not warranted. If you were building a brand new "ebay" I would say webdna is not your language, but if your going to build a quick interface into your backend support system or create one from scratch then it may be the way to go. Then it may work perfectly well until you've proven its worth and then some. At that point you can program it for greater use using your system as a basis for how the new program will function. On Oct 12, 2008, at 3:55 PM, Will Starck wrote: > If anyone has any code snippet examples of a few lines of code in > WebDNA vs. > something much longer that would be required in PHP code you post them > please? > > Thanks, > > > Will Starck > ------------------- > NovaDerm Skincare Science > http://www.novaderm.com > wjs@novaderm.com > 817-717-7377 > > > > -----Original Message----- > From: Donovan Brooke [mailto:dbrooke@webdna.us] > Sent: Sunday, October 12, 2008 12:29 AM > To: talk@webdna.us > Subject: Re: [WebDNA] a major shift in strategy? > > Meyers, David E. wrote: > >> Strategy? Think marketing and business not tech. >> >> I have been a WebDNA fan since I bought the original plug-in for 5 >> grand > over ten years ago. I have no where near the programming and "tech" > ability > of those that I see commenting on the Talk Lists - in fact, half of > the talk > list comments are greek to me. I continue to contract out to some true > WebDNA experts that have been with the software for years. I will > share the > observations that I shared with Smith Micro - who I feel we all agree > mismanaged and had little care for supporting WebDNA. >> >> As stated by Olin - Creating, managing, extending, modifying,? >> searching > and editing databases is about as easy as it gets. Bottom line - it > is VERY > simple and VERY powerful. Hell, I'm a designer and I have managed to > create > some pretty powerful solutions (even without the support of my > contacted > friends). >> >> In my graduate schools days, I had a genius of a professor who was > extremely successful (and quite wealthy) - he did nt have to teach, > rather > he chose to do so - he pointed out to students that companies and > products > will exist by falling into one of the following categories - They > will: >> >> Fail. (or) >> Survive. (or) >> Thrive. >> >> WebDNA has survived. >> >> I have shared this rather controversial position before privately, >> but > this time I throw it to the public forum and let you guys think > about it. >> >> WebDNA will never thrive as long as Php and MySQL is available for >> free > -snip > > > > Hi David, > I don't know if you realize it, but you made the case of exactly why > WebDNA > will > thrive, then you go on to say it won't. ;-) > > This subject, of course, has been the longest debate of the list to > date... > but the fact > is that we've pretty much nullified the "PHP is free" argument. A PHP > solution, in my opinion > will always cost more than a webdna solution.. especially now. The > cost of > WebDNA is > trivial at this point when you consider everything. PHP is free? > Hmmm, tell > that > to programmer that you are paying. Tell that to the database > company, or the > "solution" that you choose to use with it. Labor cost for a > developer, or > the > time it takes to "build stuff" drowns any perceived intial cost of the > product... > especially now. > > So, though there will always be plusses and minuses of different > solutions, > I > generally disagree... > > I think Christophe said it best: > > "Imagine you have two ways to reach the top of a mountain, a quick and > comfortable > cable car for 10 dollars and 15 minutes, or a long, winding mountain > pathway, free, but a > rough lengthy walk" (which would you choose) > > Anyway, I find it suprising that we are still having discussions > like this. > Everybody say it with me... > > WebDNA Has Been Rescued. > WebDNA is back on it's way Up. > > :-) > > I say, lets just finally realize this and focus on making cool stuff > with > it. > > Donovan (getting back to late night WebDNA programming on a > Saturday night) > > > > > > > > > -- > Donovan D. Brooke PH/FAX: 1 (608) 291-2024 > ---------------------------------------------- > VP > WebDNA Software Corporation > 16192 Coastal Highway > Lewes, DE 19958 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ > > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > old archives: http://dev.webdna.us/TalkListArchive/ Robert Minor Director of Internet Services ------------------------------------------------------------ Cybermill Communications http://www.cybermill.com http://www.merchantmaker.com Providing Ecommerce and interactive website development and hosting services on Macintosh, Windows NT, *nix, and AS/400. Complete ddos proof hosting solutions and network services.
Bob Minor
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Nested vs conditional (1997)
Can WebDNA do this? (2000)
PCS Customer submissions ? (1997)
[WebDNA] An actual attempt to get WebDNA and MAMP Pro to work - (2018)
[SHOWIF AND/OR] (1997)
Custom WebCat Prefs ... (1997)
2nd WebCatalog2 Feature Request (1996)
Bug In Admin Templates (2003)
Creating 404 Not Found pages (1999)
form data submission gets truncated (1997)
Help name our technology! (1997)
Tea Room trouble (1997)
include bug????? (1997)
cart converting to scientific notation format (2001)
carriage returns in data (1997)
For those of you not on the WebCatalog Beta... (1997)
Sku numbers (1997)
Replace context problem ... and answers (1997)
upgrading (1997)
WebDNA Writer Needed (1997)