Re: [WebDNA] WebDNA future
This WebDNA talk-list message is from 2010
It keeps the original formatting.
numero = 104445
interpreted = N
texte = > 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. This is an excellent goal Chris. I have always felt that a cheap one-domain version of the software (think "Typhoon" if you will) was the way to get lots of new customers. It just has to be done right, not the way Typhoon was done by PCS. > The commands are outdated and will be removed I thought SmithMicro was going to do this years ago but nothing ever came of it. > The xml contexts implies a lot of overheat and are > almost a language by themselves. They will disappear. I have actually used the xml stuff recently. It's hard to understand unless the new docs explain things better, but I was using it somewhere ... Twitter I think. Once you get it working it's great, but it's really confusing to figure out. Someone could have done a better job of conceiving the syntax for the XML stuff, that's for sure. > The sandboxes will be useless with the fastCGI version And this makes things so much easier to manage and secure! > The Commerce and Enterprise software will be > available separatly In all the years that I've coded in WebDNA I have seldom used the eCommerce stuff. It is very outdated in that it still uses static files rather than a db for maintaining cart/order data. I was told a very long time ago that the only reason WebMerchant uses those static cart/order files is because it was developed long before WebCatalog could open multiple databases. Nothing was ever done to update this situation after WebCatalog gained multi-database capability, so we are still using that old file-based system from 15 years ago. I think your decision to make the commerce stuff separate is good. It will be even better to get rid of the cart file system and replace it with a database system if you find that people start buying the eCommerce add-on. I actually wrote such a db-driven eCommerce system for Typhoon 10-15 years ago. It was exceptionally flexible compared with the old cart file system. But Typhoon died so I never bothered doing anything with it. I wonder if I still have it on my hard drive somewhere? I'll have to check. > Most websites will be able to move from module to fastCGI > without any single programming modification. That's good news. > Nevertheless, the module version will still be available as > 6.2.1, as a free update and another free gift to the group. In other words you're going to continue to maintain 6.2.1 basically as 6.2 exists now (only with some bug fixes?) so people can still use WebDNA the same way they have always used it. Yet for those with simpler needs and an eye toward the future, your new standard product is going to be the FastCGI version. Is this correct or have I misunderstood something here? > The module version would have been perfect for an ISP, > but so far, no ISP bought any license from us. SmithMicro poured a lot of money into trying to get ISP's to buy into that scenario too. I guess you're learning what they already learned about ISP's and their software needs. I think your FastCGI version is the best way to move WSC into the future. At least it should run on nginx, right? Are you testing on nginx? Sincerely, Kenneth Grome www.KenGrome.com
Associated Messages, from the most recent to the oldest:
> 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. This is an excellent goal Chris. I have always felt that a cheap one-domain version of the software (think "Typhoon" if you will) was the way to get lots of new customers. It just has to be done right, not the way Typhoon was done by PCS. > The commands are outdated and will be removed I thought SmithMicro was going to do this years ago but nothing ever came of it. > The xml contexts implies a lot of overheat and are > almost a language by themselves. They will disappear. I have actually used the xml stuff recently. It's hard to understand unless the new docs explain things better, but I was using it somewhere ... Twitter I think. Once you get it working it's great, but it's really confusing to figure out. Someone could have done a better job of conceiving the syntax for the XML stuff, that's for sure. > The sandboxes will be useless with the fastCGI version And this makes things so much easier to manage and secure! > The Commerce and Enterprise software will be > available separatly In all the years that I've coded in WebDNA I have seldom used the eCommerce stuff. It is very outdated in that it still uses static files rather than a db for maintaining cart/order data. I was told a very long time ago that the only reason WebMerchant uses those static cart/
order files is because it was developed long before WebCatalog could open multiple databases. Nothing was ever done to update this situation after WebCatalog gained multi-database capability, so we are still using that old file-based system from 15 years ago. I think your decision to make the commerce stuff separate is good. It will be even better to get rid of the cart file system and replace it with a database system if you find that people start buying the eCommerce add-on. I actually wrote such a db-driven eCommerce system for Typhoon 10-15 years ago. It was exceptionally flexible compared with the old cart file system. But Typhoon died so I never bothered doing anything with it. I wonder if I still have it on my hard drive somewhere? I'll have to check. > Most websites will be able to move from module to fastCGI > without any single programming modification. That's good news. > Nevertheless, the module version will still be available as > 6.2.1, as a free update and another free gift to the group. In other words you're going to continue to maintain 6.2.1 basically as 6.2 exists now (only with some bug fixes?) so people can still use WebDNA the same way they have always used it. Yet for those with simpler needs and an eye toward the future, your new standard product is going to be the FastCGI version. Is this correct or have I misunderstood something here? > The module version would have been perfect for an ISP, > but so far, no ISP bought any license from us. SmithMicro poured a lot of money into trying to get ISP's to buy into that scenario too. I guess you're learning what they already learned about ISP's and their software needs. I think your FastCGI version is the best way to move WSC into the future. At least it should run on nginx, right? Are you testing on nginx? Sincerely, Kenneth Grome www.KenGrome.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:
[sendmail] on NT? (1997)
Associative lookup style? (1997)
[WebDNA] Need someone to port CakePHP auction site to WebDNA (2010)
Trunk-gator (1997)
[WebDNA] Installing WebDNA on VPS (2008)
Mozilla/4. and Browser Info.txt (1997)
[WebDNA] Yosemite (2014)
Fwd: Problems with Webcatalog Plug-in (1997)
[MATH] and Dates (1998)
emailer setup (1997)
Serving images from databases (1998)
categories (1997)
Moment of Thanks (1997)
Sorting by date (1997)
Re:Virtual hosting and webcatNT (1997)
Who is doing sign-ups-got it (1998)
Sort Order on a page search (1997)
WebCat2b15MacPlugin - [protect] (1997)
How can I Add several Items into the cart at once? (1997)
[WebDNA] anyone use curl with shell? (2010)