Then, the sync should be conditional on the OS it is running on, and disabled on Linux.
I'm not sure if this is still relevant, but at one point it was the major culprit for excess syncs and it is indeed configurable. It's probably more informative to read the bug comments and see the diff than for me to paraphrase.
Fix Firefox? Why does it "need" to do a lot of syncs?
Sync (or fsync) is the way to ensure that files are committed to disk and not just cached somewhere. This is a precondition for reliable "restore session" and similar functionality. However, application developers cannot rely on the OS to sync data in the background, because e.g. on a laptop where frequent disk access is both expensive (battery life) and risky (physical motion), the OS will cache as much as possible. If FF did not sync, the OS might delay writes for hours, which means a computer crash leads to lost hours of browsing history for the user. It doesn't sound like a big deal, but I can tell you that it is infuriating as a user to see a browser say, "whoops, I lost your tabbed windows, hope you weren't using the WWW for anything important!". Not having looked at the source myself, I don't know if it's possible to optimize FF's sync behavior; but I do know that it's impossible to eliminate it.
Buyers who subscribed for the IPO and sold yesterday lost 1-2% for the transaction. My bet is: FB, banks, traders, stock exchange won, people screwed.
Buyers who expected to sell at a profit before the end of the day are day traders. If that's who you mean by "people" then it's hard to call them screwed. They knowingly stepped into the ring with professionals, gambled, and lost. Now, if by "people" you mean longer-term investors, then they are all holding their positions still and a $5 one-day loss on paper is meaningless.
Now, I do agree with you that FB, banks, and the stock exchange won without a doubt. FB got publicity and a big fat market valuation, banks got their pound of flesh from the IPO, and the stock exchanges got their pound of flesh from the high trading volume.
THen there's the 2.0 Dolby Stereo mix. This is the one you want, if you want it to sound like it did in a theater. This one's uncompressed.
This is interesting; I have always assumed that the stereo mix was just a mixdown of the surround mix, and I've not done any A/B tests. Do you know if this is a common phenomenon?
make a system that amplifies dialog to the same level as everyfucking thing else in the movie so I dont have to constantly fiddle with my remote.
Audyssey is one system that does this, but I'm sure there are others. If I crank my receiver's "dynamic volume" to "heavy" it substantially reduces the dynamic range, which is good for Michael Bay movies while the baby sleeps. It also destroys any music that has dynamic range, so I'm quite glad to have source material with a wide dynamic range and an optional compressor in my playback device.
I wish they'd just leave HDMI level audio in uncompressed PCM. But then we wouldn't need to license these Dolby decoders.
We'd also need to reserve more space for audio on our discs. Dolby's and other encoding schemes compress audio data. This factors into bandwidth as well: IIRC, my PS3 sends "bitstream" audio data to my receiver because the optical cable can't handle 5.1 LPCM at the source frequency. HDMI cables are higher-bandwidth than optical, but it was not an option for me.
It's also convenient to use the Dolby matrix-encoded audio to get surround sound out of plain old RCA cables. I discovered this with Guitar Hero on my Wii, and the fact that Nintendo and my receiver's manufacturer both payed Dolby meant that I could get surround sound without switching out the entire audio path.
But yeah.. TrueHD is probably overkill. I expect the room to have a bigger impact than a lossless codec for all but the most anal home theaters.
Can you imagine the power [a hacker] holds ? Whatever the terrorists will do, he can achieve the same or even more than that with just the click of a button.
I'm curious, how would you go about proving this? Occam's Razor comes to my mind: positively identify that the common Santa Claus story is a fiction, and then deduce that a coincidentally identical Real Santa Claus is extremely unlikely, given the rarity of individuals that are similar and well-known. But that's not proof by a long shot.
In odds, it's an exact 50/50 split. There either is, or is not a creator.
Ask yourself, if it's a 50/50 split why would you not want people to hear what the odds are for and learn to think about the answer for themselves?
It is a fallacy to assume that because two possibilities exist that they must be equally probable. Nobody on earth knows the odds on this sort of a "bet". It is also a mistake to award equal effort or weight to all possibilities in an investigation, since there are innumerable dead-ends. It makes sense to expose people to logic, the scientific method, and mythology (religious or otherwise). It does not make sense to present these topics as competitors, because comprehension of scientific discovery and processes does not preclude personal faith.
If you have any money invested in a 401K there is a chance you own stock in big oil or other evil corporations. It happens.
Yup, I did some digging in my 401K ETF holdings and discovered that I owned a little bit of Halliburton. Whoops! I did not unwind the ETF position but I was able to redirect new investments to other funds with similar "risk profiles" but with holdings that I was more interested in promoting. Big oil, OTOH, is probably a bit more difficult to avoid. A quick check shows that Exxon and Chevron are in the top 10 for SPY.
The way code is split out across multiple files is rarely done in a way optimal for recompilation speed.
Both libpthread and libncurses are split out with very few externally-visible functions defined per translation unit. They are very close to being optimal on my platform (Linux, x86_64) in that static linkage will include only the translation units required and not the entire archive file. I'm sure that there are many other C libraries like this (C++ probably not as much due to templates and inline class member functions).
They didn't ban it. It just happens that the restrictions in GPL is incompatible with their terms of service. If Stallman fixes the bugs in GPL...
Since the GPL existed before the App Store and is an extremely popular software license, it is logical to conclude that Apple knowingly crafted terms of service that excluded GPL compliance. Whether this is intentional exclusion or simply collateral damage is unknown, but the onus is on Apple and not the FSF/RMS.
Many people don't like florescents simple because the color temperature isn't as close to incandescent
That is like complaining that CDs lack the hiss or distortion of tape or LPs. Why is yellow light a good thing, just because 100-year-old technology makes for yellow lamps?
In the context of the GP's incorrect statement, your response makes sense. However, the problem that people find with fluorescent lighting is typically not the color temperature but the spectrum (measured as CRI, where 80 is most cheap CFL bulbs and 100 is the sun). There are many ways to produce light that looks "white" to our eyes, but light with an uneven spectrum will look weird when it reflects off of any surface that is not also white. Think about shining a red light on green plant leaves: the plants look black, because the spectrum of the light multiplied by the reflectance of the leaf (think SIMD or vector math) is very dark (close to a 0-vector).
So in actuality, it's not people complaining because they want their warm (red/yellow) color and tape hiss back; it's because fluorescence produces very weird colors in real-world settings which appear very unnatural in comparison with the sun.
And, incidentally, current CFLs have no startup time, at least not one that humans can notice.
My Westinghouse PAR38s* all take about a second to start up. It's not continuous, they hit some darker pinkish color in one step and then their final color in the next step. The startup time appears to decrease as the bulbs "break in" as well, but they're never "instant-on" the way that most other lights appear to be (CFL or not).
*bought new a year ago, which qualifies for most definition of "current"**
Nobody outlawed incandescents. Laws were made for lighting to meet certain energy usage requirements.
Needlessly pedantic. If laws are passed that make it impossible for incandescent lights to meet energy-efficiency standards, then incandescent light bulbs have been de facto outlawed.
It's got an OO system that no other language uses.
Lua's OO system is pretty similar. Not that I view this as a good thing in general, but there is a certain beauty in keeping a language as simple as possible and foisting the boilerplate onto library designers.
...the "day trader" mentality causes the price to go spiking up.
It's not just mentality, it's how the market rules are laid out. The possibility of short selling keeps prices from spiking up regularly (effectively, the short sellers punish overeager buyers). Short-selling a stock is very difficult within its first 30 days, meaning that most otherwise-market-neutral traders end up with a long bias on this stock. Of course the stock jumps up as a result. Now, the "IPO mentality" exacerbates this phenomenon, but the long bias would exist even if we were all emotionless robots (or "rational investors").
Whenever Facebook reports user numbers, they report *active* users, which they define as using the site once in the last 30 days.
I believe that visiting a site with "like" buttons counts as FB activity as long as they can see your login cookie. This effectively lowers the bar of activity to "all users who do not deliberately avoid us" (via logging out, switching browsers, blocking CIDRs, etc.)
It's not clear why for some reason you changed ["fiduciary responsibility to their share holders to save money and maximize return on their investments"] to: "fiduciary responsibility to maximize tax avoidance".
It should be clear; the implication I intend is that maximizing tax avoidance is a requirement for maximizing ROI. You could successfully argue about local vs. global maxima: that the maximum ROI may happen to not coincide with the maximum tax avoidance (because it may require changing business operations); but that's a substantial nit to pick.
Employees DO have a fiduciary responsibility to their employer (the shareholders).
That they do; but the fiduciary responsibility can conflict with ethical considerations. I also believe that laws representing the prevailing majority opinion will naturally lag behind ethics, so there will always be gray areas with legal-but-unethical actions and illegal-but-ethical actions.
Well in this case it was both legal and ethical.
Publicly traded companies have a fiduciary responsibility to their share holders to save money and maximize return on their investments. Therefore it is the right thing to do.
I would argue that the conclusion does not follow, and that a fiduciary responsibility to maximize tax avoidance is necessarily unethical. Put another way, the duty to shareholders should not trump the duty to society at large.
nobody care about your references if they are not commit id on github
That's an absurd thought. Plenty of code is written and not open-sourced or otherwise distributed to the public. This will remain true until we reach the Star Trek level of technology and culture.
Slashdot Mirror
I'm not sure if this is still relevant, but at one point it was the major culprit for excess syncs and it is indeed configurable. It's probably more informative to read the bug comments and see the diff than for me to paraphrase.
Sync (or fsync) is the way to ensure that files are committed to disk and not just cached somewhere. This is a precondition for reliable "restore session" and similar functionality. However, application developers cannot rely on the OS to sync data in the background, because e.g. on a laptop where frequent disk access is both expensive (battery life) and risky (physical motion), the OS will cache as much as possible. If FF did not sync, the OS might delay writes for hours, which means a computer crash leads to lost hours of browsing history for the user. It doesn't sound like a big deal, but I can tell you that it is infuriating as a user to see a browser say, "whoops, I lost your tabbed windows, hope you weren't using the WWW for anything important!". Not having looked at the source myself, I don't know if it's possible to optimize FF's sync behavior; but I do know that it's impossible to eliminate it.
Buyers who expected to sell at a profit before the end of the day are day traders. If that's who you mean by "people" then it's hard to call them screwed. They knowingly stepped into the ring with professionals, gambled, and lost. Now, if by "people" you mean longer-term investors, then they are all holding their positions still and a $5 one-day loss on paper is meaningless.
Now, I do agree with you that FB, banks, and the stock exchange won without a doubt. FB got publicity and a big fat market valuation, banks got their pound of flesh from the IPO, and the stock exchanges got their pound of flesh from the high trading volume.
This is interesting; I have always assumed that the stereo mix was just a mixdown of the surround mix, and I've not done any A/B tests. Do you know if this is a common phenomenon?
Audyssey is one system that does this, but I'm sure there are others. If I crank my receiver's "dynamic volume" to "heavy" it substantially reduces the dynamic range, which is good for Michael Bay movies while the baby sleeps. It also destroys any music that has dynamic range, so I'm quite glad to have source material with a wide dynamic range and an optional compressor in my playback device.
We'd also need to reserve more space for audio on our discs. Dolby's and other encoding schemes compress audio data. This factors into bandwidth as well: IIRC, my PS3 sends "bitstream" audio data to my receiver because the optical cable can't handle 5.1 LPCM at the source frequency. HDMI cables are higher-bandwidth than optical, but it was not an option for me.
It's also convenient to use the Dolby matrix-encoded audio to get surround sound out of plain old RCA cables. I discovered this with Guitar Hero on my Wii, and the fact that Nintendo and my receiver's manufacturer both payed Dolby meant that I could get surround sound without switching out the entire audio path.
But yeah.. TrueHD is probably overkill. I expect the room to have a bigger impact than a lossless codec for all but the most anal home theaters.
You silly goose, hackers don't have mice!
I'm curious, how would you go about proving this? Occam's Razor comes to my mind: positively identify that the common Santa Claus story is a fiction, and then deduce that a coincidentally identical Real Santa Claus is extremely unlikely, given the rarity of individuals that are similar and well-known. But that's not proof by a long shot.
It is a fallacy to assume that because two possibilities exist that they must be equally probable. Nobody on earth knows the odds on this sort of a "bet". It is also a mistake to award equal effort or weight to all possibilities in an investigation, since there are innumerable dead-ends. It makes sense to expose people to logic, the scientific method, and mythology (religious or otherwise). It does not make sense to present these topics as competitors, because comprehension of scientific discovery and processes does not preclude personal faith.
Yup, I did some digging in my 401K ETF holdings and discovered that I owned a little bit of Halliburton. Whoops! I did not unwind the ETF position but I was able to redirect new investments to other funds with similar "risk profiles" but with holdings that I was more interested in promoting. Big oil, OTOH, is probably a bit more difficult to avoid. A quick check shows that Exxon and Chevron are in the top 10 for SPY.
Both libpthread and libncurses are split out with very few externally-visible functions defined per translation unit. They are very close to being optimal on my platform (Linux, x86_64) in that static linkage will include only the translation units required and not the entire archive file. I'm sure that there are many other C libraries like this (C++ probably not as much due to templates and inline class member functions).
Since the GPL existed before the App Store and is an extremely popular software license, it is logical to conclude that Apple knowingly crafted terms of service that excluded GPL compliance. Whether this is intentional exclusion or simply collateral damage is unknown, but the onus is on Apple and not the FSF/RMS.
My vote goes to the Irishman in Braveheart. It's his island.
Ah, but what if it's Hurricane Ditka?
In the context of the GP's incorrect statement, your response makes sense. However, the problem that people find with fluorescent lighting is typically not the color temperature but the spectrum (measured as CRI, where 80 is most cheap CFL bulbs and 100 is the sun). There are many ways to produce light that looks "white" to our eyes, but light with an uneven spectrum will look weird when it reflects off of any surface that is not also white. Think about shining a red light on green plant leaves: the plants look black, because the spectrum of the light multiplied by the reflectance of the leaf (think SIMD or vector math) is very dark (close to a 0-vector).
So in actuality, it's not people complaining because they want their warm (red/yellow) color and tape hiss back; it's because fluorescence produces very weird colors in real-world settings which appear very unnatural in comparison with the sun.
My Westinghouse PAR38s* all take about a second to start up. It's not continuous, they hit some darker pinkish color in one step and then their final color in the next step. The startup time appears to decrease as the bulbs "break in" as well, but they're never "instant-on" the way that most other lights appear to be (CFL or not).
*bought new a year ago, which qualifies for most definition of "current"**
** except for the definition I = dQ/dt, yuk yuk
Needlessly pedantic. If laws are passed that make it impossible for incandescent lights to meet energy-efficiency standards, then incandescent light bulbs have been de facto outlawed.
Lua's OO system is pretty similar. Not that I view this as a good thing in general, but there is a certain beauty in keeping a language as simple as possible and foisting the boilerplate onto library designers.
It's not just mentality, it's how the market rules are laid out. The possibility of short selling keeps prices from spiking up regularly (effectively, the short sellers punish overeager buyers). Short-selling a stock is very difficult within its first 30 days, meaning that most otherwise-market-neutral traders end up with a long bias on this stock. Of course the stock jumps up as a result. Now, the "IPO mentality" exacerbates this phenomenon, but the long bias would exist even if we were all emotionless robots (or "rational investors").
I believe that visiting a site with "like" buttons counts as FB activity as long as they can see your login cookie. This effectively lowers the bar of activity to "all users who do not deliberately avoid us" (via logging out, switching browsers, blocking CIDRs, etc.)
It should be clear; the implication I intend is that maximizing tax avoidance is a requirement for maximizing ROI. You could successfully argue about local vs. global maxima: that the maximum ROI may happen to not coincide with the maximum tax avoidance (because it may require changing business operations); but that's a substantial nit to pick.
That they do; but the fiduciary responsibility can conflict with ethical considerations. I also believe that laws representing the prevailing majority opinion will naturally lag behind ethics, so there will always be gray areas with legal-but-unethical actions and illegal-but-ethical actions.
I would argue that the conclusion does not follow, and that a fiduciary responsibility to maximize tax avoidance is necessarily unethical. Put another way, the duty to shareholders should not trump the duty to society at large.
B&H photo/video does the same. Last I checked, even their website was closed for sales on the sabbath.
That's an absurd thought. Plenty of code is written and not open-sourced or otherwise distributed to the public. This will remain true until we reach the Star Trek level of technology and culture.
Rather, I think the GP just stumbled upon the true meaning of the "US War Machine". Behold our mustachioed clone army and tremblingly obey!