It’s been an overwhelming—and hilarious—week for us here at Texts from Hillary (TFH). What started as a joke at the bar between two friends turned into a national conversation about Secretary Clinton and went as far as talks about 2016.
After a week that included 32 posts, 83,000 shares on…
(Source: j.mp)
Italian Surgeon Claims High Success Rate Against MS
By Sheila Casey / RCFP
A former vascular surgeon from the University of Ferrara in northern Italy has apparently cured his wife and 65 other people of multiple sclerosis (MS) by using balloon angioplasty to open the narrowed veins…
By Sheila Casey / RCFP
Numerous studies have found that a common mineral heals the brain by stimulating the growth of new brain cells and protecting brain cells from every known neurotoxin. It has been shown to reduce the incidence of violent crime, homicide, suicide, and drug…
National Academy of Science member and Distinguished Professor endorses
David Ray Griffin’s work exposing the truth of 9/11By Lynn Margulis
I comment here on the nanotechnology aspect of Jerry Mazza’s masterful review (Rock Creek Free Press, January 2010, page 6) of David Ray…
By Carla Stea / RCFP
On December 18, 2009, The United Nations General Assembly, by an overwhelming majority, adopted Resolution 64/147, A/C.3/64/L.53 put forth by the Third Committee, entitled: “Inadmissability of Certain Practices that Contribute to Fuelling Contemporary Forms of…
pk11:
в…
Most of the people who have done server side Java development are approaching Android the same way. Android is Java, right? So where is my dependency injection? How can I configure things with annotations? How can I unit test? How can I just include my usual 400 libraries or my favorite JVM language with giant dependencies? Turns out programming for an embedded device is different. You do not use dependency injection and program against interfaces because performance and lazy loading are everything. You test most parts in context (using Instrumentation) and yes, configuration is done in XML(thankfully, resources at least get translated into classes). Also, library size and speed matter (so most JVM languages like Scala, even after the proguard treatment, are unfortunately out of question). And finally, you will feel the pain of not having (less noisy) closures in java more than in server side development, thanks to Android’s callback-centric design.
That all being said, there are things you can do to improve your development environment, so here is a list of tools that I found particularly useful.
By Sheila Casey / RCFP
Numerous studies have found that a common mineral heals the brain by stimulating the growth of new brain cells and protecting brain cells from every known neurotoxin. It has been shown to reduce the incidence of violent crime, homicide, suicide, and drug…
Some months ago, I posted a list of links to recent discussions of Gaga and Beyonce videos. I will update and expand the list here; since the previous version was pre-“Telephone”, and a lot more has been posted recently.
As we’re all aware by now, one of the worst environmental disasters in recorded history is underway in the Gulf.
As helpless as you may feel, you can do something right now by donating to a Gulf protection group like Save Our Gulf, the National Audubon Society, or the Greater New Orleans Foundation.
To get all of you involved this week, we’re replacing Tumblr’s usual ocean blue with a new heart-of-BP-executive black and letting you donate without leaving your Dashboard.
Donating will also unlock the Limited Edition Black Dashboard as an account preference.
pk11:
в…
Most of the people who have done server side Java development are approaching Android the same way. Android is Java, right? So where is my dependency injection? How can I configure things with annotations? How can I unit test? How can I just include my usual 400 libraries or my favorite JVM language with giant dependencies? Turns out programming for an embedded device is different. You do not use dependency injection and program against interfaces because performance and lazy loading are everything. You test most parts in context (using Instrumentation) and yes, configuration is done in XML(thankfully, resources at least get translated into classes). Also, library size and speed matter (so most JVM languages like Scala, even after the proguard treatment, are unfortunately out of question). And finally, you will feel the pain of not having (less noisy) closures in java more than in server side development, thanks to Android’s callback-centric design.
That all being said, there are things you can do to improve your development environment, so here is a list of tools that I found particularly useful.
One of the questions we always...
Getting a decent data connection at SXSW can be a challenge, given that it attracts what may be...
This week’s cover: the Navy SEALs.
Like many of us, I’ve been thinking a lot about Steve Jobs the last few days — thinking...
