But nature also has little regard for per country statistics. Splitting China into two countries, isn't going to lower their polution.
Using per capita statistics at least allows us to focus on those that are emitting excessively more than others.
737 karma · joined November 19, 2014
But nature also has little regard for per country statistics. Splitting China into two countries, isn't going to lower their polution.
Using per capita statistics at least allows us to focus on those that are emitting excessively more than others.
But I guess this is wishful thinking given that we don't even generally sign written comments yet.
It does. It specifies how the filesystem should behave in a particular (non corrupted) way. There is no exception that this requirement is somehow voided if the system wasn't cleanly shutdown.
Are there any issues in Germany with professional usage of common Public Domain software like Sqlite?
The point of rename() is to prevent a version to ever exist that mixes the old and the new version, which it always does, regardless of the filesystem.
Surely, if I do "write foo~", "rename foo~ foo", regardless of any crash, foo is either pointing to the old data or the new data. There simply isn't any inode with any "partially renamed state" mixing the two.
You use a hardlink only for atomic creation of the initial data:
write 'foo~'
hardlink 'foo~' onto 'foo'
To atomically update you simply use rename: read 'foo'
write 'foo~'
rename 'foo~' into 'foo'
I don't know what dan-robertson's claim is based on, but this surely is atomic even on a crash, as the filesystem will never be in a state where 'foo' contains only partially updated data. That would require some severe fs corruption.We write our code such that it minimizes the amount of effort to read it, under the assumption the reader knows the language.
This way, it makes sense not to use a library for something that can already be cleanly expressed by the language because this introduces additional mental overhead for the reader.
Yet is doesn't make sense to avoid modern, simplifying language constructions, as we can assume these are known by the reader.
This unwritten contract is jeopardized by an overload of language features, as suddenly we may want to avoid certain features considered complicated. Hence, the notion of optimal code becomes more subjective.
You will need a ground station to communicate that isn't going to fit in a pocket.
Let me give it try:
> let R be the set of real numbers. Let x be an element of R.
There it is, I've dealt with and used every single real number.
The notion that reals are only real when they are individually described (Borel's credo in the article) is an odd one. Sure, almost every real number is a "Mathematical fantasy" as the author calls it, but that doesn't mean Mathematicians can't use them or deal with them.
Mathematics excels in dealing with imaginary things. To extent Borel's credo to question the Mathematical validity of these Mathematical fantasies seems to defy the entire idea of Mathematics.
By far most energy is used to produce things (including the transportation requirements to do so). And as it turns out, the hunger for producing and buying new things is very hard to temper. This hunger is evident from the fact that the ways we are measuring "economic success" strongly correlates with the amount of things we produce, or even with the speed at which we are increasing the amount of things we produce.
The favicon is acquired from DDG servers for the result you've just retrieved from DDG servers.
How is this leaking anything? What additional privacy would you gain from getting the favicons from the domains directly of search results delivered by DDG?
This gives the best of both worlds of electoral districts and popular voting: Everyone is locally represented but the national representation is neatly distributed over ideologies instead of having just two parties.
As the most import benefit, it completely removes the incentive for strategic voting.
Art isn't useless, and usefulness is highly subjective. No matter how sustainable we attempt to behave we cannot distinguish pleasures from necessities in a meaningful way.
Then again, even if the footprint of art in its entirety is rather small, this doesn't absolve artists from the same responsibility we all share. A responsibility you rightfully point out, not apparent in Christo's art.
Then again, most of his work is from decades ago when the urgency of sustainability wasn't as obvious as it is now.
I don't think he deserves being remembered for wastefulness.
Unbiased reality by no means implies that the number of scandals, controversial quotes, achievements or even the relevance of the party slogan must be similar for both sides.
Rust's terminology is kind of reversed: It is stated that a mutable reference cannot be shared, while in fact a reference is called "mutable" when it cannot be shared.
The terminology is understandable and great to get started, but once you dive in deeper into atomics and internal mutability, it's rather crucial to understand this reversal.
Highly intuitive, beautiful and always "just working", with an elegant plugin system.
It is no coincidence that the authors went on to create Gnutella, which could be considered the starting point of decentralized networking.
This is why I hope for a future with content-based addressing, as used in bittorrent and IPFS.
Bittorrent has its focus set on files, and IPFS is becoming a bit convoluted but the core idea is very powerful.
Immutable content persists by "pinning". And even if the author no longer wants to maintain the resource, there are likely some "users" that will (eg. linked pages). And even if there is little interest from users there are still archiving services that might want to keep it. Persistent unless it's so vile or irrelevant that even archiving services ditch it.
All addressable by the same content hash.
I would say OR is the natural use, and exclusion is implied by the context in these examples.
Oligopolies like this exist because there is no free market. Government laws on things like intellectual property, profit taxes and most importantly, the limited liability of corporations are the necessary breading ground for organization into giants.
In a pre-corporate "Adam Smith" style free market Google could not exist. In a sense, these giants are the opposite of a free market as every movement of value within large corporations is governed by hierarchical decision making with an almost military scheme.
From this perspective, it isn't all that strange for governments to look into rules and regulations that can tame the beasts that they have created with their rules and regulations.
Containers have become the first stop method to hide overly complicated build processes. When you've noticed your wiring has become a complete mess of knots, just put it in a box so no one will trip.
It seems to me that containers are useful for deploying final setups, but should be a no go for packaging tools.
Yes. The behaviour is quite odd and unexpected. It seems they have different rules for when to apply the constant version of floating math than what constitutes actual compile time evaluation.
const a float64 = 0.1;
const b float64 = 0.2;
const x float64 = 0.1 + 0.2; // Const evaluation, "rational" math
const y float64 = a + b; // Const evaluation, IEEE-754 math
fmt.Println(x == y) // false ??!?
This seems quite a horrible approach.EDIT: Or how about this one:
const x float64 = 0;
fmt.Println(x + 0.1 + 0.2 == 0.1 + 0.2 + x ); // false!
fmt.Println(x + 0.1 + 0.2 == x + (0.1 + 0.2) ); // false!Why does it have this result?
I don't think this is compelling argument. Normally the test and the fix are looked at together and are already sufficiently separated in the code.
It makes more sense to me to use a single commit so the fix can be described in a single commit message, keeping the history clean.
Although hardware is relatively cheap, 170 QPS on 40 servers for this type of query is astonishingly horrible even from a Business/Product Engineering standpoint.
Boasting this as "highest QPS* engineering achievement is just awkward. It may be better suited for an article on how throwing hardware at problems is cheaper than hiring engineers.
After all modern ads and cookies on every site, they just keep finding new ways to make my browser experience even bore abhorrent.