562 karma · joined October 21, 2013
Apps don't have a good way to convey that they are using HTTPS, so I don't like the idea of entering my credit card details in an app. Most internet banking gateways in India aren't yet mobile optimized, so that's inconvenient too. (Internet banking is a popular alternative to debit cards in India; merchants re-direct users to their bank's website where users can login and agree to paying the merchant. It's actually a lot more convenient than credit cards because you only have to remember your bank account's username and password.)
https://dl.dropboxusercontent.com/u/53155453/cookoo_kicad.zi...
Not sure if this is the latest version.
Schematic - https://github.com/s-gv/cookoo/blob/master/schematic/whistle...
"The hopeless ones become college professors" - http://lemire.me/blog/archives/2015/02/25/hopeless-ones/
Also, is binary ISA translation restricted by patents?
Much has been said on this topic. So, I'm just going to post two links that I think are interesting.
Joel Spolskey claims that Java isn't hard enough to separate good programmers from the bad: http://www.joelonsoftware.com/articles/ThePerilsofJavaSchool...
This article claims that competency of CS grads is going down: http://www.education.rec.ri.cmu.edu/roboticscurriculum/resea...
http://www.joelonsoftware.com/articles/LeakyAbstractions.htm...
Yes, the link is about JS. But there are relevant pieces.
Quote from the article: "If you want to process camera images on Android phones for real-time object recognition or content based Augmented Reality you probably heard about the Camera Preview Callback memory Issue. Each time your Java application gets a preview image from the system a new chunk of memory is allocated. When this memory chunk gets freed again by the Garbage Collector the system freezes for 100ms-200ms. This is especially bad if the system is under heavy load (I do object recognition on a phone – hooray it eats as much CPU power as possible). If you browse through Android’s 1.6 source code you realize that this is only because the wrapper (that protects us from the native stuff) allocates a new byte array each time a new frame is available. Build-in native code can, of course, avoid this issue."
Source: Why mobile web apps are slow - http://sealedabstract.com/rants/why-mobile-web-apps-are-slow...