I know this thread has been thrashed pretty good, but one more thought---
I see it as the best for multiple types of hams
For those that really want to be on the bleeding edge-- truly are the
experimental types, there are the betas, latest "let's try this" ideas
that may or may not pan out.
erant of the frailty of others! And that does
include people who write software!
Lee K9WRU
- Original Message - From: "Burt"
To:
Sent: Saturday, November 06, 2010 8:39 PM
Subject: Re: [Flexradio] The just around the corner syndrome
I can think of one thing more humbling bei
ilty of others!
> And that does include people who write software!
>
> Lee K9WRU
> - Original Message ----- From: "Burt"
> To:
> Sent: Saturday, November 06, 2010 8:39 PM
> Subject: Re: [Flexradio] The just around the corner syndrome
>
>
>
> I can
I can't speak for Flex but in my experience unless you require and have
a lot of external programmers it can take just as many internal
resources to manage the external ones by the time you make sure they
follow your process, coding standards, etc.
Developing a large program that controls mult
: Saturday, November 06, 2010 8:39 PM
Subject: Re: [Flexradio] The just around the corner syndrome
I can think of one thing more humbling being called in one hour AFTER
school began to take a 4th grade class and try and figure out lesson plans
while the kids are watching after have had no teach
It's my understand that this has been in the works for about 5 years, is that
correct?
It has to be a little difficult trying to write one software program for 3
different (or is 4?) different products.
Perhaps it's time to farm some of it out - I'm sure that there are software
people that would
I can think of one thing more humbling being called in one hour AFTER school
began to take a 4th grade class and try and figure out lesson plans while the
kids are watching after have had no teacher for an hour
Burt
--- On Sat, 11/6/10, Neal Campbell wrote:
>
> I can say from personal experie
I think thats exactly why Flex isn't giving any dates at all. I think the
description of the new development cycle they are using internally caused
some people to expect a new beta every two weeks. As Tim's note earlier
documented, they are doing a pretty decent job doing release iterations and
sin
Ron,
No flamesHang in there.. There is a lot of work going on in the
background, these changes are not just minor updates or fixes. Things like
an entirely new USB driver for the 1500, additions to the U/V modules,
besides corrections to the usual list of fixes.
The final release is not
I am not bothered by the fact that it takes a couple of months to
deliver a new beta version of Pwrsdr, what bothers me is that we are
alerted to look for some great release that should be available next
week. Next week is suddenly a month and then 2 months. I know Flex is
not going to releas
10 matches
Mail list logo
