No, I'm not kidding. If we seperated every single piece, you can suffer what some DB schema's suffer from, over normalization. qmail REALLY suffers from this in its goal of security.
If qmail for instance, since spamassassin doesn't know a thing about the mail system in front of it, it can't tell qmail not to bounce a message from a spammer.. nor can qmail figure this out. So now it bounces mail and then when it can't reach the spamemr, it bounced to postmaster. Joy.
I understand the philosophy of "do one thing and do it well". Do you understand trying to spread yourself too thin? Ever take a look at the redhat configuration scripts? THAT is spreading all of the functionality over too many things, that it is convoluded.
So let sendmail do what it does well.. process mail. Just so long as it doesn't try to do ftp and my other services as well.
It's the case of software once being buggy now being deemed always buggy.
Remember the various bugs with ext3? Well, let's use the same idea. Ext3 will never be as stable as ext2, especially since it corrupts file systems.
Or apple. Apple never will make a fast system, since they always lag behind intel.
Can't we get past these childish prejiduces? Sendmail is pretty friggin cool. At least in sendmail, i can analyze the headers of a message, and if certain ones are present, do one thing vs another. And I don't need a third party util, like procmail to do it.
C++ is a super-set of C, so in theory you can get the same output if you want. However, typically program efficiency is at a higher level than specifically optimized loops etc. - e.g. at the level of algorithm choice. In addition, a good C++ matrix class (for example) can do constant folding, loop unrolling and ensure the memory access order of common matrix/vector operations is appropriate for your CPU (via templates) - that you'd be hard pressed to do in C except for very small projects.
Ah.. but with C++, you have complications like inheritence and polymophism that can make C++ more complex. I'd suspect OOP systems to be a little less efficient memory-wise at least, to be a bit more ineffficent for this dynamic type thing. But then again, what do I know?:)
C is really just glorified assembly language. It only provides a minimal of type checking over most macro assemblers and is about as easy to read. It does have alot of operators to save typing though.
But for embeded systems, where your resources may be very limited, wouldn't a good optimizing compiler do a better job than an OO one?
I'm sure an assembly code monkey could do better than a c junkie, but I wouldn't know the rankings between the compiled code now-a-days as a desktop programmer.
Main Entry: indemnify Pronunciation: in-'dem-n&-"fI Function: transitive verb Inflected Form(s): -fied; -fying Etymology: Latin indemnis unharmed, from in- + damnum damage Date: circa 1611 1 : to secure against hurt, loss, or damage 2 : to make compensation to for incurred hurt, loss, or damage
Now that's not fair for sofware engineers. I'm not talking people who are asked, "write a program that sorts a list". I'm talking, we have about 40 different pieces of data and we need to create an OO solution that can scale.
Backbones should switch over first, proxying ipv4 over ipv6, then propogate downwards.
When it hits users, they'll have an ultimatum. Upgrade within the next 180 days, or j00 are fux0red.
As for the OS and device makers, simply make dhcp check ipv6 first, then fallback to ipv4. That'll be transparent for all the chuckleheads who would ignore the "switch" thing.
Yeah, but problem is, it happens in a cron-like fashion. Midnite every nite forever and ever. With timezone shifts for day light savings, it's not a static number.
I can have cron do a job way before midnite, but if I had to have a job run in all 24 time zones, it could get ugly in running many at jobs at many times.
It'd be great if there was somethign clean to put in cron as...
It's just filled with so many negatievs.. some get confused. It's gramatically laid out right:)
package it. no one more than me.. 'cept for those that hate it more than me, hate doing custom compiles on a system that doesn't have/usr/ports or emerge.
Me and only me, except those that are an exception, hate doing custom compiles on a system which doesn't support it.
Synonymous.. but same order:) Don't you love english?
1. port it to as many systems as possible, even non-targert systems. possibly AIX, old Digital Unix.. you name it.
2. get the werd out. If people know about your package, it could solve a problem somewhere that would get it installed.
3. support it. if you support it, people will keep using it. even if it is initially crappy, you'll get bug fixes and advice.
4. package it. no one more than me.. 'cept for those that hate it more than me, hate doing custom compiles on a system that doesn't have/usr/ports or emerge.
Then you live on w/ your life. If your software is good and fulfills a need, you'll see it get put in.
Nope, I'm dealing with worldwide timezones. If it were simple as puttin in the crontab, run at midnite GMT or midnite, EDT5EST (I've seen that somewhere), that'd pwn. Problem is, cron doesn't support that. Well.. not yet if I don't find an easier solution than "fixing' cron in c.
Right now, the time zone I'm in respects daylight savings. Midnite is gonna shift in the fall, as well as in april. Places like england or or barbados celebrate it at different times or not at all.
Writing a job managing job on top of a job managing job (at on cron) could get messy. Especially so when day light savings hits for various places.
The vulnerability results because the Windows RPC service does not properly check message inputs under certain circumstances. This particular failure affects an underlying Distributed Component Object Model (DCOM) interface, which listens on TCP/IP port 135.
Sounds like we'll haev winnuke2003 sometime soon.:)
<disclaimer>I know that winnuke uses OOB data vs this which does something on the application layer.:P</disclaimer>
Books can be as misleading as any other periodical, website or interview. Code books w/ mistakes, articles with incorrect facts or people just saying wrong stuff.
Trusting where your sorce blindly is just plain bad.
In Soviet America, government just tries to make it illegal to sell the hardcore stuff to kids instead of shutting down the whole industry.
Unconstitutional?
Not really. It's only unconsititutional to countries whose constitution has laws preventing other laws or or decisions to be made or broken. If Afghanistan's law doesn't protect freedom of speech or things pertaining to selling games, then that's that. If they inerpret freedom differently, well.. that's that, eh?
If you weren't spending your spare time in the years 99-00 downloading MP3s like a champ, it's likely you were still in diapers or dancing with wolves. Oh, Napster, we loved ye when.
Or using ftp, irc or usenet. Or not using them at all.
I prefer whole albums myself. Napster never made that easy.
Slashdot Mirror
Just don't put the pasta near the anti pasta. That could be bad.
/rimshot
And you know what, we should also quit the human race. Look at all the mistakes it has made.. just kill everyone in one large felt blast, eh?
So what were you saying about sendmail? Can't change etc?
No, I'm not kidding. If we seperated every single piece, you can suffer what some DB schema's suffer from, over normalization. qmail REALLY suffers from this in its goal of security.
If qmail for instance, since spamassassin doesn't know a thing about the mail system in front of it, it can't tell qmail not to bounce a message from a spammer.. nor can qmail figure this out. So now it bounces mail and then when it can't reach the spamemr, it bounced to postmaster. Joy.
I understand the philosophy of "do one thing and do it well". Do you understand trying to spread yourself too thin? Ever take a look at the redhat configuration scripts? THAT is spreading all of the functionality over too many things, that it is convoluded.
So let sendmail do what it does well.. process mail. Just so long as it doesn't try to do ftp and my other services as well.
The fact it's not sendmail.
It's the case of software once being buggy now being deemed always buggy.
Remember the various bugs with ext3? Well, let's use the same idea. Ext3 will never be as stable as ext2, especially since it corrupts file systems.
Or apple. Apple never will make a fast system, since they always lag behind intel.
Can't we get past these childish prejiduces? Sendmail is pretty friggin cool. At least in sendmail, i can analyze the headers of a message, and if certain ones are present, do one thing vs another. And I don't need a third party util, like procmail to do it.
Ah.. but with C++, you have complications like inheritence and polymophism that can make C++ more complex. I'd suspect OOP systems to be a little less efficient memory-wise at least, to be a bit more ineffficent for this dynamic type thing. But then again, what do I know?
But for embeded systems, where your resources may be very limited, wouldn't a good optimizing compiler do a better job than an OO one?
I'm sure an assembly code monkey could do better than a c junkie, but I wouldn't know the rankings between the compiled code now-a-days as a desktop programmer.
For those who couldn't infer the word..
Indemnify -
Main Entry: indemnify
Pronunciation: in-'dem-n&-"fI
Function: transitive verb
Inflected Form(s): -fied; -fying
Etymology: Latin indemnis unharmed, from in- + damnum damage
Date: circa 1611
1 : to secure against hurt, loss, or damage
2 : to make compensation to for incurred hurt, loss, or damage
And both are equally unwanted. At least in my house. Something about canned processed meat is just evil.
:)
On a second note, isn't ham.. pork? I think it doesn't stand for that.. prolly just "Spiced Ham"'
Now that I've made an insightful and funny comment, lessee if the mod's don't spaz out.
Now that's not fair for sofware engineers. I'm not talking people who are asked, "write a program that sorts a list". I'm talking, we have about 40 different pieces of data and we need to create an OO solution that can scale.
THOSE are the people that are skilled.
Ah, but I can't do that since I need to be able to run the script arbitrarily, say.. if the machine was off overnite.
I like the solution. Too bad i'm gonna have to write a script between each process and cron. well.. tnx.
-s
hmm.. damnit. so someone hit the button already
Not too hard.
Backbones should switch over first, proxying ipv4 over ipv6, then propogate downwards.
When it hits users, they'll have an ultimatum. Upgrade within the next 180 days, or j00 are fux0red.
As for the OS and device makers, simply make dhcp check ipv6 first, then fallback to ipv4. That'll be transparent for all the chuckleheads who would ignore the "switch" thing.
Yeah, but problem is, it happens in a cron-like fashion. Midnite every nite forever and ever. With timezone shifts for day light savings, it's not a static number.
....
I can have cron do a job way before midnite, but if I had to have a job run in all 24 time zones, it could get ugly in running many at jobs at many times.
It'd be great if there was somethign clean to put in cron as...
0 0EDT * * *
I might have to write that a day.
It's just filled with so many negatievs.. some get confused. It's gramatically laid out right :)
/usr/ports or emerge.
:) Don't you love english?
package it. no one more than me.. 'cept for those that hate it more than me, hate doing custom compiles on a system that doesn't have
Me and only me, except those that are an exception, hate doing custom compiles on a system which doesn't support it.
Synonymous.. but same order
1. port it to as many systems as possible, even non-targert systems. possibly AIX, old Digital Unix.. you name it.
/usr/ports or emerge.
2. get the werd out. If people know about your package, it could solve a problem somewhere that would get it installed.
3. support it. if you support it, people will keep using it. even if it is initially crappy, you'll get bug fixes and advice.
4. package it. no one more than me.. 'cept for those that hate it more than me, hate doing custom compiles on a system that doesn't have
Then you live on w/ your life. If your software is good and fulfills a need, you'll see it get put in.
Then you can go onto 5. Profit. or ????. YMMV
Sounds like I'd put a custom cron on top of cron. It'd work nicely in the short term. I might as well "fix" vixie cron to respect my GMT autoritah.
I forsee myself having to do stuff at 3pm GMT or 1pm EDT or 2pm MDT.
Nope, I'm dealing with worldwide timezones. If it were simple as puttin in the crontab, run at midnite GMT or midnite, EDT5EST (I've seen that somewhere), that'd pwn. Problem is, cron doesn't support that. Well.. not yet if I don't find an easier solution than "fixing' cron in c.
Right now, the time zone I'm in respects daylight savings. Midnite is gonna shift in the fall, as well as in april. Places like england or or barbados celebrate it at different times or not at all.
Writing a job managing job on top of a job managing job (at on cron) could get messy. Especially so when day light savings hits for various places.
This sounds like we need the rebirth of sneaker-net. :)
Sounds like we'll haev winnuke2003 sometime soon.
<disclaimer>I know that winnuke uses OOB data vs this which does something on the application layer.
Jokes? Call the national guard! They prolly control them too :( /running in circles panicing
Books can be as misleading as any other periodical, website or interview. Code books w/ mistakes, articles with incorrect facts or people just saying wrong stuff.
Trusting where your sorce blindly is just plain bad.
Not really. It's only unconsititutional to countries whose constitution has laws preventing other laws or or decisions to be made or broken. If Afghanistan's law doesn't protect freedom of speech or things pertaining to selling games, then that's that. If they inerpret freedom differently, well.. that's that, eh?
Or using ftp, irc or usenet. Or not using them at all.
I prefer whole albums myself. Napster never made that easy.