|
|
A story about our classy protagonist - our office building has an atrium that runs all the way through the middle of the building. The first time I met this guy was when I sat next to him at a team dinner and he told us quite proudly that he's been able to look up the skirt of one of the HR girls by sticking his head into the atrium and looking up.
|
|
|
|
|
 Well... he sounds like a keeper!! Err... creeper!!
|
|
|
|
|
|
I don't believe it
PooperPig - Coming Soon
|
|
|
|
|
Seems to fantastic but it's on the web so it's got to be true right? 
New version: WinHeist Version 2.1.0 Beta
Have you ever just looked at someone and knew the wheel was turning but the hamster was dead?
Trying to understand the behavior of some people is like trying to smell the color 9.
I'm not crazy, my reality is just different than yours!
|
|
|
|
|
It also seems too fantastic 
Judging by the number of comments from folk who fell for it, I think I might start marketing bio-luminescent moss as a miracle-cure-all.
PooperPig - Coming Soon
|
|
|
|
|
Yeah it does make one wonder?
New version: WinHeist Version 2.1.0 Beta
Have you ever just looked at someone and knew the wheel was turning but the hamster was dead?
Trying to understand the behavior of some people is like trying to smell the color 9.
I'm not crazy, my reality is just different than yours!
|
|
|
|
|
Mike Hankey wrote: Yeah it does make one wonder?
??? It does?
Your use of question mark proliferates the conspiracy perfectly? 
|
|
|
|
|
I think he may have been wondering if it made two wonders.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I think that entire website is satire, nothing on the homepage looks remotely plausible
What's amazing is that every article has comments by people who appear to seriously believe the content, terrifying!
|
|
|
|
|
|
"The problem with stories on the Internet is that it is often rather difficult to verify their authenticity."
Sir Winston Churchill, 1938
Life is too shor
modified 1-Sep-14 18:01pm.
|
|
|
|
|
What a visionary!
New version: WinHeist Version 2.1.0 Beta
Have you ever just looked at someone and knew the wheel was turning but the hamster was dead?
Trying to understand the behavior of some people is like trying to smell the color 9.
I'm not crazy, my reality is just different than yours!
|
|
|
|
|
Brilliant.
But make it "often rather difficult", rather than "rather often difficult" (and note that, in this construction, he would have pronounced the 't' in "often").
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Noted and THX.
Speaking of eunuchs:
only a git would use unix
Life is too shor
|
|
|
|
|
Hey, careful!
Apparently, we Britons are sensitive to jokes...
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Recently I posted about getting a new computer (i7 with 8Gb Ram) and still having trouble starting the Android Emulator.
It was stuck on the Android splash screen. Could not figure it out. It was driving me crazy. Then I ran some command-line stuff
c:\>adb shell ps
(adb.exe found in ADT \platform-tools)
Stuck Writing To Emulator's OS Image
I found out that even though the thing was stuck it was actually running a ton of processes.
Then I noticed that there were a bunch of installations the android image was trying to do but were failing, but it kept trying (for hours).
Finally, I stumbled upon a couple of solutions:
1. add the android home path which points to the location of the android images to environment variables (see below).
2. (most important) make sure that the path to your android images is FULL READ/WRITE access. Those files had read-only access before.
The OS is really just a file on your computer (obvious to many) and if your computer cannot write to that file then the emulator cannot either and it tries and fails forever.
This fixed it. Now emulator starts in seconds.
Now I'm working through a great book on Android programming:
Android Programming- The Big Nerd Ranch Guide [^]
ANDROID_SDK_HOME=C:\Dev\Android\.android\
|
|
|
|
|
Have you tried the Genymotion[^] emu? It's insanely fast. And free for personal use.
/ravi
|
|
|
|
|
I was going to try it... Well, I actually did try it on my older laptop (Celeron) and it didn't work over there either.
The only problem I had with Genymotion is that I had to install VirtualBox and I just didn't feel like installing that on my new laptop unless I absolutely have to.
However, a lot of people have told me to use it too, so it must be great.
|
|
|
|
|
newton.saber wrote: Celeron
That may have been part of the problem.
newton.saber wrote: The only problem I had with Genymotion is that I had to install VirtualBox
FWIW, the Genymotion install is a self-contained installer that installs all its pre-requisites.
The standard emulators worked for me, but took forever to spin up on my Xeon quad core, 16G RAM, SSD box, which led me to Genymotion.
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: Celeron That may have been part of the problem.
Yes, celeron was definitely the problem with running VirtualBox and also the problem with running the emulator at a realistic speed.
My new i7, with 8Gb RAM -- and I keep saying that in an attempt to generate envy across the Internet -- absolutely crushes the emulator. By that, I mean I can start it in seconds and deploying running a new version of the app is like I always expected it to be.
|
|
|
|
|
Awesome!  I hope to experience a similar feeling of joy with my new box[^].
/ravi
|
|
|
|
|
Yes, good luck to you. Congratulations on new computer. It had been over 5 years for me & my old computer
Was very weak. Your new one sounds like it'll take on any task. I can't believe how well mine performs & it isn't as good as yours.
|
|
|
|
|
I have installed and re-installed Android Studio, and eclipse ADT a few times, and never come across this issue. The emulators always start first time, the defaults and my custome types.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
