200 bytes? Here, we have a stream of full-MTU packets making frames of around megabit each.
Those "unaware repeaters" are indeed frequent on optical links, but they don't count as hops. Usually, you measure the number of hops as the number of machines capable of routing that reduce TTL by one and may return pings.
12ms -- for every single hop. Sure, the routers upstream have a better link than you so it will be less than 12 for those hops, but you still suffer a separate delay for every routers on the way.
Let's assume you have a hop where distance/c = 10ms and packet's length/bandwidth = 10ms. This means, the head of a packet arrives in 10ms, the tail in 20. No routers or bridges save for the most unaware repeaters will handle the packet until it arrives completely. Only then they will examine it and start sending it forward.
Thus, the final latency will be: a) distance/c, plus b) time spent in queues, plus c) time needed for the bodies of packets to arrive.
To reduce a), you need to be closer to your destination. To reduce b), you need an ISP who oversells less. To reduce c), you need bandwidth on all hops.
Unless MS is starting to give away those licenses for free now ?
There's a crapload of filesystems better than NTFS that even Microsoft can use freely. Except, you know, that would 1. be an admission there is a world outside Microsoft, 2. lessen the stranglehold they work so hard to maintain, and 3. do something good for the customers, and they can't have anything like that.
Make a _directory_ named autorun.inf, this works on FAT as well. Since 99.9% USB sticks use FAT -- and most devices don't understand anything else -- moving to NTFS (or a more sane filesystem) is usually not an option.
Too bad, the whitelist is retardedly narrow. I cannot see any reason to not allow every single printable character -- if you care for terminally broken browsers, perhaps except RTL, but that's it.
It's only certain control characters that can cause mess like that.
Well, one of Polish kings, Leszek Bialy, sent the pope an opinion of his medics that claimed that he suffers from an allergy to water, and, because during a campaign in Palestine an uninterrupted supply of beer or wine would be hard to assure, he can't go to the crusade there.
By the original definition, you're right. Too bad, in most popular usage, this term's meaning was extended to include ephebophilia -- the latter term being nearly completely unknown by the general public. Heck, it is lacking from Firefox' spell checker for example.
Others have refuted your claim about "selective" reading, so let's go talk about you hating "bigotry". How is condeming an unnatural (even if largely harmless) activity bad if the politically correct group ("liberal" in a perverted sense of that word) you promote declares group marriage and pedophilia evil, often in the same sentences they bash homophobia?
Group marriage is fully natural, and encouraged by some major cultures. It is not really compatible with the western world, since allowing 1:4 marriages but not 4:1 or 2:2 would be inconsistent and discriminative, but unlike homosexualism it does not hamper biological functions in any way.
Some parts of pedophilia, namely those where the younger partner is between puberty and the "legal age of consent" is fully natural too. In fact it's the current law what is a perversion -- it bans a fully healthy behaviour and punishes it harsher than murder. Too bad, it would be unwise to change that law without amending related parts as well -- the root issue comes from people below 18 being "children" without being allowed to take on any responsibility and then suddenly fully grown at then magic age. If they are sheltered from any "evils" like pornography or reading about violence, how are they supposed to handle these issues when they are adult?
So uhm, "homosexualism good, group marriage bad". I hope you can see what's wrong here.
As far as readable languages go, you picked something that's actually far worse than TeX. I wouldn't really count XML as "human readable" -- I mean, back in the day I once played with a boot virus and changed it to load at 0xB800:0 so I could literally see its running code and variables, but neither that nor XML is what one would choose to read.
In this case, the one who wrote that. And I don't mean just readability by novices.
*(&z + z) -- unless it's C++, this makes sense only for referring to the zth next variable after z. Like: int z, a, b, c; -- z=1 will select a, z=2 will select b, z=3 will select c. In an old compiler, this will always work. In an optimizing one, it's damn likely to break.
Mixing dec and hex numbers, and writing down constants for bit operations using decimal numbers in general is prone to mistakes. So is using addition in an expression that consist mostly of bit operations, you want | there instead.
0x8F is a complex mask, it definitely should be a #define with a name. There's nothing wrong with masks like 0x7F or 0x1F, but for 0x8F, it's not obvious enough.
~(~t11) -- uhm, what's the point?
With these issues fixed, though, with a bit of comments such a code isn't that bad.
You mean, "altavista.com"? That's a new-fangled URL. Back in the day, the address was "altavista.digital.com", because a gimmick like internet search certainly wasn't important enough to warrant a domain on its own.
That ugly search bar thing merely wastes screen space. I just type "g whatever" -- by default, the keyword is "google" but you can change it to just "g".
It's especially useful if you want to search for something else -- like, going on to a given bug entry (in Debian's BTS / your project's Mantis / whatever) can be done with just "bts 213361". You could do that with the search bar, yeah, but it requires several clicks every single time.
There's absolutely no reason to not allow every single printable character, perhaps excluding RTL or combining chars if you're paranoid. A white/blacklist made by hand would be counterproductive, character classification functions are there for a reason.
Actually, pinyin romanisation rules don't even vaguely resemble the meaning letters have in ANY language that uses the Latin script. On the other hand, Wade-Giles is based on English. Thus, it's the PRC spelling what's abuse of Latin letters, not the old version.
That's why we need strong Intellectual Property protection.
Just think of the real true thing, hieroglyphs, provided by the clergy of Amon, available through scribes for Reasonable And Non-Discriminatory fees. Don't accept counterfeit alphabets!
Patent protection would have to be extended to 3000 years, but we're getting there.
Slashdot Mirror
200 bytes? Here, we have a stream of full-MTU packets making frames of around megabit each.
Those "unaware repeaters" are indeed frequent on optical links, but they don't count as hops. Usually, you measure the number of hops as the number of machines capable of routing that reduce TTL by one and may return pings.
12ms -- for every single hop. Sure, the routers upstream have a better link than you so it will be less than 12 for those hops, but you still suffer a separate delay for every routers on the way.
Let's assume you have a hop where distance/c = 10ms and packet's length/bandwidth = 10ms. This means, the head of a packet arrives in 10ms, the tail in 20. No routers or bridges save for the most unaware repeaters will handle the packet until it arrives completely. Only then they will examine it and start sending it forward.
Thus, the final latency will be:
a) distance/c, plus
b) time spent in queues, plus
c) time needed for the bodies of packets to arrive.
To reduce a), you need to be closer to your destination. To reduce b), you need an ISP who oversells less. To reduce c), you need bandwidth on all hops.
And with the bandwidth this service uses, you'll hit your ISPs "unlimited" cap in what, 6 hours? A day?
Well, they provided the reason. Ossetians used Russian-given artillery and were guided by Russian officers.
It's like as if the US planted WMDs into Iraq themselves and organized personnel to teach Saddam's folks how to use them.
US can invade Afghanistan and Iraq while Russia can't invade Georgia
Can't? They did, and for about as good reason as the US did invade Iraq for.
The Wayback Machine will purge the record the very moment you slap a robots.txt. Yes, even retroactively. Yes, even if some squatter took your domain.
This policy makes them worthless for recovering old versions the web page author's actively wants to hide.
Unless MS is starting to give away those licenses for free now ?
There's a crapload of filesystems better than NTFS that even Microsoft can use freely. Except, you know, that would 1. be an admission there is a world outside Microsoft, 2. lessen the stranglehold they work so hard to maintain, and 3. do something good for the customers, and they can't have anything like that.
Make a _directory_ named autorun.inf, this works on FAT as well.
Since 99.9% USB sticks use FAT -- and most devices don't understand anything else -- moving to NTFS (or a more sane filesystem) is usually not an option.
In fact, on old systems with a graphics card it is significantly faster than the traditional way of redrawing windows.
Why? Because:
1. the gfx card can do part of the work
2. all windows are already drawn and kept in the graphic card's memory
But the domains are controlled by Chinese government organizations, so dissidents and emigrants are not going to use them.
Too bad, the whitelist is retardedly narrow. I cannot see any reason to not allow every single printable character -- if you care for terminally broken browsers, perhaps except RTL, but that's it.
It's only certain control characters that can cause mess like that.
Well, one of Polish kings, Leszek Bialy, sent the pope an opinion of his medics that claimed that he suffers from an allergy to water, and, because during a campaign in Palestine an uninterrupted supply of beer or wine would be hard to assure, he can't go to the crusade there.
Just wait until Google says it can't unbundle Chrome from the Chrome OS...
Well, then how would you explain why it works on Wine?
By the original definition, you're right. Too bad, in most popular usage, this term's meaning was extended to include ephebophilia -- the latter term being nearly completely unknown by the general public. Heck, it is lacking from Firefox' spell checker for example.
Others have refuted your claim about "selective" reading, so let's go talk about you hating "bigotry". How is condeming an unnatural (even if largely harmless) activity bad if the politically correct group ("liberal" in a perverted sense of that word) you promote declares group marriage and pedophilia evil, often in the same sentences they bash homophobia?
Group marriage is fully natural, and encouraged by some major cultures. It is not really compatible with the western world, since allowing 1:4 marriages but not 4:1 or 2:2 would be inconsistent and discriminative, but unlike homosexualism it does not hamper biological functions in any way.
Some parts of pedophilia, namely those where the younger partner is between puberty and the "legal age of consent" is fully natural too. In fact it's the current law what is a perversion -- it bans a fully healthy behaviour and punishes it harsher than murder. Too bad, it would be unwise to change that law without amending related parts as well -- the root issue comes from people below 18 being "children" without being allowed to take on any responsibility and then suddenly fully grown at then magic age. If they are sheltered from any "evils" like pornography or reading about violence, how are they supposed to handle these issues when they are adult?
So uhm, "homosexualism good, group marriage bad". I hope you can see what's wrong here.
As far as readable languages go, you picked something that's actually far worse than TeX. I wouldn't really count XML as "human readable" -- I mean, back in the day I once played with a boot virus and changed it to load at 0xB800:0 so I could literally see its running code and variables, but neither that nor XML is what one would choose to read.
If anti-intellectualism is what is required to blend well with the society, I say: fuck the society.
In this case, the one who wrote that. And I don't mean just readability by novices.
*(&z + z) -- unless it's C++, this makes sense only for referring to the zth next variable after z. Like: int z, a, b, c; -- z=1 will select a, z=2 will select b, z=3 will select c. In an old compiler, this will always work. In an optimizing one, it's damn likely to break.
Mixing dec and hex numbers, and writing down constants for bit operations using decimal numbers in general is prone to mistakes.
So is using addition in an expression that consist mostly of bit operations, you want | there instead.
0x8F is a complex mask, it definitely should be a #define with a name. There's nothing wrong with masks like 0x7F or 0x1F, but for 0x8F, it's not obvious enough.
~(~t11) -- uhm, what's the point?
With these issues fixed, though, with a bit of comments such a code isn't that bad.
You mean, "altavista.com"? That's a new-fangled URL. Back in the day, the address was "altavista.digital.com", because a gimmick like internet search certainly wasn't important enough to warrant a domain on its own.
That ugly search bar thing merely wastes screen space. I just type "g whatever" -- by default, the keyword is "google" but you can change it to just "g".
It's especially useful if you want to search for something else -- like, going on to a given bug entry (in Debian's BTS / your project's Mantis / whatever) can be done with just "bts 213361". You could do that with the search bar, yeah, but it requires several clicks every single time.
There's absolutely no reason to not allow every single printable character, perhaps excluding RTL or combining chars if you're paranoid. A white/blacklist made by hand would be counterproductive, character classification functions are there for a reason.
Actually, pinyin romanisation rules don't even vaguely resemble the meaning letters have in ANY language that uses the Latin script. On the other hand, Wade-Giles is based on English. Thus, it's the PRC spelling what's abuse of Latin letters, not the old version.
That's why we need strong Intellectual Property protection.
Just think of the real true thing, hieroglyphs, provided by the clergy of Amon, available through scribes for Reasonable And Non-Discriminatory fees. Don't accept counterfeit alphabets!
Patent protection would have to be extended to 3000 years, but we're getting there.