A bunch of the software in the world of ham radio is pretty bad--for whatever reason it seems like everybody is stuck on developing software for Windows 95/98 with Visual Basic or FoxPro, and they typically shoot for "it gets the job done" and not much else. There is some great (and free) software out there, but HRD isn't one of them.
The real advances in amateur radio software are coming from the devs and hams who embrace open source, or at least believe in sharing the knowledge.
A bunch of the software in the world of ham radio is pretty bad--for whatever reason it seems like everybody is stuck on developing software for Windows 95/98 with Visual Basic or FoxPro, and they typically shoot for "it gets the job done" and not much else.
That's because electrical engineers are typically shit at writing code. I've been looking at code written by EE's for a long time, and it is almost always bad - full of software delay loops (because there is only one speed of CPU out there), structured like a landfill, breaking every form of good practice known to mankind, etc.
You also shouldn't let software engineers get close to a soldering iron, but that's ok - the two groups can work together to get great things done...
99% of software is developed to the point of "it gets the job done" and that's all.
Quite simply because getting the job done is the most important part of the job's function.
If only the writer or a small number of people are ever going to use it, then there is no need to develop it further and change for change's sake is a waste of time.
I disagree. Change that does not change functionality, but improves user friendliness, performance, resource usage, or just sheer elegance and awesomeness, is still a welcome improvement.
Also, I find the efficiency argument boring. In the end we all die. Life is not about being 'most efficient' before that moment comes.
A bug in the hand is better than one as yet undetected.
Sadly... (Score:3, Informative)
Re:Sadly... (Score:2)
A bunch of the software in the world of ham radio is pretty bad--for whatever reason it seems like everybody is stuck on developing software for Windows 95/98 with Visual Basic or FoxPro, and they typically shoot for "it gets the job done" and not much else.
That's because electrical engineers are typically shit at writing code. I've been looking at code written by EE's for a long time, and it is almost always bad - full of software delay loops (because there is only one speed of CPU out there), structured like a landfill, breaking every form of good practice known to mankind, etc.
You also shouldn't let software engineers get close to a soldering iron, but that's ok - the two groups can work together to get great things done...
Re: (Score:2)
99% of software is developed to the point of "it gets the job done" and that's all.
Quite simply because getting the job done is the most important part of the job's function.
If only the writer or a small number of people are ever going to use it, then there is no need to develop it further and change for change's sake is a waste of time.
Re: (Score:2)
I disagree. Change that does not change functionality, but improves user friendliness, performance, resource usage, or just sheer elegance and awesomeness, is still a welcome improvement.
Also, I find the efficiency argument boring. In the end we all die. Life is not about being 'most efficient' before that moment comes.