Re: Here we go again...
This WebDNA talk-list message is from 2006
It keeps the original formatting.
numero = 66805
interpreted = N
texte = Pricing is going up...?-----Original Message-----From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf OfKenneth GromeSent: Thursday, April 06, 2006 8:26 AMTo: WebDNA TalkSubject: Re: Here we go again...Hi Bess,It's $20 per hour now.=20Sincerely,=20Kenneth Grome=20owner@kengrome.comkengrome@gmail.comwww.kengrome.comOn Wed, 5 Apr 2006 11:29:11 -0700, Bess Ho wrote:> Kenneth,>=20> What is the hourly charge for your php programmers? I will consider=20> this service for my personal use if it is reasonable.>=20> I want to build something for myself but I don't have the time to do =so.>=20> Bess>=20> -----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...>=20>=20>> Performance really comes down to how things>> are structured. Code for scale and I don't see=20>> any limitations with webdna.>=20> This assumes that it's practical or possible to "code for scale" in=20> webdna all the time. But this is not always possible ...>=20> In the example I just gave a day or so ago it was practically=20> impossible to "code for scale". Maybe you have not personally=20> experienced this type of situation and that's why you don't see any=20> limitations in webdna, but I have seen this situation -- more than=20> once -- and it's not a fun situation to be in when you love webdna=20> and want to use it for everything.>=20> In my recent example the data came from another source -- a source=20> that uses FMPro as its original database. This is not some little=20> company either, it is the leader in its industry.>=20> To make this data work in webdna means exporting it as tab-delimited=20> text files, then using those resulting flat files -- and whatever=20> coding techniques are available in webdna -- to get the search=20> results required by the client. The problem is that the data is not=20> structured for efficient use of webdna (by any stretch of the=20> imagination) so webdna is pathetically slow when doing the kind of=20> searches the client requires.=20>=20> As the web developer on this project, I did not have authorization to=20> go in and reformat these multi-megabyte data files in order to "make=20> them work" with webdna. This would have taken 10-20 times as long as=20> trying another software. Besides, I was not convinced that webdna=20> would perform as well as MySQL even if we did go in and reformat the=20> databases to optimize them for webdna -- because I've seen slow=20> performance in similar situations before when using webdna on such=20> large data sets (without nested searches) -- and I didn't want the=20> client to have to pay for all that labor only to find that webdna=20> still couldn't handle the task.>=20> So instead of "coding or scale" which would have meant restructuring=20> the database files that we exported from FMPro, I had my put=20> everything we had into PHP/MySQL. It took him less than 10 hours to=20> do this (at $1.20 an hour for his labor) ... so for about twelve=20> bucks I was able to see that PHP/MySQL was far superior to webdna in=20> this situation. This saved the client hundreds if not thousands of=20> dollars over using a webdna solution.>=20> The bottom line here is that webdna has serious limitations that make=20> it a poor substitute for MySQL in certain situations. In these=20> situations MySQL and other truly relational data systems are far=20> better suited to the tasks at hand.>=20> Sincerely,=20> Kenneth Grome=20>=20> owner@kengrome.com> kengrome@gmail.com> www.kengrome.com>=20>=20>=20>=20> -------------------------------------------------------------> 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=20> > Web Archive of this list is at: http://webdna.smithmicro.com/>=20> -------------------------------------------------------------> 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=20> > Web Archive of this list is at: http://webdna.smithmicro.com/>=20>=20-------------------------------------------------------------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:
Pricing is going up...?-----Original Message-----From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf OfKenneth GromeSent: Thursday, April 06, 2006 8:26 AMTo: WebDNA TalkSubject: Re: Here we go again...Hi Bess,It's $20 per hour now.=20Sincerely,=20Kenneth Grome=20owner@kengrome.comkengrome@gmail.comwww.kengrome.comOn Wed, 5 Apr 2006 11:29:11 -0700, Bess Ho wrote:> Kenneth,>=20> What is the hourly charge for your php programmers? I will consider=20> this service for my personal use if it is reasonable.>=20> I want to build something for myself but I don't have the time to do =so.>=20> Bess>=20> -----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...>=20>=20>> Performance really comes down to how things>> are structured. Code for scale and I don't see=20>> any limitations with webdna.>=20> This assumes that it's practical or possible to "code for scale" in=20> webdna all the time. But this is not always possible ...>=20> In the example I just gave a day or so ago it was practically=20> impossible to "code for scale". Maybe you have not personally=20> experienced this type of situation and that's why you don't see any=20> limitations in webdna, but I have seen this situation -- more than=20> once -- and it's not a fun situation to be in when you love webdna=20> and want to use it for everything.>=20> In my recent example the data came from another source -- a source=20> that uses FMPro as its original database. This is not some little=20> company either, it is the leader in its industry.>=20> To make this data work in webdna means exporting it as tab-delimited=20> text files, then using those resulting flat files -- and whatever=20> coding techniques are available in webdna -- to get the search=20> results required by the client. The problem is that the data is not=20> structured for efficient use of webdna (by any stretch of the=20> imagination) so webdna is pathetically slow when doing the kind of=20> searches the client requires.=20>=20> As the web developer on this project, I did not have authorization to=20> go in and reformat these multi-megabyte data files in order to "make=20> them work" with webdna. This would have taken 10-20 times as long as=20> trying another software. Besides, I was not convinced that webdna=20> would perform as well as MySQL even if we did go in and reformat the=20> databases to optimize them for webdna -- because I've seen slow=20> performance in similar situations before when using webdna on such=20> large data sets (without nested searches) -- and I didn't want the=20> client to have to pay for all that labor only to find that webdna=20> still couldn't handle the task.>=20> So instead of "coding or scale" which would have meant restructuring=20> the database files that we exported from FMPro, I had my put=20> everything we had into PHP/MySQL. It took him less than 10 hours to=20> do this (at $1.20 an hour for his labor) ... so for about twelve=20> bucks I was able to see that PHP/MySQL was far superior to webdna in=20> this situation. This saved the client hundreds if not thousands of=20> dollars over using a webdna solution.>=20> The bottom line here is that webdna has serious limitations that make=20> it a poor substitute for MySQL in certain situations. In these=20> situations MySQL and other truly relational data systems are far=20> better suited to the tasks at hand.>=20> Sincerely,=20> Kenneth Grome=20>=20> owner@kengrome.com> kengrome@gmail.com> www.kengrome.com>=20>=20>=20>=20> -------------------------------------------------------------> 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=20> > Web Archive of this list is at: http://webdna.smithmicro.com/>=20> -------------------------------------------------------------> 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=20> > Web Archive of this list is at: http://webdna.smithmicro.com/>=20>=20-------------------------------------------------------------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/
"Bess Ho"
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:
Server Creation - vendors (2005)
NT considerations (1997)
Re1000001: Setting up shop (1997)
no word on MacAuthorize... (1997)
Weird [date] and [time] problems. (2003)
WebCat2b15MacPlugIn - [authenticate] not [protect] (1997)
off topic, converting mail (1998)
Re:Help name our technology! (1997)
Help with getting rpm file (2002)
lazy programming (2000)
[OT] XML Primer (2004)
required fields??? (2000)
[WebDNA] IIS 7.5 (2015)
[WebDNA] Integrating a HTML Parser (2013)
Creating main- and sub-category search (1997)
Banner DNA (1997)
Database Changes (2000)
[OT] Linux -> Winderz (2005)
[TaxableTotal] - not working with AOL and IE (1997)
shipcost (1997)