It's not all about you. I don't tweet much, but I find the service invaluable (though also potentially distracting) as a means of "keeping up with what's going on".
By the time the 6 O'clock news rolls around each evening, there's nothing on there I haven't already learned. Extreme weather alert? Tweeted. Sure, by looking at the "live feed" I can see that 80% of the tweets are moronic drivel, so I don't follow morons. I follow people I was already interested in before, and through that learn of other people who say things I follow interesting (thanks to people I follow "re-tweeting" them).
Once upon a time I couldn't see what all the fuss was about and found humour in the name, but when it hit me what you can use it for it was amazing. I now only miss tweets of people I follow when I'm asleep.
How is the page rendered? Surely if it's some sort of a bitmap then exponentially more space will be taken. A slashdot discussion page is a particularly large HTML doc on its own, being rendered before passing over the network would surely make it huge. What am I missing here?
Thanks for that. The other day I suggested to someone here he keeps a "/bin/cat swear jar" on his desk. Whenever you use/bin/cat for something other than concatenating files, but a dollar in the jar.
His crime was cat *.txt | grep "somePhrase" and wanted to know he could report which file and line number the matches were found on. First suggestion was get rid of the damn cat!
When you made these hypothetical beer-posts, did you have any expectation or guarantee that they would vanish in the first place? What if the BBS you posted them on never went offline, and was still available (presumably over the Internet) today? Would this situation be any different to you?
Exactly. Even with the flattest of flat panels, lenses themselves have their own distortions that need to be corrected anyway. It's a well-understood and already-solved problem. OCR has to deal with a hell of a lot more problems than barrel distortion.
No, some old serial controllers really were quite bad, and only had a single byte buffer. This means they generate an interrupt for every single byte received, this byte needs to be fetched immediately so the next byte to arrive won't overflow the buffer (fortunately this condition is detected too). Same deal for sending, throw a byte in the buffer, wait for an interrupt asking "Next one!", repeat.
Continuous transfer tended to be quite CPU intensive.
I'd use cpio since many versions of tar had a rather dismal maximum pathname length, and might choke when tarring the entire filesystem. Found this out the hard way, not that I hadn't been warned before.
Given the shocking state of 802.11 implementations, I don't use spaces or symbols in my SSIDs just to save myself trouble when some mongrel device comes along with some special requirements.
I don't have an IE handy to test, but I'm guessing it behaves like other browsers, and throws up a dialog at that point saying something to the effect of "Where would you like to save this bookmark?"
Nonsense! This is Slashdot, we believe in Darwin, and everybody who's so much as got something stuck between their teeth once is an Idiot and need to be weeded from the gene-pool immediately.
Regarding moderation: Parent is absolutely correct. If you're a big free-speech believer, or just want to see the whole Slashdot, simply read at -1, and ignore moderation (I do). Ideally all the spam/goatse would be at -1, and offtopic or particularly rabid posts wouldn't go below zero, but that's apparently unattainable.
I agree, and have always preferred to listen to Dark Side in its entirety, and need no convincing. I was only taking issue with the suggestion that vinyl copy of it didn't have any "metadata" separating the tracks. I argued that it does, in as much as vinyl records can carry metadata - in the form of wider pitches between grooves to permit visual identification and ease of needle placement. Sure, there's no guarantee the needle will land on a silent part, (you'll want to [cross]fade the song in anyway) but the media assists identification of separate tracks - contrary to the person I was responding - just like in an album full of silent gaps.
There's no easy way in to The Great Gig in the Sky, but sometimes that's all I want to hear.
That's not security, that's policy. The iPhoneOS Public API provides you with all the power you need make a 'nasty' application with underlying behaviour that completely eludes these scans.
Slashdot Mirror
It's not all about you. I don't tweet much, but I find the service invaluable (though also potentially distracting) as a means of "keeping up with what's going on".
By the time the 6 O'clock news rolls around each evening, there's nothing on there I haven't already learned. Extreme weather alert? Tweeted. Sure, by looking at the "live feed" I can see that 80% of the tweets are moronic drivel, so I don't follow morons. I follow people I was already interested in before, and through that learn of other people who say things I follow interesting (thanks to people I follow "re-tweeting" them).
Once upon a time I couldn't see what all the fuss was about and found humour in the name, but when it hit me what you can use it for it was amazing. I now only miss tweets of people I follow when I'm asleep.
[pinky to mouth] 0x174876E800 dollars!
Fair enough - I guess I vastly underestimated the amount of markup included if compressed bitmaps really are viable.
How is the page rendered? Surely if it's some sort of a bitmap then exponentially more space will be taken. A slashdot discussion page is a particularly large HTML doc on its own, being rendered before passing over the network would surely make it huge. What am I missing here?
Context. I read posts in the context of the post to which they are replying. Go back, read your parent, then your post. You'll see.
This is Slashdot. You don't say 10x, you must say an order of magnitude, OK?
That you equate non-programmer with non-contributor makes it quite easy to guess what you are.
in Gnome, in this order "Restart", "Cancel", "Shut Down".
His crime was cat *.txt | grep "somePhrase" and wanted to know he could report which file and line number the matches were found on. First suggestion was get rid of the damn cat!
When you made these hypothetical beer-posts, did you have any expectation or guarantee that they would vanish in the first place? What if the BBS you posted them on never went offline, and was still available (presumably over the Internet) today? Would this situation be any different to you?
Exactly. Even with the flattest of flat panels, lenses themselves have their own distortions that need to be corrected anyway. It's a well-understood and already-solved problem. OCR has to deal with a hell of a lot more problems than barrel distortion.
Nitpicky, but you mean ISA slots. The ISA bus is alive and kicking, all PC-compatible machines have them.
Probably being born in the mid 90's or something. Consider yourself lucky he didn't recommend mkisofs | cdrecord
I should add that on asynchronous serial links buffer underrun when sending is not the disaster that buffer overrun when receiving is.
Continuous transfer tended to be quite CPU intensive.
I'd use cpio since many versions of tar had a rather dismal maximum pathname length, and might choke when tarring the entire filesystem. Found this out the hard way, not that I hadn't been warned before.
XON/XOFF are sent inband, you're thinking of RTS/CTS which have their own separate conductors in the cable.
Given the shocking state of 802.11 implementations, I don't use spaces or symbols in my SSIDs just to save myself trouble when some mongrel device comes along with some special requirements.
I don't have an IE handy to test, but I'm guessing it behaves like other browsers, and throws up a dialog at that point saying something to the effect of "Where would you like to save this bookmark?"
Nonsense! This is Slashdot, we believe in Darwin, and everybody who's so much as got something stuck between their teeth once is an Idiot and need to be weeded from the gene-pool immediately.
Regarding moderation: Parent is absolutely correct. If you're a big free-speech believer, or just want to see the whole Slashdot, simply read at -1, and ignore moderation (I do). Ideally all the spam/goatse would be at -1, and offtopic or particularly rabid posts wouldn't go below zero, but that's apparently unattainable.
Tell that to the Lomography crowd.
No. Yes: computers.
There's no easy way in to The Great Gig in the Sky, but sometimes that's all I want to hear.
That's not security, that's policy. The iPhoneOS Public API provides you with all the power you need make a 'nasty' application with underlying behaviour that completely eludes these scans.