For someone who "only really started using Photoshop around the end of 2002" I must say you're about the most smug idiot I've ever seen on Slashdot. Congratulations.
For the record:
You don't know anything about Photoshop.
You know even less about the graphic design industry.
Be careful with net send. We used to fire those back and forth at an old job when they decided banning IM software was a good idea. Accidental domain-wide (meaning company-wide in our case) net sends are hilarious, until you send a particularly humiliating one yourself.
Surely there are more important rules than that. How about:
Don't give out the root passwords
Don't give users more access than they need to do their jobs
Disable any unneeded services on a box
Terminate staff who implement undocumented changes with extreme prejudice
I shudder to think of the shape a network must be in when the admins are primarily worried about whether any of the production machines have a compiler on them.
User: I need an account on all the production boxes to run SETI@Home.
Admin: I'm too busy tracking down compilers to set that up. Here's the root password, do it yourself.
How many companies just do downright nice things anymore? Wild speculation aside, until there's a reason for me to feel otherwise, I fucking love you, Google.
I like Kazaa (Lite), and am very technical. Not at all because it's easy, either. It's by far the biggest network around, and that means something when you're looking for more esoteric content. You know, like kiddy porn.
I'd like to see a cross platform solution take off and leave the shady KMD and its almost equally shady hack in the dust, but until that happens it'll remain yet another reason I keep a Windows box on my network (but only with NAT behind OpenBSD).
Re:Opcode depreciation
on
AMD64 Preview
·
· Score: 1
Your comment's parent was making a joke about the use of "depreciated" rather than, what the grandparent likely meant, "deprecated."
To answer you anyway, in this case I believe the deprecated instructions are being emulated with the likely intention of them being removed at some arbitrary point in the future.
I'm of the mind you should use the proper IP range for the network you have. I've got a home network with 6 machines on it at present that sees an extra host or two when friends bring their laptops over and maybe an additional 4-5 when I'm playing with VMware extensively. Work uses 10/8, and even if my network grows tenfold I won't exhaust the space available in 192.168.0/24, so I use that.
Of course, in the event my situation changes, I could re-IP this dinky network in under five minutes. This is a little bit more of a danger for me using 0 than for people who choose a random number as the third octet, but I don't lose sleep over it. Shit happens.
Ultimately the right IP range to use is the one that gets your network working before you get fired (that sounds remarkably similar to something out of the Camel Book). There's always going to be a chance you're going to need to re-IP because of network growth or need to communicate with someone using the same space as you. Make an educated guess at the growth and changing of your network over the next few years and pick the range that fits it, or a larger one if that suits you. Or just use 10/8 and be pretty damn sure you won't run out of space. Of course, if you know you're going to need to hook up with someone else's network, it might not be a bad idea to ask them what they use while you're designing your own network.
Off topic:
The excerpt quoted in his journal does, in fact, point out IE's RFC ignorance w.r.t. HTTP/1.1. The RFC states that the server SHOULD send a Content-type header. This means, if you're a lazy implementer, that your server doesn't HAVE to send this header. In the event that a user agent encounters such a server, and only in that situation, it may attempt to use other methods to determine the content type of the document.
Since IE does this even when the server DOES include a Content-type header, IE's HTTP/1.1 implementation is broken.
Of course, the poster is also wrong, since he states that all web browsers must implement HTTP/1.1. Of course, HTTP/1.1 is not the first iteration of HTTP, and there are many browsers that predate it. They are, however, most assuredly browsers in every sense of the word.
Slashdot Mirror
For the record:
- You don't know anything about Photoshop.
- You know even less about the graphic design industry.
- You smell like shit.
Have a nice day, kid.How about I just shit on your bed and we call it even?
You're just as big of a fucking sheep as the people you're complaining about. Go away, moron.
If it was off, shouldn't it be okay if you give it time to dry out? At the very least the motherboard, CPU, and any expansion cards should be fine.
Don't know for sure about the PSU and disk drives.
I saw that one coming the second I hit submit. I think the damage has been done.
Not really. I've had to call buddies to move my living human corpse several times. Man drinking is great.
Be careful with net send. We used to fire those back and forth at an old job when they decided banning IM software was a good idea. Accidental domain-wide (meaning company-wide in our case) net sends are hilarious, until you send a particularly humiliating one yourself.
Viagra... big... uh huh huh.
Pussy.
What the fuck is Britain?
That's really frightening.
Google has iPods in its pants? Kinky.
I didn't get it from Google. And Google didn't buy you anything! Liar!
"Extramural" is my vocabulary word of the day today. Thanks!
- Don't give out the root passwords
- Don't give users more access than they need to do their jobs
- Disable any unneeded services on a box
- Terminate staff who implement undocumented changes with extreme prejudice
I shudder to think of the shape a network must be in when the admins are primarily worried about whether any of the production machines have a compiler on them. Sounds like a blast.I got a new cell phone.
I take it to mean that Google shares my feelings and wishes to start some sort of long-term relationship.
How many companies just do downright nice things anymore? Wild speculation aside, until there's a reason for me to feel otherwise, I fucking love you, Google.
Why use telnet when you can use netcat? "nc" saves you FOUR WHOLE LETTERS over "telnet". Can you not see that this is the way forward?
I'd mod you up if I hadn't posted the parent comment :P.
- ISPs start blocking ports
- All software uses port 80
- ISPs start using more complex and intrusive filtering that blocks everything that doesn't look like MSIE
- The internet is officially shit
I can't fucking wait.I like Kazaa (Lite), and am very technical. Not at all because it's easy, either. It's by far the biggest network around, and that means something when you're looking for more esoteric content. You know, like kiddy porn.
I'd like to see a cross platform solution take off and leave the shady KMD and its almost equally shady hack in the dust, but until that happens it'll remain yet another reason I keep a Windows box on my network (but only with NAT behind OpenBSD).
Your comment's parent was making a joke about the use of "depreciated" rather than, what the grandparent likely meant, "deprecated."
To answer you anyway, in this case I believe the deprecated instructions are being emulated with the likely intention of them being removed at some arbitrary point in the future.
*pours gasoline all over karma*
On topic (to at least contribute something):
I'm of the mind you should use the proper IP range for the network you have. I've got a home network with 6 machines on it at present that sees an extra host or two when friends bring their laptops over and maybe an additional 4-5 when I'm playing with VMware extensively. Work uses 10/8, and even if my network grows tenfold I won't exhaust the space available in 192.168.0/24, so I use that.
Of course, in the event my situation changes, I could re-IP this dinky network in under five minutes. This is a little bit more of a danger for me using 0 than for people who choose a random number as the third octet, but I don't lose sleep over it. Shit happens.
Ultimately the right IP range to use is the one that gets your network working before you get fired (that sounds remarkably similar to something out of the Camel Book). There's always going to be a chance you're going to need to re-IP because of network growth or need to communicate with someone using the same space as you. Make an educated guess at the growth and changing of your network over the next few years and pick the range that fits it, or a larger one if that suits you. Or just use 10/8 and be pretty damn sure you won't run out of space. Of course, if you know you're going to need to hook up with someone else's network, it might not be a bad idea to ask them what they use while you're designing your own network.
Off topic:
The excerpt quoted in his journal does, in fact, point out IE's RFC ignorance w.r.t. HTTP/1.1. The RFC states that the server SHOULD send a Content-type header. This means, if you're a lazy implementer, that your server doesn't HAVE to send this header. In the event that a user agent encounters such a server, and only in that situation, it may attempt to use other methods to determine the content type of the document.
Since IE does this even when the server DOES include a Content-type header, IE's HTTP/1.1 implementation is broken.
Of course, the poster is also wrong, since he states that all web browsers must implement HTTP/1.1. Of course, HTTP/1.1 is not the first iteration of HTTP, and there are many browsers that predate it. They are, however, most assuredly browsers in every sense of the word.
IE is a browser, just a fairly braindead one.