Yes, and the "bare metal" aspect is more similar to Xen or KVM.
LXC is the exact opposite. It uses a shared kernel, while isolating various resources like networking, RAM, user IDs, etc between the different containers.
Xen or KVM provide something that looks like a bare metal computer.
The difference here, as far as I can understand, is that this is designed to be even more minimalist than what Xen or KVM gives you. Xen and KVM will still use some non-trivial amount of CPU resources on the CPU used by the guest (and depending in the setup may even share the CPU between different guests). This is designed to give the guest nearly complete control over the CPU, to allow you to run, say, a real-time operating system on one CPU, without interfering with the Linux kernel running on the others.
Xen and KVM also traditionally provide emulated devices that the guest talks to, while this just gives the guest direct access to the devices it needs.
So this is pretty much in exactly the opposite direction as LXC. The advantage of LXC is that containers are very lightweight, while still giving you a full Linux environment, as they share the kernel and lots of resources (like their root filesystem) with the host or other containers.
The advantage of Jailhouse is that the guest really gets full control of the CPU and hardware and very little interference, so you really can run a RTOS alongside a traditional Linux system.
There are a continuum of different virtualization designs; this extends the options available in a new direction. You use LXC if you want everything to be a Linux system sharing a kernel, and want control of what resources are shared vs. isolated. This can allow you to run a lot more VMs a lot more quickly and with lower resource impact than the other solutions. Xen or KVM if you want a full emulated virtual machine, which can run any OS that you want, and can share CPU, disk, and other resources with the host or other guests. Jailhouse if you basically want to have a separate computer sitting on the same motherboard.
What types of questions are you interested in asking?
If you want to ask answerable technical questions (I'm trying to do X, here's the code sample, it's crashing here or producing this output), Stack Overflow is great.
If you want to ask a vague "which framework should I use for this project" or "tabs vs. spaces" question, Stack Overflow is not the place to go, and that's by choice.
I do sometimes have a problem with people who are over-eager to downvote or close questions which aren't phrased perfectly from the beginning, but overall, if you actually have an objective, answerable technical question to ask, it can be a good place to go.
Let's put it this way. Just about any programming question I google leads me to SO. Just about every one of those links are "closed as not helpful by the moderators" (paraphrased). Google thinks it is a useful question. I think it is a useful question. The questioner thought it was useful, as did the people that answered the question before it was closed. If it quacks like a duck....
Funny, I see a lot of closed questions on SO, but most of them are from HN links. When I google for a solution for a programming problem, I usually find a high-scoring (not closed) SO question with useful answers.
I want to ask subtle qualitative questions with nuance in the asking and answering. These questions do not always have singular answers, nor do they lend themselves to simple answers. Worse, they frequently have elements of subjectivity, since the nuance needed to answer this class of questions often relies on experiential information and insight.
It's become acknowledged with the professional software developers I've met (in real life) that SO has become fine for elementary "how do I X" (where X is a popular subject and has contributors on SO), but for anything more profound, SO is usually useless (often wrong, even).
Yeah, SO is explicitly designed not to be appropriate for qualitative questions with nuance. The problem is that those kinds of questions can frequently lead to endless debate, there's no clear "right" answer, and so on, and anything where there's voting and marking "accepted" answers and which is designed to be a good resource for someone Googling something to be able to find an answer isn't going to be a good fit for qualitative, subjective, nuanced questions.
I am a professional software developer in real life, and I use SO to ask questions occasionally, and answer questions often. There are definitely plenty of cases where it is much more useful than just elementary "how do I X"; there are lots of cases of real, difficult questions being asked and answered, or lots more of people who are experienced developers but new on a particular language or framework or library asking questions about that. It's also quite good at it's mission, of providing fairly good answers for when you Google a question, rather than a forum post where you have to go to the third page to find a comment that almost, but not quite, actually answers the question, and then two pages further to find the clarification that makes it all actually work.
So, you have to use it for the right kinds of questions, but I find that it really does work fairly well for those. The two main problems are that there is a somewhat low signal to noise ratio, as on any popular forum (lots of beginners asking those basic questions that you mention, lots of people asking questions poorly or unclearly, lots of people jumping on people for not quite asking their question perfectly at first), and that people are a little hasty to close imperfect questions without giving them time to be fleshed out into good questions.
The moderation, voting, and closing of questions is supposed to help with that signal to noise ratio, but I'm a bit skeptical, as it seems to be suppressing a little too much signal, and letting through a little too much noise.
Now, we saw the problems that I described at first (the question was a little bit vague, a lot of people jumped in with hasty and incorrect answers, and it was closed for being too vague), but since the system allows editing, voting, and re-opening of questions, those problems were fixed.
For a lot of questions, if you Google for a question and find it on StackOverflow, there's a very good chance it will be answered correctly. If you find a question that has no answer or was answered incorrectly, you are able to correct it or answer it yourself.
I guess what I'm saying is that StackOverflow isn't perfect, but you really shouldn't write it off based on a single bad experience. Just keep in mind what it is for; questions that are answerable, not just subjective or bikeshed questions, and you need to do at least some effort to ask a good question that has enough detail to be possible to answer.
Just so you know: I have a decently high rep on SO - 21K - and have a highish rep on Programmers.SE. And I spent a fair amount of time on Meta.SO back when unicorns were a good deal more popular. I am not writing this off of a single bad experience: I'm writing this based off about 2 years experience. It's a system - designed at that - that rewards simple questions with simple answers, and is particularly susceptible to wrong answers that are popularly believed. The exception is the nuance and the depth (Clearly, Jon Skeet is part of the exception. :-) ).
I don't particularly care that nuanced qualitative questions can lead to debate. Most things that are interesting and matter can be debated; that's why they are interesting- because there are different perspectives and education and experience can provide the nuance to help with choice. That's why I consider /r/programming a better place to find fruitful discussion than StackOverflow...
Anyway. Hope that helps you in your thought processes.
> Here's an example of StackOverflow working for a fairly deep question, about the maximal possible asymptotic slowdown due to purely functional programming
People aren't desperate to see Tesla fail. It's just that stories about something new are much more interesting than stories about something that everyone's familiar with, and stories about danger tend to be more interesting than stories about safety. These add up to a story about the three Teslas catching on fire, as opposed to stories about all of the gasoline cars catching on fire or stories on Tesla's safety record.
I appreciate that SO has a focus specifically on answerable programming questions, and that people are willing to protect it.
On the other hand, I find the the "questions police" are sometimes a little too hasty to shut down actually useful questions, that may stray a bit into the grey zone or may not be phrased as well as possible. I see a lot of new users posting questions that aren't quite clear enough, and then rather than commenting in a way that will help them clarify the question, people just downvote, vote to close, and move on.
There are some people who are just hopeless; no matter how much guidance on asking good questions you provide, they won't get it. But you shouldn't assume that when someone asks a question, and just vote to close. It can really hurt to have a question downvoted or closed, and put someone off the site. I think those tools should be used only for blatantly abusive or off topic questions, or users who really don't get it and keep asking the same things over and over again.
Keep in mind, Stack Overflow gets somewhere north of 8K questions per day. Every day. There's a limit to how much hand-holding anyone's willing to do in the face of that - particularly given how often it simply does not accomplish anything.
That said, if you're the conscientious sort and do listen to the advice given for improving your question... It'll get reviewed and possibly re-opened. If nothing else, you'll at least have learned something you can put to use the next time you ask a question.
Something else worth considering... Most of the moderation is done by (or at very least instigated by) the same folks answering the questions. So if you're active in a bit more of a niche tag (for instance, [firefox]) and you've done your homework to where the folks answering can actually help you... You're a lot more likely to get help.
@Shog9 One of the things I take issue with is when I am busy trying to help someone ask a better question, several other people are busy downvoting and voting to close which scares them off. There are a lot of people who have just the minimal reputation needed to vote to close, who seem a lot more interested in closing anything that they don't understand right away than trying to figure out what the person is really asking about and actually helping them.
Here's an example: http://stackoverflow.com/questions/19964962/html5-filesystem... It wasn't the best phrased question, but it was reasonably obvious what he was asking. Instead of trying to help him phrase his question better, or actually answer him, several people told him to "just Google it" or linked to tutorials that didn't answer his question while downvoting him and voting to close. Eventually, after I actually answered the question (which did take a little research, the only documentation I found was the spec which took a little parsing through to figure out how it was supposed to work), he got fed up with the number of downvotes and deleted the question.
This isn't an isolated example, it happens a lot. I've had lots of cases where there was a question that wasn't perfectly clear but if you read between the lines a bit you could figure out what they were asking, where lots of people just voted to close, wasting the time I took to actually try to answer the question correctly. It's harmful to the community.
And as you can see in this thread, there are a lot of people who are scared off by this behavior; who don't use SO because of the treatment they got. I definitely understand people's frustration with people who ask poor questions, but part of the point of SO is that you can, through commenting and editing, improve questions, and far too many people are too happy to just make a snide comment and downvote rather than actually trying to help.
(heh, funny that I defaulted to using SO-style "@Shog9" when discussing the topic on HN; it's interesting how I fall into that habit when replying to someone I recognize from SO, despite being on HN at the time)
Ugh, I hate those comments. Reminds me too much of forum cruft. Or that xda-developers video. If you see that crap cropping up, please flag it; they're easy enough to get rid of.
As you say, there's a bit of a "man with a hammer" problem with folks who've gained access to the tooling without really learning how (or when) to use it. I'm working on some better guidance there, but it can be hard to redirect that impulse. If you have any good suggestions, don't hesitate to ping me in The Tavern (http://chat.meta.stackoverflow.com/rooms/89/tavern-on-the-me...). "@Shog9" should actually do something there ;-)
You realize that Bitcoin isn't immune to fraud, it just puts the fraud burden on the consumer rather than the merchant, right?
There have already been plenty of Bitcoin frauds; pyramid schemes, merchants disappearing, computers hacked and Bitcoins stolen, entire exchanges disappearing, etc.
Sure; there's a reason I specified chargebacks and identity theft.
These are two areas that are largely solved with a push payment system rather than a pull payment system.
I'm looking forward to seeing how other types of fraud are addressed in the future, but it's fairly predictable we'll see further scams and fraud along the way.
Why do you think that Bitcoin fraud would be handled differently that fiat currency fraud; that is, by offering credit, doing chargebacks, and so on, just like people do with fiat currency?
I mean, it's not like we don't have options like wire transfers for transmitting currency without the possibility of chargebacks; but as you notice, most people choose to use credit cards, which offer the buyer protection, rather than using wire transfers for purchasing goods online.
Bitcoin isn't a particularly good payment system, and I can't imagine that most people will wind up sending Bitcoins directly as payment for the vast majority of purchases. It's more of a replacement of bank transfers or wire transfers, which are used in particular specialized circumstances but not by the average consumer.
The problem with every visual programming language that I've ever tried is not that it's aimed at novices and I'm afraid of being labelled that way. It's that there's a whole wealth of tools for dealing with text based programming that just can't be used with visual programming languages without a huge amount of effort (if at all). Visual programming languages don't work well with revision control; they usually don't have diffing and merging tools. They don't work well with grep.
They tend to have a fairly low information density on the screen. When looking at a simple program that all fits on a single screen, that's fine. But when working with an actually real world code base, when I don't understand exactly what it's doing, I need to be able to see as much on screen as possible at once to keep it all in context, while browsing through to figure out how all of the pieces link together. All of the empty space taken up in a visual language makes it a lot harder to get as much information on the screen at a time.
And the programs can frequently be quite hard to follow. Tracing all of the wires between different nodes, figuring out what's stacked on what.
There's a reason that despite the very obvious circuit diagrams you could represent electronics with, hardware engineers for integrated circuits don't use a visual tool for laying out their hardware, they use Verilog or VHDL, only compiling it down to the actual netlist and laying it out at the very end.
I have never seen a visual programming language that I would say could scale to anything beyond a few basic demos, which could just as easily be accomplished in a page of code.
Xilinx actually has (had?) a visual designer tool for their FPGAs in their IDE, allowing you to connect signals between blocks and do other stuff. It didn't work well and made for unmanageable designs. I've heard similar things about complex LabView programs becoming unmaintainable spaghetti code, although I don't know if that's actually true or not (never used it myself).
If you use selective laser sintering (which is what Shapeways uses), what you do is keep on adding layers of a fine powder, then us a laser to fuse them together in the places where you want your object. The powder supports the object, so things like a chain are entirely possible to print. When you're done, you drain the powder away and have your completed object (which you may then do further finishing on like sanding or painting).
Other 3D printing methods like extrusion may be able to do so, if they have two nozzles and can print both the final material and some supporting material that could be melted or dissolved away.
I agree with many of your criticisms (made a few of the same in another comment), but you missed a few points in their favor; looks like you spent a lot of time on this rant, it would have been good to spend a few minutes reading their FAQ and watching their video to make sure your criticism were valid.
Adding a card seems flawed. You're asked to take a picture
of the physical card after swiping to "prevent fraud" ok
but unless Coin uses some advanced image processing/OCR to
validate the card with the swiped data, you can take a
picture of any card. So big fail here.
Why do you expect them not to do image processing and OCR? Credit cards have standardized, highly OCR-able fonts. I would be very surprised if they didn't OCR it.
Most users are totally fine with credit cards and big
wallets.
I'll have to disagree with that. There may be a few people out there who appreciate the physicality of the cards, but based on personal experience, I'll bet a lot more would love to streamline it. In fact, I would love to not carry a wallet at all, just maybe a billfold and a single card or my phone. The problem is this doesn't go far enough; it only eliminates a few cards from the wallet, it does nothing about all of the health insurance cards, rewards cards, drivers license, membership cards, subway cards, etc that clutter people's wallets.
The obvious issue of losing Coin and losing everything.
People like backups. It's a mindset.
According to their video and FAQ, the cards are backed up to your phone. If you lose it, you can just get a new one and transfer your cards to that. And your phone will warn you when you lose it. Actually, one of the big draws are those two features together. Much less anxiety about leaving your card behind.
Battery issues with digitizing a non-battery product
(credit card).
They explicitly state that the battery is non-chargeable and non-replaceable. You don't charge it. According to their usage model (which includes much heavier usage than I use any of my cards, I generally use a card once or twice a day, maybe 4 or 5 times on a weekend), it will get two years life.
While I share the same concerns about privacy, compliance, card not present, and so on, I feel like you went out of your way to pick out problems, ignoring several things that were obvious from their FAQ.
The problem is any time you edit some of them out, you realize soon after that you don't have the one you need. If I don't carry around the cards I will need every day, I am likely to forget to take the ones I need only occasionally when I do need them.
The problem is that Coin doesn't really solve this. It only encodes credit cards; most of the other cards either don't have mag stripes or require other information on the cards than just what's on the mag stripe.
Everyone loses in this case. The card is supposed to facilitate a transaction and it failed to do so; the shop went without their money, the family went without their bikes, and all of the various financial institutions went without their cut.
Which is why the poster above is warning about this; if there will be merchants out there who won't accept it, it's pretty much DOA as you can't replace all the cards in your wallet with it.
LXC is the exact opposite. It uses a shared kernel, while isolating various resources like networking, RAM, user IDs, etc between the different containers.
Xen or KVM provide something that looks like a bare metal computer.
The difference here, as far as I can understand, is that this is designed to be even more minimalist than what Xen or KVM gives you. Xen and KVM will still use some non-trivial amount of CPU resources on the CPU used by the guest (and depending in the setup may even share the CPU between different guests). This is designed to give the guest nearly complete control over the CPU, to allow you to run, say, a real-time operating system on one CPU, without interfering with the Linux kernel running on the others.
Xen and KVM also traditionally provide emulated devices that the guest talks to, while this just gives the guest direct access to the devices it needs.
So this is pretty much in exactly the opposite direction as LXC. The advantage of LXC is that containers are very lightweight, while still giving you a full Linux environment, as they share the kernel and lots of resources (like their root filesystem) with the host or other containers.
The advantage of Jailhouse is that the guest really gets full control of the CPU and hardware and very little interference, so you really can run a RTOS alongside a traditional Linux system.
There are a continuum of different virtualization designs; this extends the options available in a new direction. You use LXC if you want everything to be a Linux system sharing a kernel, and want control of what resources are shared vs. isolated. This can allow you to run a lot more VMs a lot more quickly and with lower resource impact than the other solutions. Xen or KVM if you want a full emulated virtual machine, which can run any OS that you want, and can share CPU, disk, and other resources with the host or other guests. Jailhouse if you basically want to have a separate computer sitting on the same motherboard.