Re: Here we go again...
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66797
interpreted = N
texte = Hi Bess, It's $20 per hour now. Sincerely, Kenneth Grome owner@kengrome.com kengrome@gmail.com www.kengrome.com On Wed, 5 Apr 2006 11:29:11 -0700, Bess Ho wrote: > Kenneth, > > What is the hourly charge for your php programmers? I will consider > this service for my personal use if it is reasonable. > > I want to build something for myself but I don't have the time to do so. > > Bess > > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Kenneth Grome > Sent: Saturday, April 01, 2006 7:41 PM > To: WebDNA Talk > Subject: Re: Here we go again... > > >> Performance really comes down to how things >> are structured. Code for scale and I don't see >> any limitations with webdna. > > This assumes that it's practical or possible to "code for scale" in > webdna all the time. But this is not always possible ... > > In the example I just gave a day or so ago it was practically > impossible to "code for scale". Maybe you have not personally > experienced this type of situation and that's why you don't see any > limitations in webdna, but I have seen this situation -- more than > once -- and it's not a fun situation to be in when you love webdna > and want to use it for everything. > > In my recent example the data came from another source -- a source > that uses FMPro as its original database. This is not some little > company either, it is the leader in its industry. > > To make this data work in webdna means exporting it as tab-delimited > text files, then using those resulting flat files -- and whatever > coding techniques are available in webdna -- to get the search > results required by the client. The problem is that the data is not > structured for efficient use of webdna (by any stretch of the > imagination) so webdna is pathetically slow when doing the kind of > searches the client requires. > > As the web developer on this project, I did not have authorization to > go in and reformat these multi-megabyte data files in order to "make > them work" with webdna. This would have taken 10-20 times as long as > trying another software. Besides, I was not convinced that webdna > would perform as well as MySQL even if we did go in and reformat the > databases to optimize them for webdna -- because I've seen slow > performance in similar situations before when using webdna on such > large data sets (without nested searches) -- and I didn't want the > client to have to pay for all that labor only to find that webdna > still couldn't handle the task. > > So instead of "coding or scale" which would have meant restructuring > the database files that we exported from FMPro, I had my put > everything we had into PHP/MySQL. It took him less than 10 hours to > do this (at $1.20 an hour for his labor) ... so for about twelve > bucks I was able to see that PHP/MySQL was far superior to webdna in > this situation. This saved the client hundreds if not thousands of > dollars over using a webdna solution. > > The bottom line here is that webdna has serious limitations that make > it a poor substitute for MySQL in certain situations. In these > situations MySQL and other truly relational data systems are far > better suited to the tasks at hand. > > Sincerely, > Kenneth Grome > > owner@kengrome.com > kengrome@gmail.com > www.kengrome.com > > > > > ------------------------------------------------------------- > 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/ > > ------------------------------------------------------------- > 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/ > > ------------------------------------------------------------- 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:
Hi Bess, It's $20 per hour now. Sincerely, Kenneth Grome owner@kengrome.com kengrome@gmail.com www.kengrome.com On Wed, 5 Apr 2006 11:29:11 -0700, Bess Ho wrote: > Kenneth, > > What is the hourly charge for your php programmers? I will consider > this service for my personal use if it is reasonable. > > I want to build something for myself but I don't have the time to do so. > > Bess > > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Kenneth Grome > Sent: Saturday, April 01, 2006 7:41 PM > To: WebDNA Talk > Subject: Re: Here we go again... > > >> Performance really comes down to how things >> are structured. Code for scale and I don't see >> any limitations with webdna. > > This assumes that it's practical or possible to "code for scale" in > webdna all the time. But this is not always possible ... > > In the example I just gave a day or so ago it was practically > impossible to "code for scale". Maybe you have not personally > experienced this type of situation and that's why you don't see any > limitations in webdna, but I have seen this situation -- more than > once -- and it's not a fun situation to be in when you love webdna > and want to use it for everything. > > In my recent example the data came from another source -- a source > that uses FMPro as its original database. This is not some little > company either, it is the leader in its industry. > > To make this data work in webdna means exporting it as tab-delimited > text files, then using those resulting flat files -- and whatever > coding techniques are available in webdna -- to get the search > results required by the client. The problem is that the data is not > structured for efficient use of webdna (by any stretch of the > imagination) so webdna is pathetically slow when doing the kind of > searches the client requires. > > As the web developer on this project, I did not have authorization to > go in and reformat these multi-megabyte data files in order to "make > them work" with webdna. This would have taken 10-20 times as long as > trying another software. Besides, I was not convinced that webdna > would perform as well as MySQL even if we did go in and reformat the > databases to optimize them for webdna -- because I've seen slow > performance in similar situations before when using webdna on such > large data sets (without nested searches) -- and I didn't want the > client to have to pay for all that labor only to find that webdna > still couldn't handle the task. > > So instead of "coding or scale" which would have meant restructuring > the database files that we exported from FMPro, I had my put > everything we had into PHP/MySQL. It took him less than 10 hours to > do this (at $1.20 an hour for his labor) ... so for about twelve > bucks I was able to see that PHP/MySQL was far superior to webdna in > this situation. This saved the client hundreds if not thousands of > dollars over using a webdna solution. > > The bottom line here is that webdna has serious limitations that make > it a poor substitute for MySQL in certain situations. In these > situations MySQL and other truly relational data systems are far > better suited to the tasks at hand. > > Sincerely, > Kenneth Grome > > owner@kengrome.com > kengrome@gmail.com > www.kengrome.com > > > > > ------------------------------------------------------------- > 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/ > > ------------------------------------------------------------- > 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/ > > ------------------------------------------------------------- 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/
Kenneth Grome
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:
RE: ShowNext Command (1997)
Strange Crash (1998)
[WebDNA] fastcgi 7+ & [cart]? (2010)
Uh...can someone help me out with the b10? (1997)
[sendmail] and [formvariables] (1997)
no global [username] or [password] displayed ... (1997)
About WebCatalog and iTools 7 (2003)
Re:no [search] with NT (1997)
[WebDNA] Brian Harrington (2019)
Moment of Thanks (1997)
Problems reading files created by WC (1997)
Error:Too many nested [xxx] contexts (1997)
trouble updating records in database (1998)
Download URL & access on the fly ? (1997)
RePost: NAT and the CART (1999)
Errata: WCS Newbie question (1997)
[WebDNA] why this error when using [shownext] with a [table]? (2009)
Math inside [showif] (1998)
Kaaaaahhhhhhhnnnnnnn! (1997)
japanese characters (1997)