And the Unix filth did it. Without moving files to trash can. And there is no way to get anything back, because WORSE IS BETTER and the the shitty Unix unlinks everything even when filesystem has enough free space. Why? Why Unix cant die and be replaced with a good OS?
Name:
Anonymous2012-08-29 11:16
``baww my OS did precisely what I told it to do without protest''
>>108 Windows inherited much of the socket API from BSD Unix.
That explains the ``prefixes'' found on the Winsock structure field names. typedef struct in_addr {
union {
struct {
u_char s_b1,s_b2,s_b3,s_b4;
} S_un_b;
struct {
u_short s_w1,s_w2;
} S_un_w;
u_long S_addr;
} S_un;
} IN_ADDR, *PIN_ADDR, FAR *LPIN_ADDR;
typedef struct addrinfo {
int ai_flags;
int ai_family;
int ai_socktype;
int ai_protocol;
size_t ai_addrlen;
char *ai_canonname;
struct sockaddr *ai_addr;
struct addrinfo *ai_next;
} ADDRINFOA, *PADDRINFOA;
`
>geniuses create operation system
>idiot does something stupid with operation system
>therefore, the geniuses are idiots and the idiot is a genius
OP logic.
>>125
That's the browser that stops it, not the operating system. Unix doesn't do anything to prevent idiots like >>1 from writing a browser that does install extensions at the system level, other than allowing such idiots to rm -rf * before they get a chance to do anything really harmful.
>>129
And? Microsoft's browser has no security, because it takes after its OS. And most Windows exploits are done through the browser, so their browser is the weakest link. Therefore, Windows has no fucking security.
Oh, unless you count the Norton nag screen begging you for money.
>>130
It's not a quote, idiot, it's code. Can't you see it's wrapped in a code tag?
Faggot.
Name:
Anonymous2012-08-29 14:48
>>33
The other day I put gas in my Linux car so I can drive it. Then I began driving and the OOG killer blew it up. Whoever invented OOG killers was an idiot. The car should just stop where it was so you can refill the tank or call a tow truck when it runs out of gas.
# Supposing you are using a good Linux distro, now you can stop
# shooting yourself in the foot all of the time.
alias mv='/bin/mv -i'
alias rm='/bin/rm -I'
>>140
Except that these aliases serve a definite purpose: they prevent users from accidentally deleting files. Even experienced users will eventually accidentally use the commands erroneously, and these aliases will protect them from that.
Name:
Anonymous2012-08-29 17:48
>>145
The best alias is a trashcan or an undo feature in the filesystem. Alas Unix has no undo.
Imagine a text editor without an undo feature. That would be the Linux version of Notepad (with a retarded name like GNotepad or KNotepad).
>>150
Unix has safety features. rm has safety features (-i, -I). You can override rm so that it moves files to ~/.trash (if you're that much of a retard). All the more reason >>1 is a retard, because he could have easily implemented the functionality he desires and didn't. How many more safety features do you need?
Name:
Anonymous2012-08-29 18:44
>>151 You can override rm so that it moves files to ~/.trash
When your leg is already sawed off. You can as well pray to God, so he will give you a new one.
Buffer overflows, tedious and slow development, memory leaks, no type safety, #define, no generics, everything is undefined, shitty and exploitable standard libs...I could go on.
>>153
Yeah man, should make those operating systems in Java.
Name:
Anonymous2012-08-29 21:02
>>157
C makes you reinvent the wheel for every single program. Most programmers aren't wheel experts so they make shitty hash tables and reference counting that are slower than professional hashes and GC. Null-terminated strings in C are the cause of the majority of buffer overflows and other bugs. Most of C's descendents (C++, C#, D and Java) don't use them as their main string type because of all the exploits. You might be better off writing an OS in Java even with the JIT because you could spend your time adding features and optimizing the JIT and GC instead of fixing string bugs and buffer overflows.