[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 easythat most projects can do just fine without any database administrator. It'snot the scripting language. The scripting language is decent but definitelynot as feature rich or community supported as other options. I don't think Iam alone. I think there are tons of developers that are interested in usingsomething even easier than mysql than there are developers that will switchto a relatively obscure language. Plus competing with the open sourcealternatives is near suicide. Every day you'll see cool stuff about theother langs. For instance, host a 5 million hits per day site for free inGoogle's cloud with the potential to scale your app to any size (python fornow with other langs to follow); handle 25,000 connections at any given timewith 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 systemempowers developers with virtually no database skills to get up to speedpretty quickly.2. Have a web based interface to completely manage databases that blowsphpmyadmin way out of the water. The interface should also have a querybuilder so folks getting started and build queries visually. This toolcreates, manages, edits, deletes, merges, etc. databases. Have a sandboxfolks can play with online.3. Create a version of the software that essentially runs the dbserver andis callable via common languages (php, python, java, ruby, .net, etc.) inways that is much easier than traditional calls to a sql based server. Whocares if they buy the system for the db and not use the rest of thescripting language!This strategy essentially positions webdna as an alternative, a simple easyto 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 couldresult in marketplace success. Fixing bugs and adding features supports thesmall group still using the product and in my opinion without marketinggenius and more lady luck than most of us have ever been graced with, themasses will not come over. However, who wouldn't want to try out a scrappypiece of software that promises to empower the developers to wrestle the dbthemselves!Oh, one last thought. You should be able to get a team together usingodesk.com pretty quickly. I've used a few contractors found on the site thathad 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:
Aloha all, I love WebDNA. Why? Creating, managing, extending, modifying,searching and editing databases is about as easy as it gets. It's so easythat most projects can do just fine without any database administrator. It'snot the scripting language. The scripting language is decent but definitelynot as feature rich or community supported as other options. I don't think Iam alone. I think there are tons of developers that are interested in usingsomething even easier than mysql than there are developers that will switchto a relatively obscure language. Plus competing with the open sourcealternatives is near suicide. Every day you'll see cool stuff about theother langs. For instance, host a 5 million hits per day site for free inGoogle's cloud with the potential to scale your app to any size (python fornow with other langs to follow); handle 25,000 connections at any given timewith 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 systemempowers developers with virtually no database skills to get up to speedpretty quickly.2. Have a web based interface to completely manage databases that blowsphpmyadmin way out of the water. The interface should also have a querybuilder so folks getting started and build queries visually. This toolcreates, manages, edits, deletes, merges, etc. databases. Have a sandboxfolks can play with online.3. Create a version of the software that essentially runs the dbserver andis callable via common languages (php, python, java, ruby, .net, etc.) inways that is much easier than traditional calls to a sql based server. Whocares if they buy the system for the db and not use the rest of thescripting language!This strategy essentially positions webdna as an alternative, a simple easyto 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 couldresult in marketplace success. Fixing bugs and adding features supports thesmall group still using the product and in my opinion without marketinggenius and more lady luck than most of us have ever been graced with, themasses will not come over. However, who wouldn't want to try out a scrappypiece of software that promises to empower the developers to wrestle the dbthemselves!Oh, one last thought. You should be able to get a team together usingodesk.com pretty quickly. I've used a few contractors found on the site thathad 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)