[Elecraft] Firmware Fatigue - was K2 v K3

[michael taylor]

On Wed, May 7, 2008 at 12:51 PM, S Sacco <nn4x.steve at gmail.com> wrote:
> I think the problem (well, one of the problems; there are several) is
> that they don't, in reality, have a "Beta" test; they go from "Alpha"
> right into Production.

I am an outsider, just an Elecraft customer, and from what I've seen
there is nothing wrong with their development process. User/Field
flashable devices are more toward the personal computer software
release style, than what we are use to for black box amateur
transceivers.

The firmware upgrade process for the K3 is no harder than frequency
calibration, so I don't particularly see why there is so much concern.
Maybe I'm missing something because I'm extremely comfortable for
computers. Of course, I personally view and can visualize software as
an extension to hardware (analog and digital) so I just see it as a
different point on the continuum of change. Not unlike the general
decline (and popular demise) of electron tubes and analog computers.
Heck you don't even have set down your drink to update the firmware,
whereas some of the post initial release K2 mods were best done with
two hands which could interrupt beverage consumption.

"Can you teach your old radio new tricks?"

-Michael, VE3TIX