Re: [WebDNA] No more SQL in 7.1?
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 108503
interpreted = N
texte = Hi! about the name and the ideas suggested by Ken: 6.2 =3D WebDNA Classic 7.0 =3D WebDNA Prime 7.1 =3D WebDNA Lite Here how i see it: i expect 6.2 to disappear by lack of interest; 7.0 is = faster (particularely the [search] context we optimized and the [append] = context in RAM), offers more control, and runs on almost any linux-unix = platform. On another hand, 6.2 offers windows version, something we = still do not offer for WebDNA 7.x. Thus, it remains available, with one = single version for unlimited domains and is very reasonably priced. We = will see how much of those we are still selling. My guess is as soon as = we have a 7.x windows version, 6.2 will be in the limbo. 7.0 offers MySQL but how many of us need MySQL for new projects? when = SMSI targetted large companies, they would have had to support Oracle, = PostGres etc.. unfortunately, WebDNA lost support from these customers, = php evolved during the last 10 years and the niche is now controled by = ColdFusion, .Net and... php with polished (and very heavy) applications = like WordPress, Joomla, Magento etc... unfortunately for the webmasters, = there is almost no alternative and i hope WebDNA to become THE = alternative. WebDNA is much lighter than a LAMP server, the RAM and disk footprint is = a small percentage of a php+MySQL, is faster, includes its own database = system, works great with ajax, json or html5 (and we will further = improve this), is very easy to learn and i think more and more young = programmers, webmasters or even designers will discover the power of a = database driven interactive website without the hassle ot learning php = and MySQL. Sun's acquisition of MySQL did not go smoothly; most of the = MySQL leaders have left Sun. Oracle, not having the best possible = reputation in the Open Source space, has had a hard time keeping the = remaining MySQL people in the company or even working on the MySQL = project. Oracle will also have a hard time to ensure to the MySQL = customers, community and users that it will keep MySQL "free and = available for all". There is room for WebDNA and i am not sure = supporting MySQL will result in more sales, but it increases costs by = needing more builds and by complicating installation process. However, if i am wrong, then we will go back. To me, 7.1 is an evolution from 7.0: with its 64bits OSX version, with = its simplified installation process and no more need for external = dependencies. We optimized some parts of the code and we will go further = with future versions to make WebDNA even faster, even more controllable = and we will work with you to make the language more consistent and add = new features (particularely to simplify interactuation with ajax / html5 = / json). But i do not want WebDNA to convert into a complicated monster = like php did. I see 7.1 as the new platform to start from and go forward. Think different! :-) - chris On Feb 3, 2012, at 22:11, C. Frank Wolfe wrote: > You know, then name it 7.0 Lite, not 7.1 > That would solve all the confusion. >=20 > frank >=20 > On Feb 3, 2012, at 9:57 AM, aaronmichaelmusic@gmail.com wrote: >=20 >>> No one ever said anything about abandoning support for=20 >>> MySQL. Chris simply said he wants to create a Lite version=20 >>> that's faster and easier to install and will therefore not=20 >>> support MySQL. =20 >>>=20 >>> This is very different from abandoning MySQL support! >>=20 >> The language (from Chris/WebDNA Technical Change History) isn't very = clear to me one way or the other, so just checking in on the topic. = Also, the naming conventions of 'Prime' vs 'Lite' haven't been applied = until you came up with it Ken. So without that distinction, I don't = know what is being deprecated as opposed to what is being left out for a = 'lite-er' variety. Perhaps, if anything, this just creates an = opportunity to get feedback from the community on the issue. >>=20 >> I only have 1 site now that depends on 6.2, so I'm all about rolling = along with the latest builds as they come. I like the 'lite' concept = too, especially with the fcgi approach. I can use mostly 7.1 and where = I need it, load in the 7.0 build. Cool. One thing I'm not interested = in though (and this is just me personally) is maintaining legacy = products. So the future direction of this product is also important to = me. I want to be sure that the features I need will continue to be = supported down the line. That's all. >>=20 >> I don't want to start an argument about databases. I think they're = both great. But I have to say that the more I've gotten to know = RDBs/SQL, the more I think it is really quite cool, and If anything, I = plan to start using it more with WebDNA. =20 >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list
. >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >>=20 >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
Associated Messages, from the most recent to the oldest:
Hi! about the name and the ideas suggested by Ken: 6.2 =3D WebDNA Classic 7.0 =3D WebDNA Prime 7.1 =3D WebDNA Lite Here how i see it: i expect 6.2 to disappear by lack of interest; 7.0 is = faster (particularely the [search] context we optimized and the [append] = context in RAM), offers more control, and runs on almost any linux-unix = platform. On another hand, 6.2 offers windows version, something we = still do not offer for WebDNA 7.x. Thus, it remains available, with one = single version for unlimited domains and is very reasonably priced. We = will see how much of those we are still selling. My guess is as soon as = we have a 7.x windows version, 6.2 will be in the limbo. 7.0 offers MySQL but how many of us need MySQL for new projects? when = SMSI targetted large companies, they would have had to support Oracle, = PostGres etc.. unfortunately, WebDNA lost support from these customers, = php evolved during the last 10 years and the niche is now controled by = ColdFusion, .Net and... php with polished (and very heavy) applications = like WordPress, Joomla, Magento etc... unfortunately for the webmasters, = there is almost no alternative and i hope WebDNA to become THE = alternative. WebDNA is much lighter than a LAMP server, the RAM and disk footprint is = a small percentage of a php+MySQL, is faster, includes its own database = system, works great with ajax, json or html5 (and we will further = improve this), is very easy to learn and i think more and more young = programmers, webmasters or even designers will discover the power of a = database driven interactive website without the hassle ot learning php = and MySQL. Sun's acquisition of MySQL did not go smoothly; most of the = MySQL leaders have left Sun. Oracle, not having the best possible = reputation in the Open Source space, has had a hard time keeping the = remaining MySQL people in the company or even working on the MySQL = project. Oracle will also have a hard time to ensure to the MySQL = customers, community and users that it will keep MySQL "free and = available for all". There is room for WebDNA and i am not sure = supporting MySQL will result in more sales, but it increases costs by = needing more builds and by complicating installation process. However, if i am wrong, then we will go back. To me, 7.1 is an evolution from 7.0: with its 64bits OSX version, with = its simplified installation process and no more need for external = dependencies. We optimized some parts of the code and we will go further = with future versions to make WebDNA even faster, even more controllable = and we will work with you to make the language more consistent and add = new features (particularely to simplify interactuation with ajax / html5 = / json). But i do not want WebDNA to convert into a complicated monster = like php did. I see 7.1 as the new platform to start from and go forward. Think different! :-) - chris On Feb 3, 2012, at 22:11, C. Frank Wolfe wrote: > You know, then name it 7.0 Lite, not 7.1 > That would solve all the confusion. >=20 > frank >=20 > On Feb 3, 2012, at 9:57 AM, aaronmichaelmusic@gmail.com wrote: >=20 >>> No one ever said anything about abandoning support for=20 >>> MySQL. Chris simply said he wants to create a Lite version=20 >>> that's faster and easier to install and will therefore not=20 >>> support MySQL. =20 >>>=20 >>> This is very different from abandoning MySQL support! >>=20 >> The language (from Chris/WebDNA Technical Change History) isn't very = clear to me one way or the other, so just checking in on the topic. = Also, the naming conventions of 'Prime' vs 'Lite' haven't been applied = until you came up with it Ken. So without that distinction, I don't = know what is being deprecated as opposed to what is being left out for a = 'lite-er' variety. Perhaps, if anything, this just creates an = opportunity to get feedback from the community on the issue. >>=20 >> I only have 1 site now that depends on 6.2, so I'm all about rolling = along with the latest builds as they come. I like the 'lite' concept = too, especially with the fcgi approach. I can use mostly 7.1 and where = I need it, load in the 7.0 build. Cool. One thing I'm not interested = in though (and this is just me personally) is maintaining legacy = products. So the future direction of this product is also important to = me. I want to be sure that the features I need will continue to be = supported down the line. That's all. >>=20 >> I don't want to start an argument about databases. I think they're = both great. But I have to say that the more I've gotten to know = RDBs/SQL, the more I think it is really quite cool, and If anything, I = plan to start using it more with WebDNA. =20 >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >>=20 >=20 >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us
christophe.billiottet@webdna.us
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:
carriage returns in data (1997)
webcat nt (1997)
webdelivery not working (1998)
OT Weird Messenger Service message (2002)
Is there a max number of fields? (1998)
Associative lookup style? + bit more (1997)
Attn: Bug in GeneralStore example b15 (1997)
RE: strip .0 off off IPaddress (1999)
More Shopping Cart Problems (2000)
Sitebuilder (2004)
Locking up with WebCatalog... (1997)
Images in WebCat (2000)
Webcat not processed for CACHEd image error pages (1998)
emailer settings and control questions (1997)
mail on NT (1998)
still having shipCost.db Problem (1997)
First postarg not taking in $Commands (1997)
E-mail loop ! (1997)
ShowNext (1997)
Re:no [search] with NT (1997)