No, but if the researcher the article cites published his findings in PNAS (Proceedings of the National Academy of Sciences 09/2009; 106(37):15583-7. DOI:10.1073/pnas.0903620106 9.81 Impact Factor) it's very likely to have some merit. I did do my research before finding a good article summarizing the work.
As to watching live streaming. Why do you assume you can do just one at a time, watch or do? I stream to about 100 people nightly, and many of those people are actually working on their own project(s) with me on in the background as a support/comfort/buddy layer.
Because multitasking doesn't work. http://lifehacker.com/5922453/...
1. I watched a live coding session a month or so ago and lasted about 10 minutes (the first 5 I ignored because the streamer forgot to turn on audio) before I stopped. This is only useful for those who have enough time on their hands to watch someone code for hours at a time and can't find anything more interesting to watch. I just can't imagine sitting through this all the time.
2. For the developer who is streaming: You can get the same benefit (articulating your thoughts out loud) by using your cat, dog, infant or some inanimate object you can talk to (a Wilson volleyball, perhaps). You'll save tremendous amounts of bandwidth, storage space etc. and won't temp someone who should be making better use of their time to watch you so they can pretend they are doing something productive.
I only allow GMO-free ants to roam my property.
Thanks. If I understand your summary correctly, this sounds like a good security feature, apart from the "killing the process" bit. This seems like a handy mechanism for DOS attacks. Why not just refuse to do the unwanted thing and ignore it, while perhaps logging the attempt?
The VideoLan website still says VLC for Android is a beta at version 0.9.10.
Someone is talking bollocks and, this time, it's not me...
It's listed at 1.1.0 at the Google Play Store, which might be considered more authoritative that what it says on a web page someone forgot to update.
F-Droid was a 1.0.1 a month ago, so same argument. F-Droid lags a bit behind with their releases, so I suspect they will be updating to 1.1.0 soon.
Head transplants has been tried before. In 1970, Robert White led a team at Case Western Reserve University in Cleveland, US, that tried to transplant the head of one monkey on to the body of another. The surgeons stopped short of a full spinal cord transfer, so the monkey could not move its body. Despite Canavero's enthusiasm, many surgeons and neuroscientists believe massive technical hurdles push full body transplants into the distant future. The starkest problem is that no one knows how to reconnect spinal nerves and make them work again. "This is such an overwhelming project, the possibility of it happening is very unlikely," says Harry Goldsmith."
If this is what you consider "stuff that matters" I would suggest getting a copy of the obituaries. Newspapers put them out daily, and there are literally millions of them.
You know, you could have typed your message, enjoyed the cathartic effect of a little bit of snark, then clicked "Cancel". But no.
Since I'm dignifying you with a response, I'll point out that once the obituary is published, it's too late. You missed the point entirely.
I agree. This might be the only story I can recall in several decades of reading
Rust, on the other hand, is something genuinely new: it provides completely memory safety without a requiring a garbage collector at all.
The only way to provide memory safety in a language without a garbage collector is to severely limit semantics. So, either the Rust designers are ignorant or the language is severely limited. In the case of Rust, Rust makes trivial memory allocation, the kind other languages simply optimize quietly for you, unnecessary complex, while failing to work in complex scenarios.
Rust is a badly designed language.
CItation needed. Please give examples to support your assertion, along with alternatives of better design.
Is that because it was named after a great hunter, or because it was named after the leader of the people that built the Tower of Babel - leading to the multitude of languages? Or are you going the Bugs Bunny route?
Because it has been a well known slur for a long time. Bugs' use of it only reflects society.
According to Wikipedia, citing the Dictionary of Jewish Usage, the use of nimrod as slang for dimwitted was first recorded in 1932, but was indeed actually popularized by Bugs Bunny in the 1940s. And apparently nobody knows *why* it became popular as an insult, because there's no real connection between the original meaning and the slang meaning.
[...] I penalize "funny" posts and really wish I could do the same on Reddit.
That's certainly your prerogative, but I have to wonder why? Do you have something against humor? Must every discussion be nothing but dead serious utterances of grave import? Some "funny" comments are certainly childish or base, but quite a lot of them are quite clever and they add a little fun to the atmosphere of the conversation(s).
Nim isn't a scripting language. It compiles to native binaries by default (with an intermediate conversion to C code) and doesn't depend on an interpreter or virtual machine at runtime.
The comments in the "Nim Programming Language Gaining Traction" submission on the front page are pretty awful at the moment. Let's hope you are right and the quality of subsequent comments increases dramatically. I was hoping for better