This is one of the most insightful comments I've seen in a long time. It's nice to see such a rational, well-thought-out response to such an irrational remark.
Qualify your statements. I can say that you are the worst posting in the world as well, but without rationale, reason, and specifics, my statement is meaningless. The same applies to your comments about Java and C++.
*THINK* abou things, don't just parrot back what your instructor told you.
printf can be useful sometimes, yes, especially when you want a log of something's operation that you can mull over later. The problem is that there are certain classes of errors that printf cannot catch, e.g., smashing the stack and corrupting the heap. For these, tools like electric fence are invaluable.
Debugggers also allow you to dynamically insepct and *MODIFY* the values of variables, unlike printf. To look at a new variable with printf, you'd need to recompile the source file!
I don't suppose I quality, but I work in a 'war-room' environment for my school's yearbook. We have 30 computers in an arrangement resembling a pitchfork with three prongs. Most computers are visible to everyone, but there are a few private spots available. People generally work quite well, and if someone, e.g., starts up Napster it's obvious. It's private enough, however, so that if someone wants to move to a computer in the corner where he or she can work without being bothered by the the constant din in the area, it can be done. I like it quite much, actually.
The only problem is that we have a lack of space for non-computer activities, which usually results in an ad hoc "meeting area" of a circle of chairs between "prongs".
We don't do any programming work, alas, but the variety of tasks (raw creation, proofreading, article writing, proofreading, tweaking layout, etc. (did I mention proofreading?) approximated the various stages of programming.
I hope that the next devel version of The Gimp will allow script-fus to be undone. That's the only reason I don't like using them much --- they are not completely undoable.
I imagine this would be fairly easy to get around --- just use an entry in the hosts file to redirect it to localhost and use a packet sniffer to capture the packets. Code a small server that plays back whatever data is sent from the server, but with a 1x1 transparent image replacing the usual banner ad.
Let's say you run Linux (I don't know if you do, this is just an example). You use it for legimate purposes, but it's well-known that a few use it for h4x0r1ng other sites. Does that mean you should be prosecuted for using Linux?
Hemos took a lot of liberty with my submission including changing the title as well as cutting of some technical
analysis at the end of my submission.
You might want to try Kuro5hin instead, or in addition, next time. We welcome technical analysis and such.:)
Re:just have an option that says your bandwith typ
on
Gnutella's Challenge
·
· Score: 1
So make the client on the other end provide the information and have the sending client limit the bandwidth. It's still possible to modify, but it's much easier to modify your OWN nefarious client for evil purposes than it is to modify someone else's.
Why is using the filesystem not a suitable solution?
Also, the reason why things use different formats is because they need different things. hosts.allow requires very different information than Apache needs in its configuration files, making a different format (simpler for hosts.allow) necessary.
As for effort --- Why don't *you* code an alternative configuration file parser for sendmail and see how it fares?
Why on earth are all these people saying we need XML files, XML files, XML files, because we need nested, uniform data structures?
Flat files are small, efficient, well-understood, and extremely fast to parse compared XML files. They are also more human-readable, and less prone to error when modifying with a text editor (Oops, I forgot the , now Apache won't work). Programs can verify their own configuration files, and do it well at this moment. Also, when is the last time you heard of a bug in a program's configuration file parser?
There is no inherent reason a flat file cannot have unicode support, either.
As for nested data structures, we already *have* a very well-developed, efficient, and well-understood data store. It's called the filesystem.
Slashdot Mirror
Yes, but a *very*, *very* specialized one with its own redisplay.
goatse is virtually hosted, and so access via the ip address (in any form) will not work alone.
No, just the toolkits. Recently, there was even a patch for XEmacs posted that allowed this to work with it.
This is one of the most insightful comments I've seen in a long time. It's nice to see such a rational, well-thought-out response to such an irrational remark.
Qualify your statements. I can say that you are the worst posting in the world as well, but without rationale, reason, and specifics, my statement is meaningless. The same applies to your comments about Java and C++.
*THINK* abou things, don't just parrot back what your instructor told you.
Fine then. Just prevent opening of windows in onload and onunload while leaving them otherwise functional.
Speaking of Python, I know that ddd supports debugging of Python programs, but I've never been able to make it work. Any ideas?
printf can be useful sometimes, yes, especially when you want a log of something's operation that you can mull over later. The problem is that there are certain classes of errors that printf cannot catch, e.g., smashing the stack and corrupting the heap. For these, tools like electric fence are invaluable.
Debugggers also allow you to dynamically insepct and *MODIFY* the values of variables, unlike printf. To look at a new variable with printf, you'd need to recompile the source file!
As for Linux --- it does have a kernel debugger.
The problem is that you are forced to use it --- with abovenet using it and broadcasting null routes, there is no way in hell you can avoid it.
A war room setup is a room without cubicals or other boundries between people working on the same project.
I don't suppose I quality, but I work in a 'war-room' environment for my school's yearbook. We have 30 computers in an arrangement resembling a pitchfork with three prongs. Most computers are visible to everyone, but there are a few private spots available. People generally work quite well, and if someone, e.g., starts up Napster it's obvious. It's private enough, however, so that if someone wants to move to a computer in the corner where he or she can work without being bothered by the the constant din in the area, it can be done. I like it quite much, actually.
The only problem is that we have a lack of space for non-computer activities, which usually results in an ad hoc "meeting area" of a circle of chairs between "prongs".
We don't do any programming work, alas, but the variety of tasks (raw creation, proofreading, article writing, proofreading, tweaking layout, etc. (did I mention proofreading?) approximated the various stages of programming.
Then you defeat the whole damned purpose of having multiple TLDs.
I hope that the next devel version of The Gimp will allow script-fus to be undone. That's the only reason I don't like using them much --- they are not completely undoable.
I wouldn't be surprised. Their native language is even more obfuscated.
I imagine this would be fairly easy to get around --- just use an entry in the hosts file to redirect it to localhost and use a packet sniffer to capture the packets. Code a small server that plays back whatever data is sent from the server, but with a 1x1 transparent image replacing the usual banner ad.
How the fuck is this a troll? Moderations and cheap $3 crack don't mix.
Nasa did a good job with the Viking probes, and they used 1970s technology. Nasa can do fine, they just need money to do it with.
Virtually any Free program is capable of generated PDF. Just print to Postscript and use ps2pdf.
Let's say you run Linux (I don't know if you do, this is just an example). You use it for legimate purposes, but it's well-known that a few use it for h4x0r1ng other sites. Does that mean you should be prosecuted for using Linux?
This is reminiscient of the Delian and Peloponnesian Leagues, at least in name. :)
IANAM, but...
Considering that approximately 210 miles seperate New York City and Boston...
start train1 = 375
start train2 = 440
x = time for train1 in minutes
(x-65) = time for train2
speed of train1 = 2.083 miles per minute
speed of train2 = 2.333 miles per minute
2.083x + 2.333(x-65) = 210
2.083x + 2.333x - 151.645 = 210
2.083x + 2.333x = 361.645
4.416x = 361.645
x = 81.894248
So the time train1 collided is 81.894248 minutes after it left, or 496.89425 minutes after midnight, or at 7:36
You might want to try Kuro5hin instead, or in addition, next time. We welcome technical analysis and such. :)
So make the client on the other end provide the information and have the sending client limit the bandwidth. It's still possible to modify, but it's much easier to modify your OWN nefarious client for evil purposes than it is to modify someone else's.
Why is using the filesystem not a suitable solution?
Also, the reason why things use different formats is because they need different things. hosts.allow requires very different information than Apache needs in its configuration files, making a different format (simpler for hosts.allow) necessary.
As for effort --- Why don't *you* code an alternative configuration file parser for sendmail and see how it fares?
Why on earth are all these people saying we need XML files, XML files, XML files, because we need nested, uniform data structures?
Flat files are small, efficient, well-understood, and extremely fast to parse compared XML files. They are also more human-readable, and less prone to error when modifying with a text editor (Oops, I forgot the , now Apache won't work). Programs can verify their own configuration files, and do it well at this moment. Also, when is the last time you heard of a bug in a program's configuration file parser?
There is no inherent reason a flat file cannot have unicode support, either.
As for nested data structures, we already *have* a very well-developed, efficient, and well-understood data store. It's called the filesystem.