[WebDNA] a major shift in strategy?

This WebDNA talk-list message is from

2008


It keeps the original formatting.
numero = 101095
interpreted = N
texte = Aloha all, I love WebDNA. Why? Creating, managing, extending, modifying, searching and editing databases is about as easy as it gets. It's so easy that most projects can do just fine without any database administrator. It's not the scripting language. The scripting language is decent but definitely not as feature rich or community supported as other options. I don't think I am alone. I think there are tons of developers that are interested in using something even easier than mysql than there are developers that will switch to a relatively obscure language. Plus competing with the open source alternatives is near suicide. Every day you'll see cool stuff about the other langs. For instance, host a 5 million hits per day site for free in Google's cloud with the potential to scale your app to any size (python for now with other langs to follow); handle 25,000 connections at any given time with only 256 threads (resin running php/java); etc. So, anyone got thoughts on the following strategy: 1. The pitch could be to dump your database admin. Not needed. Save the $100K+ per year for trips to Hawaii for the rest of the team. The system empowers developers with virtually no database skills to get up to speed pretty quickly. 2. Have a web based interface to completely manage databases that blows phpmyadmin way out of the water. The interface should also have a query builder so folks getting started and build queries visually. This tool creates, manages, edits, deletes, merges, etc. databases. Have a sandbox folks can play with online. 3. Create a version of the software that essentially runs the dbserver and is callable via common languages (php, python, java, ruby, .net, etc.) in ways that is much easier than traditional calls to a sql based server. Who cares if they buy the system for the db and not use the rest of the scripting language! This strategy essentially positions webdna as an alternative, a simple easy to use alternative, to mysql. The market potential is then massive. Marketing could have fun with the PC v Mac parodies (mysql v webdna). I am not confident continuing on the path of making webdna better could result in marketplace success. Fixing bugs and adding features supports the small group still using the product and in my opinion without marketing genius and more lady luck than most of us have ever been graced with, the masses will not come over. However, who wouldn't want to try out a scrappy piece of software that promises to empower the developers to wrestle the db themselves! Oh, one last thought. You should be able to get a team together using odesk.com pretty quickly. I've used a few contractors found on the site that had tons of experience with ANSI C code. I'm happy to write/help write a completely modern db admin. Laters, Olin Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] a major shift in strategy? (Tim Benson 2008)
  2. Re: [WebDNA] a major shift in strategy? (Govinda 2008)
  3. Re: [WebDNA] a major shift in strategy? ("stephen" 2008)
  4. Re: [WebDNA] a major shift in strategy? (Thierry Almy 2008)
  5. Re: [WebDNA] a major shift in strategy? ("Psi Prime, Matthew A Perosi " 2008)
  6. Re: [WebDNA] a major shift in strategy? (Donovan Brooke 2008)
  7. Re: [WebDNA] a major shift in strategy? (Stuart Tremain 2008)
  8. Re: [WebDNA] a major shift in strategy? (Jesse Proudman 2008)
  9. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  10. RE: [WebDNA] a major shift in strategy? ("Olin Lagon" 2008)
  11. Re: [WebDNA] a major shift in strategy? (christophe.billiottet@webdna.us 2008)
  12. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  13. Re: [WebDNA] a major shift in strategy? (Stuart Tremain 2008)
  14. RE: [WebDNA] a major shift in strategy? ("Meyers, David E." 2008)
  15. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  16. Re: [WebDNA] a major shift in strategy? (Terry Wilson 2008)
  17. Re: [WebDNA] a major shift in strategy? (Bob Minor 2008)
  18. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  19. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  20. Re: [WebDNA] a major shift in strategy? (Stuart Tremain 2008)
  21. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  22. Re: [WebDNA] a major shift in strategy? ("Dan Strong" 2008)
  23. Re: [WebDNA] a major shift in strategy? (Bob Minor 2008)
  24. Re: [WebDNA] a major shift in strategy? (Terry Wilson 2008)
  25. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  26. Re: [WebDNA] a major shift in strategy? (Patrick McCormick 2008)
  27. RE: [WebDNA] a major shift in strategy? ("Terry Nair" 2008)
  28. Re: [WebDNA] a major shift in strategy? (Patrick McCormick 2008)
  29. Re: [WebDNA] a major shift in strategy? (christophe.billiottet@webdna.us 2008)
  30. Re: [WebDNA] a major shift in strategy? (Donovan Brooke 2008)
  31. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  32. Re: [WebDNA] a major shift in strategy? (Bob Minor 2008)
  33. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  34. Re: [WebDNA] a major shift in strategy? (Donovan Brooke 2008)
  35. RE: [WebDNA] a major shift in strategy? ("Meyers, David E." 2008)
  36. Re: [WebDNA] a major shift in strategy? (Donovan Brooke 2008)
  37. RE: [WebDNA] a major shift in strategy? ("Olin Lagon" 2008)
  38. Re: [WebDNA] a major shift in strategy? (Colin Sidwell 2008)
  39. Re: [WebDNA] a major shift in strategy? (christophe.billiottet@webdna.us 2008)
  40. Re: [WebDNA] a major shift in strategy? (Colin Sidwell 2008)
  41. Re: [WebDNA] a major shift in strategy? (Kenneth Grome 2008)
  42. [WebDNA] a major shift in strategy? ("Olin Lagon" 2008)
