did you ever use a program that was buggy, and you wondered how the authors could have released it. don't they use the program themselves? how could they not be aware of the bugs?
Name:
Anonymous2006-10-29 13:45
Yeah... Windows does that all the time.
Name:
Anonymous2006-10-29 14:21
i think it's not so much that they're not aware of the bugs, so much as they're aware of the bugs and just think users are too stupid to either notice or care and don't waste the time fixing them. they have deadlines to meet, you know.
Name:
Anonymous2006-10-29 16:26
Welcome to an economy ruled by marketing weenies who get boners over unreasonable deadlines that not even the best programmers in the world can fulfill.
Name:
Anonymous2006-10-29 17:06
why are there open source programs like that though?
Software Engineering's cumulative knowledge: software is hard
Name:
Anonymous2006-10-31 3:24
>>5
Because every cockjockey can be a programmer. Most of them don't have the patience and discipline to write correct programs however, and so infinite quantities of crap gets released.
Ever wonder how bloated software gets that way when there are small, elegant, fast, correct programs around as well? That's because the development cycle of good software involves a phase of expansion (when new features, etc, are written in) and a phase of contraction (where refactoring, bugfixing and reduction in code size and the number of special cases occurs).
Unsurprisingly, software developed in a corporate environment rarely gets to do the second phase, leading to worse bloat in the next expansion phase. This applies to many quasi-corporate environments too, such as some open source projects that hire people to write code for them. "It works, so why do you insist on calling this prototype code that will get replaced? It works, so why would you want to replace it? Get to work, we need new features." Worse, this leads to programmers that suffer from burnout due to a code base that just keeps getting worse and worse given a "number of features" -centric model of deveopment.
// Super High Infrastructure Technology Operating System
// v1.00 COMPLETE RELEASEVERSION NOT BETA
//
// Theory of operation:
// Programs run best when they have direct access to the hardware
// and don't have to go through an intermediate software solution
// to function. Furthermore, introduction of such a software layer
// (better known as 'kernel', 'BIOS', etc. to primitive minds) only
// serves to introduce bugs while decreasing execution speed. By
// eliminating the entire notion of operating system services, we
// assure maximum performance. Programs are all expected to write
// directly to hardware.
// Super High Infrastructure Technology Operating System
// v2.00 COMPLETE RELEASEVERSION NOT BETA
//
// Theory of operation:
// Programs run best when they have direct access to the hardware
// and don't have to go through an intermediate software solution
// to function. Furthermore, introduction of such a software layer
// (better known as 'kernel', 'BIOS', etc. to primitive minds) only
// serves to introduce bugs while decreasing execution speed. By
// eliminating the entire notion of operating system services, we
// assure maximum performance. Programs are all expected to write
// directly to hardware.
int main()
{
printf("Welcome to ShitOS v2.0\n");
return 0;
}
// Super High Infrastructure Technology Operating System
// v1.9 COMPLETE RELEASEVERSION3 NOT BETA
//
// Theory of operation:
// Programs run best when they have direct access to the hardware
// and don't have to go through an intermediate software solution
// to function. Furthermore, introduction of such a software layer
// (better known as 'kernel', 'BIOS', etc. to primitive minds) only
// serves to introduce bugs while decreasing execution speed. By
// eliminating the entire notion of operating system services, we
// assure maximum performance. Programs are all expected to write
// directly to hardware.
int main(int argc, char* argv[]) {
puts("Welcome to ShitOS v2.0");
return 0;
}
Name:
Anonymous2006-11-01 17:08
OMG BUGS
$ splint -strict test.c
Splint 3.1.1 --- 21 Jun 2006
test.c: (in function main)
test.c:15:5: Called procedure puts may access file system state, but globals
list does not include globals fileSystem
A called function uses internal state, but the globals list for the function
being checked does not include internalState (Use -internalglobs to inhibit
warning)
test.c:15:5: Undocumented modification of file system state possible from call
to puts: puts("Welcome to ShitOS v2.0")
report undocumented file system modifications (applies to unspecified
functions if modnomods is set) (Use -modfilesys to inhibit warning)
test.c:15:5: Return value (type int) ignored: puts("Welcome to...
Result returned by function call is not used. If this is intended, can cast
result to (void) to eliminate message. (Use -retvalint to inhibit warning)
test.c:14:14: Parameter argc not used
A function parameter is not used in the body of the function. If the argument
is needed for type compatibility or future plans, use /*@unused@*/ in the
argument declaration. (Use -paramuse to inhibit warning)
test.c:14:26: Parameter argv not used
Finished checking --- 5 code warnings
Name:
Anonymous2006-11-01 17:20
// Super High Infrastructure Technology Operating System
// v2.01 COMPLETE RELEASEVERSION3 NOT BETA
//
// Theory of operation:
// Programs run best when they have direct access to the hardware
// and don't have to go through an intermediate software solution
// to function. Furthermore, introduction of such a software layer
// (better known as 'kernel', 'BIOS', etc. to primitive minds) only
// serves to introduce bugs while decreasing execution speed. By
// eliminating the entire notion of operating system services, we
// assure maximum performance. Programs are all expected to write
// directly to hardware.
int main(/*@unused@*/ int argc, /*@unused@*/ char* argv[]) {
if (puts("Welcome to ShitOS v2.0") == EOF) {
return 1;
}
return 0;
}
I can't figure how to get rid of the last 2 warnings ;p
Name:
Anonymous2006-11-01 19:32
>>23 // ACTUALLY INCLUDE LIBRARIES YOU USE
#include <stdio.h>
// Super High Infrastructure Technology Operating System
// v2.01 COMPLETE RELEASEVERSION3 NOT BETA
//
// Theory of operation:
// Programs run best when they have direct access to the hardware
// and don't have to go through an intermediate software solution
// to function. Furthermore, introduction of such a software layer
// (better known as 'kernel', 'BIOS', etc. to primitive minds) only
// serves to introduce bugs while decreasing execution speed. By
// eliminating the entire notion of operating system services, we
// assure maximum performance. Programs are all expected to write
// directly to hardware.
int main ( void )
{
if( puts("Welcome to Shit OS") == EOF )
return 1
else
return 0;
}Now your bloatware is compilable C99. It should pass the lint test.