Best signature ever mate!! I'll even pretend that I did not read the MBA and intelligent thing...
Yeah, sure, play a driving game and you can become a pro race driver. A whole generation of geeks spent ages with leisure suit larry, and what did we get in real life???
I've been reading about exciting devices that will be released with Android for quite some time now. I am a developer and I am more interested in the device as a developer than I am as an end user. iPhone has a lot of roadblocks for me, I need a Mac to develop on it, which is a huge cost for me at the moment. Apple's policy about publishing apps is another story which has been discussed a lot.
The problem is; even if Android is emphasizing openness, its development model seems to be "we know what is good for you". As far as I can see, there is no low level access to device for developers, and you are supposed to use Java, with some JNI capabilities for process intensive tasks. Native code can only be isolated chunks which still can't access device using C/C++.
This is most likely to ensure that code runs on all devices, but this is a choice that should be left to the developer, at least if you're claiming that your platform is open. If I decide to develop something on a particular phone, knowing that it may not work in the same way on other devices, this is my choice, and I should have this option.
For whatever reason I have, I want to have native apis for C/C++ and Android does not seem to offer this. Maybe my money is not that important, but for things like gaming, which will probably be huge on the iPhone quite soon, this will be a problem.
I own one. Probably the largest screen size in any electronic reader. Lets you annotate, and can read any pdf, it is under your control.
I can easily read A4 pages with diagrams etc. For me, there is no alternative to this device. All other display technologies hurt my eyes if I read for hours, and I have to read for hours. Also there is no way on earth I can carry around all the docs I need all the time, and even a tablet pc is too thick to hold in your hands to read comfortably. Don't forget the heat problem too. Digital reader solves all of these problems.
The cons are: very expensive, buggy software, not so good battery life. No security, so I can't carry around critical docs in this.
I still have no doubt that this is the future of reading, but I'm afraid of Kindle type of products being the only option: where content and functionality is under strict control.
Here you go: http://www.bmj.com/cgi/content/short/327/7417/716?fmr It is titled: "Understanding sensitivity and specificity with the right side of the brain "
Exactly written for the purpose. PDF should be available freely.
I have to build quite complex tools using GEF and GMF, and there are many cases where I'd like to have the power of Java2D, and reuse some of the great frameworks out there built on Swing.
More and more people are using AWT/SWT bridge, since SWT does not provide an underlying drawing framework as rich as Java2D.
Eclipse has great things like EMF, and the platform is number one choice for tooling, but when it comes to things like Bezier curves etc, Swing is much easier to use. So are we going to see more developer friendly versions of Eclipse where Swing is more available to us?
if you are coming from a programming background, I assure you that you'll hate gui oriented tools like spss. if you have a slightly better understanding of probability and the notion of sampling, you'll find that the way r approaches data as a whole feels very nice for a developer.
in data analysis, you'll be transforming, filtering typecasting data. you'll be turning numbers into nominal values, you'll be sampling from complex distributions etc. writing code to do these lets you stay in complete control of what you're doing and at least for me looking at a function line by line is a much better way of seeing what I'm doing, instead of clicking on icons and selecting menu items in a particular order. the whole process is documented in code, and for me it is much easier to map the things I'm doing to statistics.
the downside of R is, as you start dealing with more and more data, things become a little bit harder since R takes all data into memory and processes it in memory. scaling into very large amounts of data is not easy, at least I can't afford as much ram as necessary (my data sets are really huge). the most important advantage of some commercial tools in my work is that they can treat data as a stream on disk, and even if it takes longer, it is possible to process huge amounts of data.
R forces you to think about what you are doing, instead of hiding behind spss and saying, well these are the results spss has given us, when we clicked these buttons and menus. my 2 cents of course.
Those who can, do; those who can't, simulate.