Aloha all, I love WebDNA. Why? Creating, managing, extending, modifying, searching and editing databases is about as easy as it gets. It's so easy that most projects can do just fine without any database administrator. It's not the scripting language. The scripting language is decent but definitely not as feature rich or community supported as other options. I don't think I am alone. I think there are tons of developers that are interested in using something even easier than mysql than there are developers that will switch to a relatively obscure language. Plus competing with the open source alternatives is near suicide. Every day you'll see cool stuff about the other langs. For instance, host a 5 million hits per day site for free in Google's cloud with the potential to scale your app to any size (python for now with other langs to follow); handle 25,000 connections at any given time with only 256 threads (resin running php/java); etc. So, anyone got thoughts on the following strategy: 1. The pitch could be to dump your database admin. Not needed. Save the $100K+ per year for trips to Hawaii for the rest of the team. The system empowers developers with virtually no database skills to get up to speed pretty quickly. 2. Have a web based interface to completely manage databases that blows phpmyadmin way out of the water. The interface should also have a query builder so folks getting started and build queries visually. This tool creates, manages, edits, deletes, merges, etc. databases. Have a sandbox folks can play with online. 3. Create a version of the software that essentially runs the dbserver and is callable via common languages (php, python, java, ruby, .net, etc.) in ways that is much easier than traditional calls to a sql based server. Who cares if they buy the system for the db and not use the rest of the scripting language! This strategy essentially positions webdna as an alternative, a simple easy to use alternative, to mysql. The market potential is then massive. Marketing could have fun with the PC v Mac parodies (mysql v webdna). I am not confident continuing on the path of making webdna better could result in marketplace success. Fixing bugs and adding features supports the small group still using the product and in my opinion without marketing genius and more lady luck than most of us have ever been graced with, the masses will not come over. However, who wouldn't want to try out a scrappy piece of software that promises to empower the developers to wrestle the db themselves! Oh, one last thought. You should be able to get a team together using odesk.com pretty quickly. I've used a few contractors found on the site that had tons of experience with ANSI C code. I'm happy to write/help write a completely modern db admin. Laters, Olin "Olin Lagon"

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:

Shipcost lookup? (1997) Admin Edit prob. (1997) Netscape v. IE (1997) Possible Bug in 2.0b15.acgi (1997) Getting Started (2003) SKU (1997) Mass Mail (2000) all records returned. (1997) Initiating NewCart (1997) 2nd WebCatalog2 Feature Request (1996) Multiple prices (1997) Req: Row DB feature (2004) keep W* in front applescript? (1998) TCPConnect misbehavin' for me. (2000) WebCat Admin access w/ClearlyHome p.i. (1997) WCS Newbie question (1997) New command suggestion (1997) Thanks ! (1997) Frames and WebCat (1997) redirect with frames (1997)