No, the volatility has been entirely in BTC. Volatility should more accurately be measured against actual real-world goods that you can buy. Since pretty much all actual goods are priced in currencies other than BTC, with the BTC price merely set based on the current exchange rate with the currency that the goods are bought at, it's BTC that's volatile, not the USD.
This kind of volatility is actually really harmful to it being adopted as a primary currency. It's pretty dumb to actually spend bitcoins if you could just hold onto them and sell a week or two later at twice the price, and then spend the USD for twice the goods you would have been able to buy last week with the same number of BTC. It's also pretty dumb to accept BTC as payment, especially when it's at an unsupportable high, because it's likely to crash soon and you'll now have half the value you had earlier. The volatility is valuable for speculators, but could be ruinous if you were trying to run a business based on it. Yes, you could get lucky and it could go in the direction that favors you, but that's speculation, that's not business.
> It's pretty dumb to actually spend bitcoins if you could just hold onto them
A similar question can be asked about USD: why would you ever save it instead of spending it immediately, since it's only going to lose value over time due to inflation?
Of course, the difference right now is that the deflation rate in bitcoin is much higher than the inflation rate in USD. But clearly, if bitcoin ever becomes a major currency and the deflation levels off, there will be plenty of motivation to spend bitcoins, the same way there is currently plenty of motivation to save USD.
> A similar question can be asked about USD: why would you ever save it instead of spending it immediately, since it's only going to lose value over time due to inflation?
The answer to this question lies at the heart of why economists generally believe a little inflation is better than no inflation nowadays. That little bit of inflation makes it more attractive to invest money in things that increase one's ability to generate money in the future instead of just stuffing it under a mattress. That makes the economy as a whole more vigorous, which means everyone tends to get more wealthy in the long run.
As for deflation in Bitcoin: Since the total number of BTC that can ever exist is asymptotically bounded, but potential economic productivity of a population of humans isn't (as far as we know), there's really only a few scenarios where BTC deflation might level off, and arguably all of them fall under the category of "economic crisis".
Then the hope is that economic productivity increases at such a slow rate that the BitCoin isn't appreciating in value quickly enough to make it irrational to spend one.
Just like monetary policy attempts to set inflation at such a rate (~1%) that it isn't irrational to save, but it is slightly more rational to spend.
I think, though, that if everyone agreed, BitCoin could eventually change to borrow some concepts from PPCoin, and restart the production of currency, once it reached a plateau of adoption. It isn't impossible to change the current production limits - just difficult. At that point BitCoin would probably splinter into two currencies, one which has a deflationary monetary policy and one which has an inflationary one.
At that point - is it still a libertarian currency? We've just traded one governing body - the US govt - for another - the BitCoin Foundation.
> A similar question can be asked about USD: why would you ever save it instead of spending it immediately, since it's only going to lose value over time due to inflation?
Except for relatively small amounts for liquidity for known or potential immediate needs, it doesn't make sense to hold US dollars (or any other modern fiat currency), it makes a lot more sense to invest them in productive assets which can be converted easily back to US dollars (or other fiat currency) when necessary.
This is not an accidental feature of modern fiat currency, its pretty much the whole point of the transition from commodity-based (e.g., gold standard) to fiat currency -- so that broad downturns don't have a dangerous positive feedback effect where poor investment market conditions lead to currency being a more attractive place to hold money than the investment markets, which leads to even poorer performance in the investment markets and even more people pulling money out of those markets and into currency, etc.
> But clearly, if bitcoin ever becomes a major currency and the deflation levels off [...]
Please explain how increasing interest in using bitcoin is going to cause the price increase relative to other currencies or goods to slow down.
> [...] there will be plenty of motivation to spend bitcoins, the same way there is currently plenty of motivation to save USD.
Seriously? How about buying a house? Buying a car? Going to college? Going on vacation? ... Most people cannot save up enough for these things overnight, and they aren't going to put their downpayment savings fund into stocks because it's not worth the risk of losing it for them.
Um, you know there do exist lower-risk investment vehicles than stocks, right? Back when there was inflation, you'd be a fool not to put the $10,000 you're saving for a house into a 1- 2- or 5-year CD. And investing in I-bonds for their kids' education is still something parents do.
> Seriously? How about buying a house? Buying a car? Going to college? Going on vacation? ...
In all those cases, saving USD as dollars is generally a suboptimal idea (unless its over a particularly short term, but that gets back to the short-term liquidity, not long-term investment, case.)
Using the dollars to buy investments that are expected to be worth more when converted back to cash is what you usually want to do.
That's a fine idea, but few people will do that in practice because they don't want any risk at all in losing the money they're saving for those things. People generally invest for the very long-term, like retirement, not for things like house downpayments.
Consider the humble savings account. Those accounts may be dollar-denominated, but under the hood they're really a type of security. You're making a loan to the bank at interest - a special kind of loan that you can call at any time, in part or in full, but a loan all the same. The bank then takes that money and loans it out at interest to people who want to borrow money to buy houses cars, whatever.
There is risk involved - the people at the end of the chain might default on their loans, in which case the bank loses their money. Historically, if the bank lost enough money then they wouldn't be able to pay back the money they borrowed from you, in which case you also lose it. Nowadays banks are required to carry deposit insurance, so instead when the bank defaults the FDIC loses their money, but you still get paid. But if enough banks default then the FDIC also won't be able to make good on their guarantee to you, and you're still out your money. Meaning that when you stick your cash in a savings account, it's not really money anymore. It's an IOU - a promise to give you money when you ask for it. Probably.
> few people will do that in practice because they don't want any risk at all in losing the money they're saving for those things.
Many people do it in practice. Stuffing dollars in your mattress is "saving dollars". Loaning money at interest who will aggregate it with other money and invest in productive assets is an indirect investment in productive assets other than dollars.
Stocks aren't the only investment option. Safer options exist, e.g. corporate bonds, money market funds, and certificates of deposit. All of those are a more productive use of capital than socking it away under a mattress or in a Bitcoin wallet.
Because it loses value slowly enough. That's the whole "stability" part. Holding onto USD for a year or two doesn't lose a significant amount of value, so you can save up effectively and plan on what you will be able to buy with it at the end. And you can put it in an interest bearing bank account or invest it to further offset or counteract the effect of inflation for longer-term savings.
Unstable currencies you generally need to convert to a more stable currency immediately, if you don't want to be subject to the sudden swings in value.
My point is that I don't think you're pointing out a fundamental flaw in bitcoin. Deflation in a currency is not a deal breaker. Bitcoin is volatile right now because it is so young. People are predicting it will reach a huge market capitalization, which would necessarily entail a huge USD price per bitcoin because there are so incredibly few bitcoins in comparison to USD. Anytime something is increasing in value there will be considerable gambling and speculation to come along with it as random people jump on and off the train repeatedly.
What bitcoin really needs is a unique and innovative service which could not exist without it. This would encourage people to hold a small balance in bitcoin which they would be willing to spend in order to enable participation in this service not otherwise possible. As the currency stabilizes and more and more use cases emerge, people will slowly but steadily become more comfortable holding larger balances in bitcoin.
Its pretty much a deal breaker in the use of currency as a the general medium of exchange and pricing. Its not a deal breaker in its use as a store of value, obviously, but that's more about being an investment vehicle than a currency.
> As the currency stabilizes and more and more use cases emerge
What I'm missing here is any explanation of why we should expect bitcoin volatility to stabilize.
> It's pretty dumb to actually spend bitcoins if you could just hold onto them and sell a week or two later at twice the price
Similarly it's pretty dumb to hold on to dollars if you know you could double them in a week by buying bitcoin. The ideal solution is to spend bitcoin and immediately replenish them by exchanging USD to bitcoin. That way, you still have the same amount of bitcoin and simultaneously more bitcoins are going into the economy.
> The volatility is valuable for speculators, but could be ruinous if you were trying to run a business based on it.
Immediately converting to fiat removes the risk. The beauty is you get to decide what you want to do with them.
I don't know who really still believes that FOSS is unpaid labor. It is generally paid in the form of better jobs available based on your record, paid support, being paid to do it incidentally as part of your job, or even being paid directly to work on it.
So, pointing out that FOSS is paid labor is basically just attacking a strawman. I suppose that a few people seem to be mistaken in thinking that their FOSS work is unpaid, despite all of the economic benefits they derive from it (like DHH recently), but I don't think that this perception is particularly widespread or really very harmful.
> pointing out that FOSS is paid labor is basically just attacking a strawman.
I would agree with you if that was the entire attack, but it's not. The article isn't making an attack. The point is that it's important to think about _who_ has access to social capital, and _who_ can produce social capital.
OK, so the FOSS community consists primarily of people in already privileged groups (white English speaking men), and they are best suited to be able to take advantage of it.
So, what's to be done? Is the solution to give up on FOSS? That's what this article seems to be arguing: "All it has done is shift the details and, indeed, done a much better job of disguising its exploitation of people. All while presenting itself as a ‘solution’." The article seems to argue that FOSS actually causes more oppression than it solves, and I have a hard time buying that.
One thing that it completely ignores is class distinctions. One of the things that FOSS allows is for anyone to produce a product without substantial investment of capital. Proprietary software is an owner's dream; invest a small amount upfront in developer's salary, and be able to reap unbounded rewards, as there is no unit cost for sales. FOSS allows anyone, without capital upfront, to create a competitive business, opening up opportunities that wouldn't otherwise exist for people who are middle and lower class.
Now, those benefits can be most easily reaped by people who have social capital in the community. But it seems that rather than throwing the baby out with the bathwater, it would be better to figure out why there are such barriers to entry to people who are underrepresented in the community. While there are some cases where there are clearly people pushing others away, I feel like there's a lot more of simply a lack of awareness of what it is that is keeping people from joining and contributing to the community, and being able to build up social capital that way.
I don't think this article attempts to provide solutions, only to 'add framing' to the problem.
> One of the things that FOSS allows is for anyone to produce a product without substantial investment of capital.
Absolutely! This is actually very in line with Marx's thinking.
After reading your last paragraph, I think your issue is that you want more than the article is attempting to give. I agree, we absolutely need these kinds of answers. I just don't think that it was ever intended to be presented here.
Well, I think the article is explicitly going in the wrong direction, criticizing the basic idea of FOSS for causing these problems. The article seems to claim that because FOSS relies on labor that is unpaid upfront but rewarded by social capital, that it is inherently going to produce worse outcomes for less privileged groups. And I don't buy that.
So it's not just that I want more than the article gives (though I want that too; I would prefer that more potential solutions were presented), I'm also uncomfortable with the way it's framing the debate, indicating that this is an inherent failure in the FOSS model as opposed to a bug that should be fixed.
"Institutional and systemic oppression within the F/OSS community" is definitely an attack. Oppression is unjust or cruel exercise of authority or power. It's not unjust to assign more value to more highly skilled labor however that skill was developed, just as it's not unjust to hang the Mona Lisa in the Louvre while excluding the work of young students who have not had the time and opportunity to become expert painters.
They actually wouldn't agree with your assessment about value assignment, other than to point out that justice has nothing to do with it, that's how markets work.
Just because it mentions an unjust situation doesn't mean that's the thrust of the article.
So, the social and economic context of FOSS, especially in light of things like DHH's article about how he doesn't believe in paid contribution to FOSS (despite, well, being paid to contribute to RoR) and Chris Anderson's post about requiring a GitHub account is certainly a worthy topic of discussion.
However, throwing around random Marxist buzzwords like "hegemonic control" and "commodity fetishism", and accusing Jeff Atwood of being an "unapologetic white supremacist" for a post that could be best described as Anglocentric, is a really pretty awful way of convincing anyone but those who already agree with you.
It appears that the author, rather than trying to improve anything, is merely trying to improve her own social capital in Marxist academic circles.
First of all, these words are not random. They're being used exactly how they're supposed to be used. Source: I read lots of Marx. I can explain any individual one to you if you'd like.
Secondly, one man's domain terms is another's 'buzzwords.' Domain terminology has value because it allows you to get to the point, once there's some amount of shared understanding. You need that understanding first, though, which I think is causing the friction here.
> is a really pretty awful way of convincing anyone but those who already agree with you.
I don't disagree, but I don't think the blog post is trying to convince anyone. As it says at the top, it's attempting to add a certain frame to the previous article: in this case, a Marxist one.
I say "I don't disagree" because, well, I actually disagree with Marx, but that doesn't hurt my understanding of the article, because I understand the terminology. It actually helps me grok the author's point and where they're coming from, because I can draw on previous bodies of work to help me understand.
> It appears that the author, rather than trying to improve anything, is merely
> trying to improve her own social capital in Marxist academic circles.
What I find amusing about this statement is that in some ways, she would agree with you: the thrust of the article is a simple assertion that 'unpaid' labor is paid, just not in {the money commodity,money}. It's paid through social capital. And ignoring the relationship between who has access to and can produce each different kind of capital misses an important part of the analysis.
So, I'm not terribly familiar with the idea of commodity fetishism, but for the sake of argument, I'll buy that it's domain terminology that has value. If you could explain how it helps describe the situation in the FOSS community, that would be helpful.
I am familiar with the notion of hegemony, and the assertion that Richard Stallman has hegemonic control over anything is laughable. Yes, he does have a certain amount of power based on his personal social capital, but it could not be described as any sort of hegemonic control over anything. Hegemonic control implies that you have implied force or economic powers that allow you to have indirect control over many people; his only "control" is people's respect for him and the strength of his opinions (as well as some direct power at the Free Software Foundation and GNU project, but that's fairly marginal in the wider world of FOSS; there's far more software and people working outside of the FSF and GNU structure than within it). Describing him as having hegemonic power is like describing any influential academic as having hegemonic power; I suppose I can see the analogy, but there's a huge difference between a nation-state using its force and economic power indirectly to shape the actions of other nations and someone being intellectually influential. Using the notion of "hegemonic power" for a person who is merely intellectually influential merely waters down the idea.
And I further take issue with the concluding paragraph that the lack of diversity in FOSS should not be seen as a bug, bur rather as a feature. Yes, I see where she's going with the notion that there are people who use their existing power as members of various privileged classes to be able to exert more leverage and derive economic benefits from their contribution to FOSS. But that just means that it's a feature for certain people; like DRM, something that is a feature for a few is a bug for many more. Likewise, just because some people take advantage of their privileges in the FOSS community, doesn't mean that allowing such privileges to be leveraged actually is a feature.
Basically, commodity fetishism is the notion that economics is about relationships between commodities, not about relationships between people. It's called 'fetishism' as an allusion to religions in which dolls come to life. Marx asserts that economics is about relationships between people, but since we focus so much on things, the things come to life, like a fetish, and become just as much a part of our notions of economics as people are.
It relates to OSS because of 'the fetishizing of the F/OSS community itself': the dozens of articles about how OSS is the best way to make software, the only good way to make software, that those who do OSS are better than those who don't. We animate this social relation and put it on the same footing as actual people. They're expressed through objects.
Does that start to make some sense?
Stallman is an example in the article, not the controller of the hegemony. The hegemony is of the fetish of Open Source. Stallman is just one person (I am very much another) who stands to benefit from the hegemony.
I understood 'bug, not a feature' in a different way than you. What I got out of it was that it's a structural, not accidental aspect of the system. She was attempting to bridge the culture gap by referencing hacker pop culture. This kind of commentary is very common in Marxism.
I'm going to go eat lunch now, I'll check back in on this discussion later. Thanks!
"Given that he is still alive and has a thriving career based on exerting hegemonic control over F/OSS discours"
My reading of the above is that Stallman is exerting hegemonic control, thus being the (or possibly one of) the controllers of the hegemony. I agree with the original poster that this assertion is laughable at best.
If Stallman were able to exert hegemonic control, we would not be using words like FOSS, and software development would focus on solving social problems. Stallman is vocal about his Socialism and spends most of his time addressing political issues. Anyone can see this clearly on stallman.org.
But since the free software model was so successful, many people worked hard to remove its political associations, creating the open source movement. I think the real hegemony is the collection of existing power structures, which will always work to assimilate successful models.
It's important to think about who benefits in social interactions, but a useful analysis requires understanding particular historical details like the animosity between idealists and pragmatists in the FLOSS community. It might have been more useful to state that despite its idealiatic origins and the continued participation of people who want to address social problems with software, old structures of privilege continue to determine who benefits from social interactions. Anyone who disagrees with these privileges must take care to decide how best to work against them, because the default benefit is always to those who have inherited privileges.
On the other hand, putting it into an email gives a chance for people to digest and think about it offline, for the person who was travelling that day to be able to see it, for you to be able to forward it to the team who's working on the UI across the Atlantic from you.
Face to face communication definitely has it's place, but it can also lead to cliquish and insular behavior, and can lose out on some benefits of having a paper (well, electronic) trail.
This is compressing the video using either H.264 or WebM (it's a bit unclear; they include both x264 and WebM logos in their "open source software used"); it's similar to Apple's AirPlay mirroring or Google's Chromecast. Unlike those, however, it's not tied into a single company's ecosystem.
Most airports have large sliding doors that are triggered on one side only. Because they are large, and there are a lot of people flowing through them, it would be possible to slip in while the door is open, so they need human guards to watch and ensure that no one does that.
A regular turnstile doesn't really work very well for people with a lot of luggage.
So this is basically a large version of a turnstile, that is more secure than just a single gate, so it can be secure enough to leave without full time guards without preventing people with baggage from getting through.
Not a bad idea, not horrible civil liberties wise, but could be a problem for people with claustrophobia, and if they are avoiding having a guard, it's likely that there won't be an alternative exit for people for whom these won't work.
Ordinarily I'd agree with the claustrophobia point, but I feel like anyone who genuinely can't deal with a few seconds in a glass-walled airlock would never have managed getting on a plane in the first place.
As a matter of fact, my SO gets claustrophobia in revolving doors; she always refuses to go through them if there's another alternative, even the really big ones. She's fine on planes, however. I'm not sure whether these would give her the same sense of claustrophobia that revolving doors do.
I'm curious what you consider to be "cargo cult bad coding questions."
When I do phone screens, I generally do two coding questions, plus several other technical questions. The coding questions are a fizz-buzz level warmup question (not fizz-buzz itself, but something fairly trivial that any programmer should be able to do in 5 minutes), plus a more real-world question that requires walking over the filesystem, looking for particular things in particular files.
Beyond that, I do non-coding technical questions that are based on actual problems I've had to solve on the job, and actual technologies that we use every day like standard networking protocols (HTTP, TCP, DNS).
This seems like it would be fairly useful for my coding questions. So far I've done them in Etherpad or Google Docs, and told people not to worry about the precise syntax since that can be hard to do in such a different environment and without being able to run and test your code; then I inspect it manually and look for obvious logic errors. However, something like this would be fairly helpful in letting people write real code and run it.
Just came across this article http://www.nature.com/nchem/journal/vaop/ncurrent/full/nchem... about an advance in silicon microparticle anodes for lithium ion batteries which claims a capacity of 3000 mA h/g, and retaining similar performance (~2000 mA h/g) over 100 discharge cycles. They don't mention the voltage, so it's a bit hard to compare energy density; at the 3.2 volts common to lithium ion batteries, that's 6400 watt hours per kilogram, but taking a look at some of the charts available (I can't look at the article itself due to the paywall) it looks like it may actually be .5 volts, which means 1000 watt hours per kilogram. Compare to Tesla's batteries, probably the best in the business, which give you ~130 watt hours per kilogram, and this could be a pretty big game changer. Obviously, they will have to improve past 100 discharge cycles, but it looks like substantial gains in battery technology may be coming within the next decade.
As far as I can tell, there is no shared hardware. The point is that it dedicates certain hardware to the guests, and they have full access to it.
This is not supposed to fit into the same space as Xen or KVM; it's supposed to give the guest pretty much bare-metal control over the resources that you give it, with minimal interference from the host, so it can be used for real-time applications even if the host kernel is not real-time.
Ok, makes sense. But then "jail" is a bad name for it, I'm sure inmates have to use a lot of shared hardware in the real life.
In fact "partition" conveys the right meaning.
It's true that ObjC itself isn't what's proprietary, but Cocoa and Cocoa Touch are.