It's just a difference in training, I was taught the a bug always took down a system and anything else was a Minor Glitch, Obviously with the advent of modular programming you could have a bug in a module that always faults the module, but it only happens when specific modules are called, not when everyone or anyone uses windows.
The use of Bug is more common in those "articles" that are used as Clickbait, It's an emotive word, and sells advertising
In my opinion a bug is a catastrophic failure, anything else is a feature.
"Set defaults by app" works fine here.
Well as a seasoned Fortran progammer, a bug was always just a coding error. It could be a minor bug or a serious bug but ALWAYS a bug.It's just a difference in training, I was taught the a bug always took down a system and anything else was a Minor Glitch, Obviously with the advent of modular programming you could have a bug in a module that always faults the module, but it only happens when specific modules are called, not when everyone or anyone uses windows.
The use of Bug is more common in those "articles" that are used as Clickbait, It's an emotive word, and sells advertising
Computer Scientists did not exist when I started programming - you were either a computer technician who looked after the hardware, or you were an engineer who did programming to solve problems that were previously virtually insoluble (iterative solutions mostly).
It is only when Computer Scientists took over, that terms like modular programming were coined. We had subroutines which was really modular programming. Terms like objects never existed - we used variables!
I know one thing - many major engineering packages still use Fortan or an offshoot still to this day for crunching mathematical solutions at the core of their programming. It is only the fancy front ends that have changed.
Quote
