I personally like this counter-argument, lots of real data:
I personally like this counter-argument, lots of real data:
Personal Productivity Secrets
It focuses in the issue you describe, and might provide you with personal tools to help you focus.
You can try with a single-hand maltron keyboard. I have used the two-hand version and it is quite comfortable for me.
And that is why the progress bar should represent progress of the task, not remaining time. The correct way is to show progress in the bar (as in percent of the total task), and a text label with the estimated time to completion below. The label can change in any direction. The progress bar (if the progress is measured properly) can only go forward.
I remember ObjectVision as an interesting example of visual programming by configuring blocks. Unfortunately it was very limited, and one reached the boundaries quite fast. IBM VisualAge is another story. I cannot remember a more complete, truer IDE than this. I used it mainly in Smalltalk and Java, but other versions for C/C++, Basic, and even COBOL existed. But it really shined in Smalltalk, it native environment. VisualAge allowed to put the pieces of a program together graphically, autogenerate code, switch to code and extend it programatically, keep version control of every time you push save, debug in place.... it was an amazing product. I am glad many features where migrated to Eclipse, but I miss the overall experience of putting a visual prototype together in one afternoon.
A PhD can help you reach some positions that otherwise will not be available for you. It is a common requisite for academia and research positions in the industry. Sometimes also helps with management tracks, but the argument for this is debatable.
In general, a PhD does not have a great career ROI, because you get a much better position/salary inside the industry by spending the same amount of time (3-6 years) specializing in industry-related topics. And this difference never catches up if you do a PhD. I am careful to point this out when I am interviewing PhD candidates, because if they are in for monetary reasons, they might have better alternatives. Also, a PhD sooner or later gets under your skin, and you need a strong motivation to finish it. You need to like it and be at least somewhat passsionate about it. If you are not sure of the reasons why you are doing it, you might drop out at that point.
If you want to do research, if you feel that, for personal reasons, you want a PhD, by all means go for it. If you want to improve your knowledge/resume/employment, I would suggest to consider other, more focused ways to achieve this goal.
I never had a problem with NVIDIA support, but that might be just my experience. I personally have no issue with the drivers being closed sourced. Just my experience.
On the other hand.. I do experience the lack of support from AMD, both in the code and the people part. Drivers are full of bugs, get broken all the time, and get in the way of me doing my work.
In terms of open source, I do tip my hat to Intel: the official drivers are open source, and work really well.
NVIDIA's driver is not open source, but the support is great. The drivers work, the give few issues, 3D, CUDA and OpenCL are fully supported.
Try that with AMD drivers.
There is a quote (somewhere, I cannot remember who said it), that the NVIDIA drivers have more LOCs than the Windows OS. So it is a huge piece of software... not so easy to "just code it again".
I decided to share, for those interested, my experience with WP7. As background: I am a programmer, I have developed for iOS, and I am a Linux, Mac and Windows user in a regular basis. I used an iPhone since the original version, and have used iPhones, Androids and, for the last year and a half, a WP7 (I have the feared Samsung Omnia 7). I work at an university and I am not related to M$ or Nokia or any other phone company in any way.
I would like to start with the positives: Windows Phone is a very fresh operating system. It is visually extremely attractive, fluid and comfortable to use. In terms of the design, it focuses in the information, giving text a central place when text is the focus (of course, images and videos when they are the focus). It succeeds in this most of the time. In addition, they data aggregation is the best of any platform (ok, maybe WebOS was better, but I have no experience there;
Now to the not so nice things.. (and I have quite a list). The first one is this thing with text overflowing the screen to the right.. it a design decision that I cannot understand, but I have learnt to live with it (still don't like it). The aggregation sources are at the moment locked to what M$ offers: i.e. you cannot are your own sources. This means no CardDAV, no CalDAV, no LDAP.. which sucks for enterprise environments. You are also out of luck with VPNs, because they are not supported yet (sigh....). The email app is OK for normal users, but if you use folders heavily, or have thousands of emails in your inbox, it is not the best app (also, it only supports server-side search in M$ and Google accounts). Battery life is short (but is that the fault of the OS exclusively?), I have to carry 2 batteries when I am on the road. And then there is the lack of apps: it is improving, but it is nowhere near the level of the apps in iOS or Android. And finally... programming in WP7 can be really difficult, which I think is the biggest drawback.
For short, the platform is still not fully mature, and it is clearly a platform for everyday users. It covers the needs of a user that wants to stay in contact with his friends, uses Facebook, Xbox live, play games, checks email, tweets something, finds some directions in the map, etc. Power users and enterprise users will find the platform still lacks key functions like VPNs and Calendar servers (heck, it only supports multiple calendars in Live accounts, even Exchange servers are limited to one calendar). But I find it to be the most polished interface of all: it makes good use of visual elements, it focus in the information (displaying, consuming, sharing), and gets the job done.
So, from this point of view, I believe the next release of WP7 is going to be critical for its survival. The OS is great for everyday users. If it addresses the key issues to appeal to the wider audience of business folks, it will become a hit. In my opinion, M$ has to embrace openness in the platform, giving more choices in the software side, and providing a better development experience.
What is now proved was once only imagin'd. -- William Blake