I just have a feeling that "fast" or "quick" will be rather ambiguous ways to describe a network connection for a rather long time
"Quick" is clearly a reference to this feat, which when applied to telecommunications would imply that the routers can deliver one packet as a free action, once per turn. A "fast" connection merely delivers one packet as a move-equivalent action, limiting the router to either two packets per turn (plus one 5" step) or one data packet plus one ICMP/IGMP control packet. AFAIK, the only other way to reliably raise bandwidth is to invest in some Switchports of Speed, which will create a permanent haste effect and thus one additional packet per turn.
According to the article NASDAQ made 10.8 million profit by shorting Facebook in just one of their rule violations.
Yeah, holy shit. No exchange should have trading accounts, least of all the listing exchange; that is a clear conflict of interest. Those profits should be disgorged.
When most of the trades where shorts, and there were few buyers, hell yeah, you are not going to get confirmation of a short sale until some buyer comes in, otherwise they would all be naked short sales.
This demonstrates some solid misunderstanding of what happened on a technical level. Nobody sends trades to the exchange: they send orders. The exchange will acknowledge that orders are accepted by the system, and will send further acknowledgments if the orders execute. An acknowledgement should arrive within milliseconds of placing the order, even if the order does not immediately execute; it will "rest in the book". If you change your mind, you can request to cancel a resting order, but it is possible that by the time your cancel request arrives at the exchange, the order has already been filled (by arbitrageurs, most likely!)
The big institutional buyers did not receive their order acknowledgments... so they sent more orders. Then, several hours later, acknowledgments and executions arrived for both sets of orders! Well, it's extremely dangerous to continue trading in a situation like this, they found out the hard way, and now they're trying to recoup their losses directly from NASDAQ. Note that someone besides NASDAQ must have been on the other side of that execution, and that counterparty probably isn't planning on returning their windfall profits to the exchange so that the exchange can pay out the losers.
The delays caused the investors to lose less money than they would have lost otherwise.
The IPO was around $38, and I heard of friends who had buy market orders executed near $43. Certainly a bad decision on their part, but it seemed that the delays did have some price impact. Other organizations that had orders remain unacknowledged may have submitted additional orders to buy at a high price, without realizing that they were effectively going to get double-filled. Now, it's not NASDAQ's fault that my friends used market orders, or that institutions sent more orders than they actually wanted to get filled... but when the most stable, consistent US equity exchange is having downtime for hours it is hard to justify putting the egg in everyone else's face and not the exchange's own.
What if you buy the new hot ipo and then immediately short the stock?
"Buying the IPO" is just buying stock in the IPO auction. "Shorting" the stock means selling stock which you do not own. So if you buy the IPO and then immediately sell, you're not actually shorting it. This is high-risk day trading, and not an activity recommended for Joe Q. Investor. Not to mention that the high IPO price for FB seems to have been crafted to punish traders expecting an "IPO pop".
Now, suppose you wanted to sell more than you initially bought. Then, the excess sell quantity actually is "short", and you must confirm the ability to borrow the stock from e.g. your broker or some other large institution. If you do not confirm the ability to borrow, then you are shorting "naked" which is not permitted. Because everyone is in this situation on IPO day, you will probably have a hard time finding someone to borrow from without paying out the nose for the "stock loan".
...some people won't take it well and will feel they can take the law into their own hands to express their disapproval. This is a case where handgun concealed carry and 'Stand Your Ground' laws become handy.
I expect the most common response of this sort would be an attempt to destroy the equipment: rip the glasses off of the rude person's face, and then smash them. The legal cost of beating the living shit out of the glass-wearer is too high for most people to consider. But you are advocating for the glass-wearers to carry firearms to defend their legally—but clearly not socially—acceptable behavior? Man, talk about escalation.
This is why I don't understand everyone's obsession with using km/s. 0.0244 km/s is just 24.4 m/s. It's still SI units, it rounds quite nicely to 25 m/s, and it actually puts the numerator on a scale that makes sense on a local (foot traffic) scale.
Your post made me question what tied "noon" to 12:00 in the first place... The Internet says that noon originally meant 15:00, as the ninth hour of daylight (noon ~ nine). Contrast that with "high noon" which refers to the sun being directly overhead.
having everyone use GMT is just retarded -- it doesn't solve any problems.
Upon re-read, I was not clear enough in my original post. My point is that eliminating rule-based "adjustments" to local time representation is more valuable than decimalization, not necessarily that they are worth doing. DST and leap seconds are imposed by organizations, and cannot be pre-encoded into algorithms. Time zones are also similarly "artificial", but the rule for the majority of them is simple. IIRC a few timezones are not hourly, which is weird. But at least if DST is out of the picture, the remaining timezone ruleset would be more consistent than the life of most software.
You can have your lunch at noon, and I'll weigh myself in pounds... but there's really *no* intrinsic value in replacing HH:MM:SS with something base-10. 60 and 12 are way more convenient for fractions.
And then there's tablespoons, pints, quarts, gallons, barrels, and who knows what else.
For (non-pastry!) recipes, I've found it simple enough to just remember that everything is "four"-ish. Four teaspoons in a tablespoon. Four tablespoons in a quarter of a cup. Four cups in a quart. Four quarts in a gallon. Pint is the odd one out, but it's the size of a large glass. For my beer.
I don't ever find myself having to measure/convert barrels. I guess I just don't cook for a big enough family.
I don't mean to pooh-pooh metric by this. Just offering my own experience on managing Imperial conversions in the kitchen.
Speaking of which... how come we haven't stopped using normal seconds and switched to decimal seconds yet?
Get the world off of daylight saving's time, or convince everyone to use GMT. Kill the leap second. Decimalization is pointless if all human–computer time conversions continue to require politically-driven lookup tables.
The term "mixing" sounds less pejorative than "laundering", but the principle is the same: disguise the transfer of wealth. I expect that some extreme pressure will be put on these mixing services as Bitcoins gain traction with nations.
I can only imagine that these people complaining about everyone doing that are themselves the people who do that.
Why would you assume that? "He who smelt it dealt it"? As an observant driver, I notice this phenomenon because it creates a "channel" of other cars moving around me. This is hazardous because it involves a lot of unnecessary passing and lane-changing.
Probably also the same assholes who know there's going to be a long line for the ramp and, rather than getting into it and waiting their turn, stay a lane over and then try to merge in right at the end.
Well, thanks for the vote of confidence. This is something else that I see regularly at I-290 for the offramp to I-90/94. Actually, on this topic, I do have a pet peeve. When "merge ahead" signs are posted for construction, many drivers will merge shortly after the signs. However, if the signs are posted too far in advance of the actual merge, this results in some drivers merging too early, and other drivers seeing the opportunity to "jump the queue" and drive all the way until the merge point. If everyone stayed in their lanes until the merge point, there wouldn't be a moral hazard to jump the queue, and traffic flow would probably be improved due to an orderly "zipper" merge. But once an early merge has started, only an asshole will break the unspoken courtesy-merge and continue straight until the actual merge. All because the signs were so early.
I do, every day I drive in Chicago. "Every 5 seconds" is probably an overstatement, but this is a constant issue both on local roads and on the interstates/highways.
I haven't followed them recently, but is it fair to attribute this to Dreamworks? "The Wrong Trousers" is credited to Aardman Animations and the BBC; I think I discovered them through PBS. All that says about Dreamworks is that they have good taste in claymation inventors.
Yeah, I was hoping that. Sorry, you didn't really deserve a snarky reply, I was just titillated at the idea of a pure-userspace malloc under a multi-tasking OS. But seriously, see my other comment about glibc code. If a program does malloc/free above the size threshold for mmap, then every call does get passed on to the OS. Additionally, if your allocated footprint grows and shrinks by large amounts in LIFO order, you may see excessive sbrk calls. All of this is tunable by mallopt.
Slashdot Mirror
7000 parsecs
"Quick" is clearly a reference to this feat, which when applied to telecommunications would imply that the routers can deliver one packet as a free action, once per turn. A "fast" connection merely delivers one packet as a move-equivalent action, limiting the router to either two packets per turn (plus one 5" step) or one data packet plus one ICMP/IGMP control packet. AFAIK, the only other way to reliably raise bandwidth is to invest in some Switchports of Speed, which will create a permanent haste effect and thus one additional packet per turn.
Yeah, holy shit. No exchange should have trading accounts, least of all the listing exchange; that is a clear conflict of interest. Those profits should be disgorged.
This demonstrates some solid misunderstanding of what happened on a technical level. Nobody sends trades to the exchange: they send orders. The exchange will acknowledge that orders are accepted by the system, and will send further acknowledgments if the orders execute. An acknowledgement should arrive within milliseconds of placing the order, even if the order does not immediately execute; it will "rest in the book". If you change your mind, you can request to cancel a resting order, but it is possible that by the time your cancel request arrives at the exchange, the order has already been filled (by arbitrageurs, most likely!)
The big institutional buyers did not receive their order acknowledgments... so they sent more orders. Then, several hours later, acknowledgments and executions arrived for both sets of orders! Well, it's extremely dangerous to continue trading in a situation like this, they found out the hard way, and now they're trying to recoup their losses directly from NASDAQ. Note that someone besides NASDAQ must have been on the other side of that execution, and that counterparty probably isn't planning on returning their windfall profits to the exchange so that the exchange can pay out the losers.
The IPO was around $38, and I heard of friends who had buy market orders executed near $43. Certainly a bad decision on their part, but it seemed that the delays did have some price impact. Other organizations that had orders remain unacknowledged may have submitted additional orders to buy at a high price, without realizing that they were effectively going to get double-filled. Now, it's not NASDAQ's fault that my friends used market orders, or that institutions sent more orders than they actually wanted to get filled... but when the most stable, consistent US equity exchange is having downtime for hours it is hard to justify putting the egg in everyone else's face and not the exchange's own.
"Buying the IPO" is just buying stock in the IPO auction. "Shorting" the stock means selling stock which you do not own. So if you buy the IPO and then immediately sell, you're not actually shorting it. This is high-risk day trading, and not an activity recommended for Joe Q. Investor. Not to mention that the high IPO price for FB seems to have been crafted to punish traders expecting an "IPO pop".
Now, suppose you wanted to sell more than you initially bought. Then, the excess sell quantity actually is "short", and you must confirm the ability to borrow the stock from e.g. your broker or some other large institution. If you do not confirm the ability to borrow, then you are shorting "naked" which is not permitted. Because everyone is in this situation on IPO day, you will probably have a hard time finding someone to borrow from without paying out the nose for the "stock loan".
Wow, that's a lot of CP!!!
You know, most of PETA's members are made out of meat, too...
I expect the most common response of this sort would be an attempt to destroy the equipment: rip the glasses off of the rude person's face, and then smash them. The legal cost of beating the living shit out of the glass-wearer is too high for most people to consider. But you are advocating for the glass-wearers to carry firearms to defend their legally—but clearly not socially—acceptable behavior? Man, talk about escalation.
Yep, just checked the google for converting 1tsp and 1tbsp each to mL. Well... shit.
This is why I don't understand everyone's obsession with using km/s. 0.0244 km/s is just 24.4 m/s. It's still SI units, it rounds quite nicely to 25 m/s, and it actually puts the numerator on a scale that makes sense on a local (foot traffic) scale.
Your post made me question what tied "noon" to 12:00 in the first place... The Internet says that noon originally meant 15:00, as the ninth hour of daylight (noon ~ nine). Contrast that with "high noon" which refers to the sun being directly overhead.
Upon re-read, I was not clear enough in my original post. My point is that eliminating rule-based "adjustments" to local time representation is more valuable than decimalization, not necessarily that they are worth doing. DST and leap seconds are imposed by organizations, and cannot be pre-encoded into algorithms. Time zones are also similarly "artificial", but the rule for the majority of them is simple. IIRC a few timezones are not hourly, which is weird. But at least if DST is out of the picture, the remaining timezone ruleset would be more consistent than the life of most software.
You can have your lunch at noon, and I'll weigh myself in pounds... but there's really *no* intrinsic value in replacing HH:MM:SS with something base-10. 60 and 12 are way more convenient for fractions.
Add coffee makers and pots to the list. A coffee "cup" is 6oz.
For (non-pastry!) recipes, I've found it simple enough to just remember that everything is "four"-ish. Four teaspoons in a tablespoon. Four tablespoons in a quarter of a cup. Four cups in a quart. Four quarts in a gallon. Pint is the odd one out, but it's the size of a large glass. For my beer.
I don't ever find myself having to measure/convert barrels. I guess I just don't cook for a big enough family.
I don't mean to pooh-pooh metric by this. Just offering my own experience on managing Imperial conversions in the kitchen.
Get the world off of daylight saving's time, or convince everyone to use GMT. Kill the leap second. Decimalization is pointless if all human–computer time conversions continue to require politically-driven lookup tables.
The term "mixing" sounds less pejorative than "laundering", but the principle is the same: disguise the transfer of wealth. I expect that some extreme pressure will be put on these mixing services as Bitcoins gain traction with nations.
Why would you assume that? "He who smelt it dealt it"? As an observant driver, I notice this phenomenon because it creates a "channel" of other cars moving around me. This is hazardous because it involves a lot of unnecessary passing and lane-changing.
Well, thanks for the vote of confidence. This is something else that I see regularly at I-290 for the offramp to I-90/94. Actually, on this topic, I do have a pet peeve. When "merge ahead" signs are posted for construction, many drivers will merge shortly after the signs. However, if the signs are posted too far in advance of the actual merge, this results in some drivers merging too early, and other drivers seeing the opportunity to "jump the queue" and drive all the way until the merge point. If everyone stayed in their lanes until the merge point, there wouldn't be a moral hazard to jump the queue, and traffic flow would probably be improved due to an orderly "zipper" merge. But once an early merge has started, only an asshole will break the unspoken courtesy-merge and continue straight until the actual merge. All because the signs were so early.
I do, every day I drive in Chicago. "Every 5 seconds" is probably an overstatement, but this is a constant issue both on local roads and on the interstates/highways.
I haven't followed them recently, but is it fair to attribute this to Dreamworks? "The Wrong Trousers" is credited to Aardman Animations and the BBC; I think I discovered them through PBS. All that says about Dreamworks is that they have good taste in claymation inventors.
Be careful with that wildcarding! Are you positive that no Starcraft movie has ever been produced?
If you don't like the ticket price or the popcorn, why not just wait to rent or stream it at home?
Yeah, I was hoping that. Sorry, you didn't really deserve a snarky reply, I was just titillated at the idea of a pure-userspace malloc under a multi-tasking OS. But seriously, see my other comment about glibc code. If a program does malloc/free above the size threshold for mmap, then every call does get passed on to the OS. Additionally, if your allocated footprint grows and shrinks by large amounts in LIFO order, you may see excessive sbrk calls. All of this is tunable by mallopt.
My copy of malloc calls sbrk and mmap/mremap/munmap—all kernel functions. How does yours get more virtual address space?
While you're at it, please denigrate PostgreSQL as well.