Re: learning PHP
This WebDNA talk-list message is from 2007
It keeps the original formatting.
numero = 68309
interpreted = N
texte = I too am learning php - but will also launch a few sites this spring using WebDNA. Mainly due to having it, the sites will be pretty simple, and I get get them up and running pretty quickly (once I get the content for them). No need to spend a lot more time figuring out how to do them with php since they can be done in WebDNA much faster - and heck, I already have the license, so why not
Terry Wilson wrote: > Why learn PHP? Pretty much all the things Jesse mentioned. It scares > me to be making new sites in a language with no support, no upgrades, > and a shrinking user base. Other than that, I love working in WebDNA. > It doesn't take a Jeanne Dixon to see the future of WebDNA. > > Thanks everyone for their input on this. > > Terry > > >> Message-Id: <59A345FE-E40C-4B99-8ADD-C7ED4D1C73E4@blueboxdev.com> >> Content-Transfer-Encoding: 7bit >> From: Jesse Proudman >> Subject: Re: learning PHP >> Date: Thu, 11 Jan 2007 09:10:01 -0800 >> >> >> >>> I'm not sure what you need to do, but PHP is just another scripting >>> language. It might have a more robust set of commands and libraries >>> and more programmers who know the language (and maybe those are the >>> main deficiencies you are looking to overcome), but I'm not sure >>> what advantage you would find in it versus WebDNA purely as a >>> programming language. >> >> Any of number of reasons: Speed, Database connectivity, contexts that >> do what the documentation says, continued support, huge base of >> programmers? >> >>> I've not been impressed with PHP mostly because of the serious >>> security issues in the open source libraries. If you're going to >>> fix or deal with those, then you might as well code from scratch >>> with something that makes security more easy to implement and check. >> >> Any programming language has security holes (Especially WebDNA). The >> nice thing about OS languages is that those security issues can be >> addressed by the community quickly, instead of having un-patched bugs >> sitting around for years (Private software). >> >>> Most other tools will require that you move into SQL or something >>> similar for database access. Not fun because that is really a >>> second language to learn. >> >> You'd be surprised at how quickly one can learn SQL. >> >>> If you want to make a real change and use a set of tools that is >>> gaining traction rapidly and seems more robust that anything I've >>> seen in PHP, you should at least investigate Ruby on Rails (or at >>> least one of the PHP frameworks--I know nothing about these). I >>> know I've touted RoR on this list before, but it has many benefits >>> such as not requiring SQL for the trivial issues, it has conventions >>> throughout that make the common case ridiculously easy and the >>> unusal case easily handled. Plus Ruby is really fun to code in and >>> has true objects and idioms that are clever and easily remembered. >>> It will be a shift from scripted coding, but you get a better >>> product with the OOP conventions I think. >> >> I definitely agree here, but as a Ruby on Rails hosting company, I >> can tell you security is not a reason to switch to Rails. Rails has >> had it's fair number of security issues over the past year. But it >> is an amazing technology and one we've been proud to work with. The >> learning curve, especially with the introduction of version control >> and of capistrano to publish your site instead of FTP will make this >> a bit more of a burden to learn for a WebDNA user than something like >> PHP. >> >> >> -- >> >> Jesse Proudman, Blue Box Group, LLC > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I too am learning php - but will also launch a few sites this spring using WebDNA. Mainly due to having it, the sites will be pretty simple, and I get get them up and running pretty quickly (once I get the content for them). No need to spend a lot more time figuring out how to do them with php since they can be done in WebDNA much faster - and heck, I already have the license, so why not Terry Wilson wrote: > Why learn PHP? Pretty much all the things Jesse mentioned. It scares > me to be making new sites in a language with no support, no upgrades, > and a shrinking user base. Other than that, I love working in WebDNA. > It doesn't take a Jeanne Dixon to see the future of WebDNA. > > Thanks everyone for their input on this. > > Terry > > >> Message-Id: <59A345FE-E40C-4B99-8ADD-C7ED4D1C73E4@blueboxdev.com> >> Content-Transfer-Encoding: 7bit >> From: Jesse Proudman >> Subject: Re: learning PHP >> Date: Thu, 11 Jan 2007 09:10:01 -0800 >> >> >> >>> I'm not sure what you need to do, but PHP is just another scripting >>> language. It might have a more robust set of commands and libraries >>> and more programmers who know the language (and maybe those are the >>> main deficiencies you are looking to overcome), but I'm not sure >>> what advantage you would find in it versus WebDNA purely as a >>> programming language. >> >> Any of number of reasons: Speed, Database connectivity, contexts that >> do what the documentation says, continued support, huge base of >> programmers? >> >>> I've not been impressed with PHP mostly because of the serious >>> security issues in the open source libraries. If you're going to >>> fix or deal with those, then you might as well code from scratch >>> with something that makes security more easy to implement and check. >> >> Any programming language has security holes (Especially WebDNA). The >> nice thing about OS languages is that those security issues can be >> addressed by the community quickly, instead of having un-patched bugs >> sitting around for years (Private software). >> >>> Most other tools will require that you move into SQL or something >>> similar for database access. Not fun because that is really a >>> second language to learn. >> >> You'd be surprised at how quickly one can learn SQL. >> >>> If you want to make a real change and use a set of tools that is >>> gaining traction rapidly and seems more robust that anything I've >>> seen in PHP, you should at least investigate Ruby on Rails (or at >>> least one of the PHP frameworks--I know nothing about these). I >>> know I've touted RoR on this list before, but it has many benefits >>> such as not requiring SQL for the trivial issues, it has conventions >>> throughout that make the common case ridiculously easy and the >>> unusal case easily handled. Plus Ruby is really fun to code in and >>> has true objects and idioms that are clever and easily remembered. >>> It will be a shift from scripted coding, but you get a better >>> product with the OOP conventions I think. >> >> I definitely agree here, but as a Ruby on Rails hosting company, I >> can tell you security is not a reason to switch to Rails. Rails has >> had it's fair number of security issues over the past year. But it >> is an amazing technology and one we've been proud to work with. The >> learning curve, especially with the introduction of version control >> and of capistrano to publish your site instead of FTP will make this >> a bit more of a burden to learn for a WebDNA user than something like >> PHP. >> >> >> -- >> >> Jesse Proudman, Blue Box Group, LLC > ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Dale
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:
WebCat2 as a chat server? (1997)
Linux Install Question (2000)
PROBLEMS WITH PROTECT TAG (2004)
emailer (1997)
[OT] Who's got a cool link (2002)
Return records from another (1997)
WebCat2b13MacPlugIn - [shownext method=post] ??? (1997)
background (2001)
apostrophe in search item (1997)
A little syntax help (1997)
format and math on the fly (1998)
database freeze (1997)
Re:Virtual hosting and webcatNT (1997)
[protect] on NT? (1997)
E-mailer error codes (1997)
WAS Strange non-display problem, now BAD MATH (2002)
WebCatalog NT beta 18 now available (1997)
[WebDNA] Math Precision Preshmilson (2019)
WARNING: MacOS The installer is broken... (2000)
[ShowNext] feature in 2.0 (1997)