You do not need a computer for the setup. You’ll need your mobile phone instead.
You may, if you wish, hook up the Q2 to a a PC to play steamVR and Oculus Games. The oculus quest 2 has a separate store (in VR) in which you purchase new games.
I’ve always been puzzled by the “You accept these cookies” banners. Some have an ‘accept’ and ‘don’t accept/let me choose’ and some even come with a ‘X’ to close the banner.
So what does it mean when I either click the ‘X’ or simply do nothing and leave the banner there while I read the article? What does it mean when I use reader mode and basically ignore the question whether I accept them or not?
We're making use of the standard Go tools + Godep and as such with any Go version below 1.6 you can run the tests with "godep go test ./...", anything above 1.5 with "go test ./...".
Hi, I'm one of the co-founders and core devs of Ethereum.
Ethereum wasn't build/implemented for or on Azure. Microsoft showed support for Ethereum by offering BaaS (Blockchain as a Service) and have now adopted our in-house programming language Solidity within VS. Solidity is our higher level smart contract language that can compile down to EVM byte code (EVM - Ethereum Virtual Machine).
I can't tell you whether Ethereum will take of or not, to me it already has. Consider me highly biased being the original author of Ethereum's most used implementation :-)
To get a good feel of Ethereum and the community; take stroll through our community reddit [1], github client repo [2], solidity language [3] and some more documentation [4].
Warning: 2 & 3 are for our technical enthusiasts, 4 is very interesting. Enjoy! :-)
Madness? Tackling problems (consensus, protocol, etc) early on a "stupid move"? You believe that copying bugs (as something you'll have to do if you want to create a new btc node from scratch) is something we should strive for? Having another client to fall back to if there's a bug in one of the others is, again, "a stupid move"?
"Many have tried such as bitcoin-ruby (ruby) and btcd (go), but they are plagued by almost constant issues of them having different states and getting forked off the network."
This is _exactly_ why you should have multiple, clean room implementation from the start.
Oh btw, we've already got consensus with 3 full nodes for quite a while.
Hi guys I'm one of the core developers and will I'll answer some the questions. There seems to be some misguided information and claims that are, fortunately, not true.
> but speaking to core developers it turns out that this isn't really significant at all.
I'm one of the 3 core developers and I'm pretty certain I've not met or talked to you, and I can't imagine the other two making such claims either.
> Ethereum has already raised as much money as the BF spends in a decade
We are a different tech but so happen so share and exist in the same space. Comparing us to the BF or Bitcoin in general is just downright wrong. You're comparing apples to oranges.
> For one it's still pretty much vaporware, little has been released
I've been relentlessly working on this for the past 7-8 months and so has Gav & Vitalik. All 3 of us have made remarkable progress if I may say so. Right now we have 3 clean room implementations with 99.99% consensus and operate on the same testnet blockchain. Vaporware? I beg the differ.
* Go - myself
* C++ - Gavin
* Python - Vitalik
The Go, C++ and Python implementations have full interoperability. A 4th, Java, implementation is being developed by Roman but hasn't got full consensus yet.
> Obviously the Ethereum team is not going to release "all the code" immediately
All of our code is available on GH actually (https://github.com/ethereum)
> Are you allowed to create TPC/IP listen sockets? This is undefined.
We have been _very_ explicit regarding I/O (in any form), it's simply not allowed, period.
> Specifically, arbitrary code execution by strangers.
I'm not sure if you're familiar with the model we're using but arbitrary execution isn't a problem considering we do not allow any form of I/O.
The arbitrary code, or contracts, are "triggered" by sending it a transaction. Once triggered it will run according to a set of rules that have to be goverend at all time. It's part of the consensus engine; it's "all in or nothing". Once mined, the miner will announce the new block, node's will verify the transactions and execution and can accept or reject based on their findings.
> Obviously it's not vaporware but there are many discussions about their implementation behind the scenes such as "Ethereum “Dagger” PoW function is flawed"
Vlad is currently working on the PoW. For code see https://github.com/ethereum/mining
I don't mind a good bit of scepticism but the amount of false claims and downright incorrect information that some of you have been posted really is below the HN standard. Most (if not all) of the answers are available online, just put a bit of research in to it.