RE: update or new version of jfw?
- From: James <james@xxxxxxxxxxxxxxxx>
- To: jfw@xxxxxxxxxxxxx
- Date: Thu, 21 Oct 2004 23:16:44 -0400
Here lies the problem, though. You *can't* get it out and get it out fast,
and still fix the bugs. You only succeed then in creating 2 more bugs for
every 1 you fix, and then you have 2 more problems crop up that you want
fixed and fixed now. It's a vicious cycle.
Also remember back in 1992 there wasn't as much of a demand for things like
this, and programs weren't as hardcore, for lack of a better term, as they
are today. One or two bugs didn't completely pull a program down around
your ears 12 years ago. Here, today, something doesn't work right, the
program goes poof and you suddenly lost whatever you were working on.
Also on that note, software has become significantly more advanced now than
12 years ago. Sometimes it takes until the next version of a program to
find a bug to begin with. JFW alone, without scripts and other added files,
has to be thousands of lines of code. Do you want to try looking for one
small error in that? Then you factor in the scripts that come with, and the
fact that any number of issues with those scripts could very well be what
causes JFW to go whacky with certain programs. Suddenly you have a 2, 3, or
4-layer program that you have to debug.
Of course, there's also the possibility that the bug lies with the program
JFW tries to support. At which point it's entirely out of FS's hands
anyway, and you're waiting for the next version of *that* program to be
released. The cycle will repeat with that program and its creators until it
locates that bug, as well. So you're losing more than you're gaining with
that attitude.
James,
List Admin
At 11:05 PM 10/21/2004, you wrote:
>Ok here we go the question of access and access now or all the bugs =
>fixed
>and getting it right first as you put it. This will mean that we will =
>see
>the new operating systems lator then every one else as we did in the =
>past.
>It will mean that the tools we need to access new programs will take =
>time to
>come out instead of being there when we need them. It used to be that
>access software was as buggy as hell but every one excepted this and was
>glad for the access. For example when I started using windows in =
>november
>of 1992 I understood the access was new and had bugs but I was happy =
>enough
>to be able to use windows just like my friends were doing and some of =
>the
>programs I needed were in windows so that access was grait. Did it have
>problems oh yes you bet it did but I was to happy to have the access to
>these programs to conplain overly much instead I worked with the =
>createers
>of this access software to make it better. So if it means not having =
>access
>to some thing or having a few bugs to deal with I for one would rather =
>have
>the access. In the case of jaws though we should be getting updates =
>every
>few weeks though tell they get there act together. In other words =
>providing
>the access they have been saying they were going to give to remote =
>access
>servers. Fixing the bugs in sertain functions like type current script =
>key.
>Yes this function does have problems and is used by a lot of scripters. =
>Jfw
>loading the wrong scripts. Jfw issues with msaa where it just stops =
>reading
>web pages. Jfw not reading in internet explorer unless it is maxamized.
>Things like that we do not need to wait a long time for thoughs issues =
>to be
>addressed we need them addressed now now now. So for my money once =
>again
>get it out get it out fast and make sure while you are getting it out =
>that
>the bugs get fixed and new features as needed get added. =20
>
>
>-----Original Message-----
>From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On =
>Behalf
>Of Bruce Toews
>Sent: Thursday, October 21, 2004 6:31 PM
>To: jfw@xxxxxxxxxxxxx
>Subject: RE: update or new version of jfw?
>
>
>But for someone else's money, get it right first. Whose money is worth=20
>more?
>
>Bruce
>
>--=20
>Bruce Toews
>E-mail and MSN/Windows Messenger: coke_drinker@xxxxxxxx
>Web Site (including info on my weekly commentaries): http://www.ogts.net =
>For
>the best oldies anywhere visit http://www.treasureislandoldies.com
>
>On Thu, 21 Oct 2004, jim grimsby wrote:
>
> > Well for my money get it out get it out fast and fix bugs as they come =
>
> > =3D up please and thank you!
> >
> > -----Original Message-----
> > From: jfw-bounce@xxxxxxxxxxxxx [mailto:jfw-bounce@xxxxxxxxxxxxx] On =
>=3D=20
> > Behalf Of Bruce Toews
> > Sent: Thursday, October 21, 2004 2:20 PM
> > To: jfw@xxxxxxxxxxxxx
> > Subject: RE: update or new version of jfw?
> >
> >
> > The reality is that FS is caught between a rock and a hard place in =
>=3D=20
> > terms=3D20 of PR when it comes to release dates. Release a product too =
>
> > soon, and =3D it's=3D20
> > bug-ridden, and everyone whines about how they should have wated. Wait =
>=3D
> > and=3D20
> > try to deal with bugs, and everyone whines about how the other guy got =
>=3D
> > it=3D20
> > out sooner, why can't they? There's no winning.
> >
> > Bruce
> >
> > --=3D20
> > Bruce Toews
> > E-mail and MSN/Windows Messenger: coke_drinker@xxxxxxxx
> > Web Site (including info on my weekly commentaries):=20
> > http://www.ogts.net =3D For the best oldies anywhere visit=20
> > http://www.treasureislandoldies.com
> >
> > On Thu, 21 Oct 2004, Chip Orange wrote:
> >
> >> Well, being a software developer myself, I know that release dates=20
> >> are =3D
> >
> >> always a tug of war between when you want it ready and when it =
>is=3D20=20
> >> really ready. Different companies have differing policies as to=3D20 =
>
> >> exactly which wins in the struggle.
> >>
> >> =3D3D20
> >> Chip
> >>
> >>> -----Original Message-----
> >>> From: jfw-bounce@xxxxxxxxxxxxx=3D3D20=20
> >>> [mailto:jfw-bounce@xxxxxxxxxxxxx] =3D
> >
> >>> On Behalf Of hank
> >>> Sent: Thursday, October 21, 2004 3:06 PM
> >>> To: jfw@xxxxxxxxxxxxx
> >>> Subject: Re: update or new version of jfw?
> >>> =3D3D20
> >>> interesting they told me they didn't have a release date. funky
> >>> ----- Original Message -----
> >>> From: "Troy Burnham" <tburnham@xxxxxxxxx>
> >>> To: <jfw@xxxxxxxxxxxxx>
> >>> Sent: Thursday, October 21, 2004 11:30 AM
> >>> Subject: Re: update or new version of jfw?
> >>> =3D3D20
> >>> =3D3D20
> >>>> A friend of mine called FS the other day and was told that a=3D3D20
> >>> new version,
> >>>> probably 6.0, will be out around the end of the year I=3D3D20
> >>> think it was. I
> >>>> don't know what will be in it though or if that is even=20
> >>>> accurate.=3D20 Troy
> >>>>
> >>>>
> >>>>
> >>>> On Thursday 10/21/2004 01:17 PM, Jarrod Jicha said:
> >>>>> does anyone know or has anyone heard anything about when=3D3D20
> >>> either an update,
> >>>>> or a new version of jfw is coming out? was just wondering,=3D3D20
> >>> also, does
> >>>>> anyone either know, or have they heard what will be in the=3D3D20
> >>> new version?
> >>>>> --
> >>>>> To post a message to the list, send it to jfw@xxxxxxxxxxxxx =
>To=3D20=20
> >>>>> unsubscribe from this mailing list, send a message to=3D20=20
> >>>>> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=3D3D20
> >>> subject line.
> >>>>> Archives located at: //www.freelists.org/archives/jfw
> >>>>>
> >>>>> If you have any concerns about the list, post received from=3D3D20
> >>> the list, or
> >>>>> the way the list is being run, do not post them to the list.=20
> >>>>> Rather =3D
> >
> >>>>> contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> >>>>
> >>>> --
> >>>> To post a message to the list, send it to jfw@xxxxxxxxxxxxx To=3D20 =
>
> >>>> unsubscribe from this mailing list, send a message to=3D3D20=3D20=20
> >>>> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=3D3D20
> >>> subject line.
> >>>> Archives located at: //www.freelists.org/archives/jfw
> >>>>
> >>>> If you have any concerns about the list, post received from=3D3D20
> >>> the list, or=3D3D20
> >>>> the way the list is being run, do not post them to the list.=3D20=20
> >>>> Rather=3D3D20 contact the list owner at=20
> >>>> jfw-admins@xxxxxxxxxxxxxx=3D3D20
> >>> =3D3D20
> >>> --
> >>> To post a message to the list, send it to jfw@xxxxxxxxxxxxx To=3D20=20
> >>> unsubscribe from this mailing list, send a message to=3D3D20=3D20=20
> >>> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the=3D3D20 =
>=3D
> > subject=3D20
> >>> line. Archives located at: //www.freelists.org/archives/jfw
> >>> =3D3D20
> >>> If you have any concerns about the list, post received from=3D3D20 =
>the=20
> >>> list, or the way the list is being run, do not post them=3D3D20 to =
>the=20
> >>> list. Rather contact the list owner at=3D3D20=20
> >>> jfw-admins@xxxxxxxxxxxxxx =3D3D20
> >> --
> >> To post a message to the list, send it to jfw@xxxxxxxxxxxxx To=3D20=20
> >> unsubscribe from this mailing list, send a message to=3D20=20
> >> jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the =
>subject=3D20=20
> >> line. Archives located at: //www.freelists.org/archives/jfw
> >>
> >> If you have any concerns about the list, post received from the=20
> >> list,=3D20 or the way the list is being run, do not post them to the=20
> >> list. Rather =3D
> >
> >> contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> >>
> > --
> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx To=20
> > unsubscribe from this mailing list, send a message to=20
> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject=20
> > line. Archives located at: //www.freelists.org/archives/jfw
> >
> > If you have any concerns about the list, post received from the list,=20
> > or =3D the way the list is being run, do not post them to the list.=20
> > Rather contact =3D the
> > list owner at jfw-admins@xxxxxxxxxxxxxx
> >
> >
> > --
> > To post a message to the list, send it to jfw@xxxxxxxxxxxxx To=20
> > unsubscribe from this mailing list, send a message to=20
> > jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject=20
> > line. Archives located at: //www.freelists.org/archives/jfw
> >
> > If you have any concerns about the list, post received from the list,=20
> > or the way the list is being run, do not post them to the list. Rather =
>
> > contact the list owner at jfw-admins@xxxxxxxxxxxxxx
> >
>--
>To post a message to the list, send it to jfw@xxxxxxxxxxxxx
>To unsubscribe from this mailing list, send a message to
>jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
>Archives located at: //www.freelists.org/archives/jfw
>
>If you have any concerns about the list, post received from the list, or =
>the
>way the list is being run, do not post them to the list. Rather contact =
>the
>list owner at jfw-admins@xxxxxxxxxxxxxx
>
>
>--
>To post a message to the list, send it to jfw@xxxxxxxxxxxxx
>To unsubscribe from this mailing list, send a message to
>jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
>Archives located at: //www.freelists.org/archives/jfw
>
>If you have any concerns about the list, post received from the list, or
>the way the list is being run, do not post them to the list. Rather
>contact the list owner at jfw-admins@xxxxxxxxxxxxxx
--
To post a message to the list, send it to jfw@xxxxxxxxxxxxx
To unsubscribe from this mailing list, send a message to
jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line.
Archives located at: //www.freelists.org/archives/jfw
If you have any concerns about the list, post received from the list, or the
way the list is being run, do not post them to the list. Rather contact the
list owner at jfw-admins@xxxxxxxxxxxxxx
Other related posts:
