Re: [WebDNA] What does PHP(5) has, that Webdna hasn't

This WebDNA talk-list message is from

2009

It keeps the original formatting. numero = 102744
interpreted = N
texte = The number one reason is development time. I have spent hundreds of hours trying to duplicate simple functionality of WebDNA in PHP. I have a library of some functions and classes (including a shopping cart that I have about 300 hours in, and it still doesn't do everything as easily as WebDNA). I have spent easily three times as long on a PHP site than a WebDNA site. Code takes time to write and test. More code takes more time. The hard part has already been done in WebDNA, the functions are simple and easy to use. There are no huge libraries of functions and classes to do fancy things because there doesn't need to be. There is no huge collection of classes for connecting to a database and pulling out information... it's built in. The database administrator is built in. While we're on the subject of databases... It's text. Need to manually update a record while you're testing? Would you rather load up phpMyAdmin, do some command line SQL, or open the database in a text editor?To address the learning curve... If you know PHP, WebDNA is a breeze to learn. Most developers wirth their salt know multiple languages anyway, so learning a new one is a breeze. I learned the basics of WebDNA in two weeks.WebDNA programing is fast. You end up spending less time doing the same tasks. It's about efficiency.Lawrence Banahan wrote:> Hi All,>> I'm using Webdna for almost 7 years and don't what to change...> But it is impossible to find trainee that would accept to learn it...> I also have partners who would like us to pass the river and get to > php/MySql.> When I have a look at MySql it looks horrible to me, but is it more > powerfull than Webcatalog?> I know about http://webdna.us/page.dna?numero=37> But what other reason could I say to keep going on Webdna...>> Thank's for your Help>>> ---------------------------------------------------------> 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/>> Associated Messages, from the most recent to the oldest:

Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (Terry Wilson 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (Donovan Brooke 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (Lawrence Banahan 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (Frank Nordberg 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't ("Psi Prime, Matthew A Perosi " 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (Donovan Brooke 2009)
RE: [WebDNA] What does PHP(5) has, that Webdna hasn't ("Michael A. DeLorenzo" 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (Terry Wilson 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (christophe.billiottet@webdna.us 2009)
RE: [WebDNA] What does PHP(5) has, that Webdna hasn't ("Tana Adams" 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (Gil Poulsen 2009)
RE: [WebDNA] What does PHP(5) has, that Webdna hasn't ("Michael A. DeLorenzo" 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (christophe.billiottet@webdna.us 2009)
Re: [WebDNA] What does PHP(5) has, that Webdna hasn't (Matthew Bohne 2009)
[WebDNA] What does PHP(5) has, that Webdna hasn't (Lawrence Banahan 2009)

The number one reason is development time. I have spent hundreds of hours trying to duplicate simple functionality of WebDNA in PHP. I have a library of some functions and classes (including a shopping cart that I have about 300 hours in, and it still doesn't do everything as easily as WebDNA). I have spent easily three times as long on a PHP site than a WebDNA site. Code takes time to write and test. More code takes more time. The hard part has already been done in WebDNA, the functions are simple and easy to use. There are no huge libraries of functions and classes to do fancy things because there doesn't need to be. There is no huge collection of classes for connecting to a database and pulling out information... it's built in. The database administrator is built in. While we're on the subject of databases... It's text. Need to manually update a record while you're testing? Would you rather load up phpMyAdmin, do some command line SQL, or open the database in a text editor?To address the learning curve... If you know PHP, WebDNA is a breeze to learn. Most developers wirth their salt know multiple languages anyway, so learning a new one is a breeze. I learned the basics of WebDNA in two weeks.WebDNA programing is fast. You end up spending less time doing the same tasks. It's about efficiency.Lawrence Banahan wrote:> Hi All,>> I'm using Webdna for almost 7 years and don't what to change...> But it is impossible to find trainee that would accept to learn it...> I also have partners who would like us to pass the river and get to > php/MySql.> When I have a look at MySql it looks horrible to me, but is it more > powerfull than Webcatalog?> I know about http://webdna.us/page.dna?numero=37> But what other reason could I say to keep going on Webdna...>> Thank's for your Help>>> ---------------------------------------------------------> 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/>> Matthew Bohne

DOWNLOAD WEBDNA NOW!

Re: [WebDNA] What does PHP(5) has, that Webdna hasn't

2009

Top Articles:

Related Readings: