Re: WebDNA version?
This WebDNA talk-list message is from 2007
It keeps the original formatting.
numero = 68962
interpreted = N
texte = On 5/4/07 12:48 PM, "Donovan Brooke"
wrote: > Clint has recently posted quite a lot of examples of probably my biggest pet > peeve about, what seems to be synonymous with, main-stream technologies. More > busy work! It's kinda like the PC vs. Mac thing... I guarantee you that if > you have two system administrators, both who manage a multi-server > environment, the PC admin will have much more work to do on a time basis than > the Mac admin. In fact the Mac Admin may very well have to fight for his/her > validity in a department. ;-) ...Same with PHP vs. WebDNA, Constant security > patches, paid upgrades, make PHP more time intensive, thus losing the energy > (costs) to results value. I don't read your comments as any type of personal attack, but I still want to respond with some reasoning. I'm a Mac guy and always have been. I agree with the simplicity. I applaud Apple for bringing us the Intel machines that let me run OS X full-time while running Window$ XP in a window for cross-platform development testing. I come from a design background, but I migrated into web development and system administration with lots of trial-by-fire training. Our company has been developing websites and web-based applications since 1998. We originally used Filemaker Pro for some limited database-type stuff since it was very Mac-friendly. We had our own WebSTAR 2 server to host on, so we had some flexibility there. Then, we moved to WebDNA 3 when our local hosting partner suggested it as another more-powerful, Mac-friendly product. We had moved on to WebSTAR 3 by this time. We eventually moved to WebSTAR 5 since it ran under OS X. There were several bulletin boards an other add-on products that required CGI or PHP to run. It became an enormous P.I.T.A. to try to get this stuff up and going with WebSTAR, so we bought an Xserve and put iTools on it to host with Apache with providing more flexibility than Apple's Apache GUI. Up until last fall, we were developing on WebDNA exclusively. Our city may have had the highest cluster of WebDNA developers at one time, since our hosting partner had recruited other developers in town to adopt WebDNA also. We had 3 people in-house, and I know of at least 4 other people in the city that were using it. As requests for additional add-on software increased, it was becoming almost impossible to integrate with WebDNA. While the RAM-based database system was fast, we found it to have some stability issues. There were several times throughout our WebDNA history that databases were truncated when WebSTAR or Apache took a big crap. This has happened as recently as February when we lost over 100k records during a server crash. Last Fall, we made the decision to move to PHP/MySQL based on several factors: 1. We hate Microsoft and didn't want to use .NET. 2. PHP has thousands of developers worldwide that can freelance or offer free code. 3. We wanted the reliability of disk-based databases. 4. There are countless books, websites, blogs, and usergroups dedicated to PHP. 5. Smith Micro completely dropped the ball with WebDNA with their silence and lack of support. This was the straw that broke the camels back. I have built some extremely feature-rich and complex applications with WebDNA, and I haven't seen any other server-side language that can compete with it's simplicity. With all this being said, I have no regrets in moving to PHP/MySQL. For us, it's been a natural progression. The main-stream nature of PHP has been very beneficial when learning. ------------------------------------------------------------- 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:
On 5/4/07 12:48 PM, "Donovan Brooke" wrote: > Clint has recently posted quite a lot of examples of probably my biggest pet > peeve about, what seems to be synonymous with, main-stream technologies. More > busy work! It's kinda like the PC vs. Mac thing... I guarantee you that if > you have two system administrators, both who manage a multi-server > environment, the PC admin will have much more work to do on a time basis than > the Mac admin. In fact the Mac Admin may very well have to fight for his/her > validity in a department. ;-) ...Same with PHP vs. WebDNA, Constant security > patches, paid upgrades, make PHP more time intensive, thus losing the energy > (costs) to results value. I don't read your comments as any type of personal attack, but I still want to respond with some reasoning. I'm a Mac guy and always have been. I agree with the simplicity. I applaud Apple for bringing us the Intel machines that let me run OS X full-time while running Window$ XP in a window for cross-platform development testing. I come from a design background, but I migrated into web development and system administration with lots of trial-by-fire training. Our company has been developing websites and web-based applications since 1998. We originally used Filemaker Pro for some limited database-type stuff since it was very Mac-friendly. We had our own WebSTAR 2 server to host on, so we had some flexibility there. Then, we moved to WebDNA 3 when our local hosting partner suggested it as another more-powerful, Mac-friendly product. We had moved on to WebSTAR 3 by this time. We eventually moved to WebSTAR 5 since it ran under OS X. There were several bulletin boards an other add-on products that required CGI or PHP to run. It became an enormous P.I.T.A. to try to get this stuff up and going with WebSTAR, so we bought an Xserve and put iTools on it to host with Apache with providing more flexibility than Apple's Apache GUI. Up until last fall, we were developing on WebDNA exclusively. Our city may have had the highest cluster of WebDNA developers at one time, since our hosting partner had recruited other developers in town to adopt WebDNA also. We had 3 people in-house, and I know of at least 4 other people in the city that were using it. As requests for additional add-on software increased, it was becoming almost impossible to integrate with WebDNA. While the RAM-based database system was fast, we found it to have some stability issues. There were several times throughout our WebDNA history that databases were truncated when WebSTAR or Apache took a big crap. This has happened as recently as February when we lost over 100k records during a server crash. Last Fall, we made the decision to move to PHP/MySQL based on several factors: 1. We hate Microsoft and didn't want to use .NET. 2. PHP has thousands of developers worldwide that can freelance or offer free code. 3. We wanted the reliability of disk-based databases. 4. There are countless books, websites, blogs, and usergroups dedicated to PHP. 5. Smith Micro completely dropped the ball with WebDNA with their silence and lack of support. This was the straw that broke the camels back. I have built some extremely feature-rich and complex applications with WebDNA, and I haven't seen any other server-side language that can compete with it's simplicity. With all this being said, I have no regrets in moving to PHP/MySQL. For us, it's been a natural progression. The main-stream nature of PHP has been very beneficial when learning. ------------------------------------------------------------- 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/
Clint Davis
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:
database visibility (2000)
[WebDNA] get vs post problems (2011)
Db design question (relational vs. flat?) (1998)
Admin Edit prob. (1997)
No Data Results (1997)
Re:trouble (1997)
WSDL Wizard (2003)
[quantity] within formulas (1997)
New Mac Public Beta Available (1997)
WebCatalog stalls (1998)
E-mailer error codes (1997)
Forms Search Questions (1997)
template cache problem (1998)
WCf2 and nested tags (1997)
Robots fill event log (1997)
all records returned. (1997)
Not really WebCat (1997)
Exclude by date - multiple (1997)
Execute Applescript (1997)
Help name our technology! (1997)