Re: Here we go again...

This WebDNA talk-list message is from

2006


It keeps the original formatting.
numero = 66811
interpreted = N
texte = No, that's a "going out of business" price. Sincerely, Kenneth Grome owner@kengrome.com kengrome@gmail.com www.kengrome.com On Thu, 6 Apr 2006 11:21:46 -0700, Bess Ho wrote: > Pricing is going up...? > > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Kenneth Grome > Sent: Thursday, April 06, 2006 8:26 AM > To: WebDNA Talk > Subject: Re: Here we go again... > > > 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/ > > ------------------------------------------------------------- > 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:

    
  1. Re: Here we go again... ( "Bess Ho" 2006)
  2. Re: Here we go again... ( Kenneth Grome 2006)
  3. Re: Here we go again... ( "sal danna" 2006)
  4. Re: Here we go again... ( "Bess Ho" 2006)
  5. Re: Here we go again... ( Kenneth Grome 2006)
  6. Re: Here we go again... ( "Bess Ho" 2006)
  7. Re: Here we go again...WebDNA - SQL- Clustering ( Kenneth Grome 2006)
  8. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  9. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  10. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  11. Re: Here we go again...WebDNA - SQL- Clustering ( "Bess Ho" 2006)
  12. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  13. Re: Here we go again...WebDNA - SQL- Stored Procedures ( Alex McCombie 2006)
  14. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  15. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  16. Re: Here we go again...WebDNA - SQL- Clustering ( Adam O'Connor 2006)
  17. Re: Here we go again...WebDNA - SQL- Clustering ( nitai@computeroil.com 2006)
  18. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  19. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  20. Re: Here we go again...WebDNA - SQL- Stored Procedures ( Adam O'Connor 2006)
  21. Re: Here we go again...WebDNA - SQL- Clustering ( nitai@computeroil.com 2006)
  22. Re: Here we go again... ( nitai@computeroil.com 2006)
  23. Re: Here we go again... ( Kenneth Grome 2006)
  24. Re: Here we go again...WebDNA - SQL- Clustering ( Donovan Brooke 2006)
  25. Re: Here we go again... ( Donovan Brooke 2006)
  26. Re: Here we go again...WebDNA - SQL- Clustering ( Alex McCombie 2006)
  27. Re: Here we go again... ( Kenneth Grome 2006)
  28. Re: Here we go again...WebDNA - SQL- Clustering ( Bob Minor 2006)
  29. Re: Here we go again... ( "Bess Ho" 2006)
  30. Re: Here we go again... ( "Bess Ho" 2006)
  31. Re: Here we go again... ( Donovan Brooke 2006)
  32. Re: Here we go again...WebDNA - SQL- Clustering ( Stuart Tremain 2006)
  33. Re: Here we go again...WebDNA - SQL- Clustering ( Adam O'Connor 2006)
  34. Re: Here we go again... ( "Bess Ho" 2006)
  35. Re: Here we go again... ( Adam O'Connor 2006)
  36. Re: Here we go again... ( Adam O'Connor 2006)
  37. Re: Here we go again... ( Marc Thompson 2006)
  38. Re: Here we go again... ( "Bess Ho" 2006)
  39. Re: Here we go again... ( "Bess Ho" 2006)
  40. Re: Here we go again... ( Donovan Brooke 2006)
  41. Re: Here we go again... ( Adam O'Connor 2006)
  42. Re: Here we go again... ( "Bess Ho" 2006)
  43. Re: Here we go again... ( "Bess Ho" 2006)
  44. Re: Here we go again... ( Pat McCormick 2006)
  45. Re: Here we go again... ( Pat McCormick 2006)
  46. Re: Here we go again... ( "Bess Ho" 2006)
  47. Re: Here we go again... ( "Bess Ho" 2006)
  48. Re: Here we go again... ( Pat McCormick 2006)
  49. Re: Here we go again... ( Chris 2006)
  50. Re: Here we go again... ( Terry Wilson 2006)
  51. Re: Here we go again... ( Donovan Brooke 2006)
  52. Re: Here we go again... ( Donovan Brooke 2006)
  53. Re: Here we go again... ( Adam O'Connor 2006)
  54. Re: Here we go again... ( Kenneth Grome 2006)
  55. Re: Here we go again... ( Kenneth Grome 2006)
  56. Re: Here we go again... ( "Dan Strong" 2006)
  57. Re: Here we go again... ( "Dan Strong" 2006)
  58. Re: Here we go again... ( Donovan Brooke 2006)
  59. Re: Here we go again... ( Adam O'Connor 2006)
  60. Re: Here we go again... ( Donovan Brooke 2006)
  61. Re: Here we go again... ( Pat McCormick 2006)
  62. Re: Here we go again... was: DDEConnect not working ( Robie Blair 2006)
  63. Re: Here we go again... ( "Bess Ho" 2006)
  64. Re: Here we go again... ( Kenneth Grome 2006)
  65. Re: Here we go again... ( Terry Wilson 2006)
  66. Re: Here we go again... ( Larry Hewitt 2006)
  67. Re: Here we go again... ( Phil Herring 2006)
  68. Re: Here we go again... ( Jesse Proudman 2006)
  69. Re: Here we go again... ( Stuart Tremain 2006)
  70. Re: Here we go again... ( Jesse Proudman 2006)
  71. Re: Here we go again... ( Stuart Tremain 2006)
  72. Re: Here we go again... ( Jesse Proudman 2006)
  73. Re: Here we go again... ( "Dan Strong" 2006)
  74. Re: Here we go again... ( Jesse Proudman 2006)
  75. Re: Here we go again... ( "Dan Strong" 2006)
  76. Re: Here we go again... ( Stuart Tremain 2006)
  77. Re: Here we go again... was: DDEConnect not working ( Chris 2006)
  78. Re: Here we go again... was: DDEConnect not working ( Kenneth Grome 2006)
  79. Re: Here we go again... was: DDEConnect not working ( Chris 2006)
  80. Re: Here we go again... was: DDEConnect not working ( Kenneth Grome 2006)
  81. Re: Here we go again... was: DDEConnect not working ( Chris 2006)
  82. Re: Here we go again... was: DDEConnect not working ( Kenneth Grome 2006)
  83. Re: Here we go again... ( Donovan Brooke 2006)
  84. Re: Here we go again... was: DDEConnect not working ( Chris 2006)
  85. Re: Here we go again... ( Terry Wilson 2006)
  86. Re: Here we go again... was: DDEConnect not working ( Kenneth Grome 2006)
  87. Re: Here we go again... was: DDEConnect not working ( Stuart Tremain 2006)
  88. Re: Here we go again... was: DDEConnect not working ( "Dan Strong" 2006)
  89. Re: Here we go again... was: DDEConnect not working ( Stuart Tremain 2006)
  90. Re: Here we go again... was: DDEConnect not working ( Jay Van Vark 2006)
  91. Re: Here we go again... was: DDEConnect not working ( Stuart Tremain 2006)
  92. Re: Here we go again... was: DDEConnect not working ( "Bess Ho" 2006)
  93. Re: Here we go again... was: DDEConnect not working ( Gary Krockover 2006)
  94. Here we go again... was: DDEConnect not working ( "Dan Strong" 2006)
No, that's a "going out of business" price. Sincerely, Kenneth Grome owner@kengrome.com kengrome@gmail.com www.kengrome.com On Thu, 6 Apr 2006 11:21:46 -0700, Bess Ho wrote: > Pricing is going up...? > > -----Original Message----- > From: WebDNA Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of > Kenneth Grome > Sent: Thursday, April 06, 2006 8:26 AM > To: WebDNA Talk > Subject: Re: Here we go again... > > > 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/ > > ------------------------------------------------------------- > 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:

countdown to date (2003) Re:UPS, FEDEX TRACKING (1999) Country & Ship-to address & other fields ? (1997) Help w/ Duplicating The General Store 5 times. (1997) SSL data to/from webcatalog? (2000) error: Too many nested [xxx] contexts (1997) Listfiles (1998) instant cookies? (1999) webdna hideif / redirect - javascript disabled (2006) Rounding Prices? (2000) Shipcost lookup? (1997) [Sum] function? (1997) SetCookie / GetCookie Problem.... (2004) using showpage and showcart commands (1996) Emailer error 550? (1999) Web Developer Product Awards (1997) MacAuthorize Hub/Client and program linking (1997) WC Database Format (1997) Expected Behavior? (1999) SiteBuilder (2004)