Re: [WebDNA] WebDNA future
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104438
interpreted = N
texte = > Instead I feel that any feature which has been around for a decade = should remain, regardless of its value in new sales, and the only reason = it should be removed is when 80-90% or more of us agree that it is no = longer necessary. But no one from WSC has ever actually consulted us = about this (or much of anything else), have they? There were the language using commands Then came the [contexts] The xml-like contexts The ISP versions with sandboxes The Commerce version The Enterprise version What we want to do at WSC is to recover the original "purity" of the = language, relieved from "wet blankets" and outdated features, and making = it ready for new interesting capabilities. The commands are outdated and will be removed The xml contexts implies a lot of overheat and are almost a language by = themselves. They will disappear. The sandboxes will be useless with the fastCGI version The Commerce and Enterprise software will be available separatly Most websites will be able to move from module to fastCGI without any = single programming modification. Nevertheless, the module version will still be available as 6.2.1, as a = free update and another free gift to the group. The module version would = have been perfect for an ISP, but so far, no ISP bought any license from = us. >> Some will offer resistance to changes and just argue=20 >> about anything ... >=20 > I am not "just arguing about anything" this comment was not exclusively for you ;-) > Sure it's your software so you can do anything you want with it, no = matter how it affects us. But I would personally be more comfortable = with WSC if you were to demonstrate a little more consideration for us = before you change or remove any more long-established features. I guess WSC has had a lot of consideration for the entire group, first = by saving WebDNA, then offering free updates, and working 18 months with = the secret hope that more than just a small loyal group would support = us. Now, we have to find new customers, and the module version as it = exists now is just not the right product for this. - chris=
Associated Messages, from the most recent to the oldest:
> Instead I feel that any feature which has been around for a decade = should remain, regardless of its value in new sales, and the only reason = it should be removed is when 80-90% or more of us agree that it is no = longer necessary. But no one from WSC has ever actually consulted us = about this (or much of anything else), have they? There were the language using commands Then came the [contexts] The xml-like contexts The ISP versions with sandboxes The Commerce version The Enterprise version What we want to do at WSC is to recover the original "purity" of the = language, relieved from "wet blankets" and outdated features, and making = it ready for new interesting capabilities. The commands are outdated and will be removed The xml contexts implies a lot of overheat and are almost a language by = themselves. They will disappear. The sandboxes will be useless with the fastCGI version The Commerce and Enterprise software will be available separatly Most websites will be able to move from module to fastCGI without any = single programming modification. Nevertheless, the module version will still be available as 6.2.1, as a = free update and another free gift to the group. The module version would = have been perfect for an ISP, but so far, no ISP bought any license from = us. >> Some will offer resistance to changes and just argue=20 >> about anything ... >=20 > I am not "just arguing about anything" this comment was not exclusively for you ;-) > Sure it's your software so you can do anything you want with it, no = matter how it affects us. But I would personally be more comfortable = with WSC if you were to demonstrate a little more consideration for us = before you change or remove any more long-established features. I guess WSC has had a lot of consideration for the entire group, first = by saving WebDNA, then offering free updates, and working 18 months with = the secret hope that more than just a small loyal group would support = us. Now, we have to find new customers, and the module version as it = exists now is just not the right product for this. - chris=
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:
AD Error Msg (1997)
Help! WebCat2 bug (1997)
Multiple Purchase (2002)
Giving out error pages (1997)
PCS Emailer's role ? (1997)
Re:trouble (1997)
Show your support (2002)
Speeding up my [showif] performance (1999)
[WebDNA] Secure Cookies (2009)
Is [thisurl] http or https? (1998)
Rubbish in form fields (2004)
X etc.... (1999)
WebCatalog2 Feature Feedback (1996)
syntax question, not in online refernce (1997)
Re:Variable Math (1998)
Execute Applescript (1997)
WebCatalog can't find database (1997)
Live Webcasts (1999)
[WebDNA] in case anyone out here is actually using the "WebdnaCodeSparker" framework... (2013)
Netscape v. IE (1997)