Coming in late here...

But just to clarify, Russ are you saying that you're finding more
bugs/errors in fusebox applications in comparison to non-fusebox
applications or just pointing out that its harder to debug a Fusebox
application than a non-fusebox application (for a non fuseboxer)?

Kola

>> -----Original Message-----
>> From: Snake Hollywood [mailto:[EMAIL PROTECTED]
>> Sent: 03 February 2004 13:58
>> To: [EMAIL PROTECTED]
>> Subject: RE: [ cf-dev ] cfstandards...coming soon!
>> 
>> Lets hope this might teach more people how to build frameworks and
write
>> modular code instead of pissing about with Fusecrap.
>> 
>> <cf_bitch>
>> Yes I am having a moan about fusebox again.
>> Why?
>> Because we have an increasing number of hosting customers with sites
>> written
>> in fusebox, and most of them has come to us at some point with a
broken
>> site
>> or a cferror and have insisted it is oour fault and there is a
problem
>> with
>> our servers insisting there is no problem with their code.
>> We (meaning me) then have to go and debug their fusebox code to find
the
>> error and prove it's not our fault. On the occasions where I have
said,
>> sorry your sites written in fusebox that's the problem, I have got
back
>> quite a lot of abuse along the lines of "I thought you were meant to
be a
>> good hosting company", "this is shit service", "there is nothing
wrong
>> with
>> our code we know what we are doing"... Etc etc...  Of course I do get
an
>> apology when I give in and go and fix their code for them, but still
I am
>> getting a bit sick of it now, because it's always fusebox apps this
>> happens
>> with. I don't mind so much when it's regular code as I can usually
tell
>> what
>> the problem is without having to wade around in their code first.
>> 
>> I am absolutely adamant now that fusebox promotes developers to
produce
>> and
>> use code they do not understand and to write apps they cannot debug.
>> </cf_bitch>
>> 
>> Now all our customers who are on this list prob wont dare ask me
about
>> fusebox problems now :-)
>> Don't be scared I'm lovely really...
>> 
>> Russ Michaels
>> Macromedia/Allaire Certified ColdFusion Developer
>> 
>> CFMX Hosting
>> Phone: 0845 456 3487
>> Tech Support: 0906 9607800
>> FAX: 0709 2212 636
>> WEB: cfmxhosting.co.uk
>> 
>> >Please use the support helpdesk on our web site to submit support
>> tickets.<
>> 
>> Join our ColdFusion Developer discussion lists.
>> Send an e-mail to [EMAIL PROTECTED]
>> 
>> 
>> > -----Original Message-----
>> > From: Simon Horwith [mailto:[EMAIL PROTECTED]
>> > Sent: 03 February 2004 11:37
>> > To: UK DevList (E-mail)
>> > Subject: [ cf-dev ] cfstandards...coming soon!
>> >
>> >
>> > I apologize to those of you have already read this post on
>> > CF-Talk, but since I publicly mentioned it on that list and
>> > I'd briefly mentioned it on some other lists some time ago
>> > without divulging any details, I thought I'd post the
>> > information to this list so that you are more aware of the
>> > project I've begun.  The site is cfstandards.org, and is
>> > committed to the definition of ColdFusion Standards in
>> > application functionality and coding practices. The site's
>> > still under development, but you can sign up for the
>> > newsletter, begin making suggestions for projects, and apply
>> > to be a volunteer right now. I'll diverge more details when
>> > the time is right, but for now I'll let you all know a few
>> > things about the project:
>> >
>> > 1. all of the code is open source and free
>> >
>> > 2. the site will not be a distribution point for UDFs, custom
>> > tags, etc. The purpose of the site is to develop modules for
>> > functionality common to web applications... very similar to
>> > jakarta and the J2EE specification itself
>> >
>> > 3. in addition to modules for "plug and play" functionality,
>> > the site will also begin defining development best
>> > practices... this will include CFML syntax, the organization
>> > of code, documentation, and more
>> >
>> > 4. I am putting together a panel of experts in the industry -
>> > development gurus and representatives from the big industry
>> > players - to make decisions regarding these best practices
>> > and to make decisions regarding which proposed projects and
>> > standards to accept and reject
>> >
>> > 5. all of the modules will adhere to these coding standards
>> > and the panel, along with other cfstandards gurus, will
>> > determine whether or not content submitted by volunteers
>> > meets these coding standards
>> >
>> >
>> > There's a little bit of information about the project on the
>> > site right now
>> > (http://www.cfstandards.org) but like I said, there will be a
>> > lot more functionality and information very soon. I have
>> > already begun receiving emails from developers that read
>> > about the project in my MAX summary back in November (page 2
>> > of http://sys-con.com/coldfusion/article.cfm?id=684) and I
>> > encourage any developers on the UK Devlist that are
>> > interested in contributing to contact me off-list via email
>> > or via the web site if you wait a day or two.
>> >
>> >
>> > ~Simon
>> >
>> >
>> > Simon Horwith
>> > CTO, Etrilogy Ltd.
>> > Member of Team Macromedia
>> > Macromedia Certified Instructor
>> > Certified Advanced ColdFusion MX Developer
>> > Certified Flash MX Developer
>> > CFDJList - List Administrator
>> > http://www.how2cf.com/
>> >
>> >
>> >
>> >
>> > --
>> > ** Archive:
http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
>> >
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail:
>> > [EMAIL PROTECTED] For human help, e-mail:
>> > [EMAIL PROTECTED]
>> >
>> 
>> 
>> --
>> ** Archive:
http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/
>> 
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>> For human help, e-mail: [EMAIL PROTECTED]


-- 
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]

Reply via email to