344 karma · joined April 19, 2013
What was the compact, correct way referring to here?
Because with that conceptualization, it seems like an inherent risk to store liquid oxygen in a charcoal container on a rocket ship.
I suppose the intent is to then use that 95% memory savings for other work.
So what's the point of making this optimization? The system is going to be hugged to death if the number of client connections approaches 100%, because the system will not have enough available memory.
If 100% client connections is causing memory problems, rather than keeping a pool of buffers so that inactive client connections have less footprint, it seems like a better solution is to decrease the number of available client connections. Then, provision more servers or more memory if more client connections are required.
It would certainly be a much more complex solution that would still have inferior results compared to computing everything locally (just like cloud streaming now). Just that it's not "change the laws of physics" impossible to get to a workable implementation.
See also John Carmack's comments from 2013 on latency mitigation: https://web.archive.org/web/20140719053303/http://www.altdev...
That's 11 hours at 3500W for 7.5gal == 5.1 kWh/gal.
1.8 gallons in that generator gives about 9.2 kWh. Or, 11.7 gallons to get 60 kWh.
Some other quick searching says gasoline has 33.4 kWH/gal and that typical gasoline engines in cars are around 25% and the best peak at maybe 35%, giving between 8.4 kWh/gal and 11.7 kWh/gal. Which is between 5 to 7 gallons for 60 kWh.
I think that qualifies as a shrinking product: slight increase in the number of users combined with a massive decrease in the time of use per day.
That's just not true.
An trending increase in the national average monthly cost of rent shows that people are competing more for housing. But, that can be explained by a migration to major metropolitan centers and/or tech centers. Which is a totally different mechanism than "running out of housing".
But, when considering life, if applying the Big Alien logic, I should expect to be a single bacteria. And if not that, then, say, some insect.
But, instead, I'm a human. Or a mammal. Or a vertebrate. Any of these very fundamental descriptions of myself already put me in the SMALL group not the LARGE group when classifying the population of all life on this planet.
It feels like confirmation bias to select "vertebrate" or "mammal" to show that we are already indeed in a large group.
And indeed you can argue scientists are already applying this logic by looking for signs of simple life, say, or Mars. Or Europa. Because, that's the most likely to be found.
Maybe we should call it the Bacterial Alien Theory. Of course, it wouldn't be very controversial.
I've learned the hard way that the 'R' in traditional RAID truly does stand only for "redundant" and not "reliable". Reliability in traditional RAID is predicated an complete, catastrophic failure of a drive such that it is either working wholly and completely or failing wholly and completely.
In a traditional RAID, for any failure mode in which a drive or its controller starts to report bad data before total failure, the bad data is propagated like a virus to the other drives. The corruption returned by a failing drive is lovingly and redundantly replicated to the other drives in the RAID.
This is the advantage of ZFS (or BTRFS). Blocks of data are checksummed and verified and corruption isolated and repaired. Yay for reliable data.
With that premise and those numbers from the article, the crash will be something like a 35% drop in revenue (bounded by 25% and 50%) for sports teams when the transition from obfuscated to transparent pricing is complete. That seems like a big deal.
http://pmthium.com/2014/10/apw2014/
"What exactly is the “Great List Refactor” (GLR)? For several years Rakudo developers and users have identified a number of problems with the existing implementation of list types — most notably performance. But we’ve also observed the need for user-facing changes in the design, especially in generating and flattening lists. So the term GLR now encompasses all of the list-related changes that seem to want to be made."
You refute that the old logo didn't scale down to smaller screens well? Getting the logo visible across mobile devices was a major part of the redesign. If your job is logos and branding, that seems like a real problem. And branding does affect a company's outcome, certainly more than "one iota". You are acting like a terrible cynic and troll.
Initially, modifying "a" also modifies "b". Later, modifying "a" does not modify "b". I can't imagine a piece of code that uses "a" or b" that wouldn't care which of those two states the system is in.
And, knowing which of those two states code will be operating under will not be clear by simply looking at an arbitrary piece of code. The fact that it is well documented that transition may occur does not resolve this ambiguity.
Like, in the "Disaster averted" example the mutex section, how is it detecting that "error: `guard` does not live long enough"? I see that access returns a borrowed mutable T. But, how does the compiler know that that's borrowed from guard instead of a hypothetical second or third parameter or from some other (global?) state altogether?
Edit: Or maybe if a function returns a borrow, then the borrow cannot outlive the scope of the function?
Do you think if Google started including ads in their search results, it would affect the discoverability problem of non-sponsored web pages?