It’s been a long and busy year. I have tried to keep the good stuff coming down the pipeline for the few readers I have. Among other things, I wanted to drive up commentary from users but that goal was not achieved this year. So I’ll shoot for that in the upcoming year, and maybe some Nexus-magic will help with that.
I covered a few topics this year closely: the rise of the Optimus V and the disappointment of the Triumph. My traffic spiked due to these two phones coming out of the depths of Virgin Mobile. Of course, there was other important content too that found high marks. So, here we begin the top posts (via traffic) from 2011!
This review set me apart for a couple of weeks. CNet and other major news sites attempted to write reviews but it always seems that those are washed out and are not typical. Nobody reading blogs is average so why average your own postings? Anyway, the post described many details of the new phone and why I liked it. I compared to the Intercept, that horrible excuse for a phone, the iPhone and the iPod touch. If I wrote a year-later review though, things would be different.
Nothing is more annoying to me than restarting Windows, you know, trying to get work done, then a couple of minutes later you’re doing something important and the Java updater comes up to complain that Java 6 Update 34 is available. Why can’t it be like Chrome? Update silently, in the background, and maybe let me know something changed when I launch it again in a couple of months.
Remind me again, why do I have Java installed? Crickets.
Since this is the third highest ranked post of the year, I gather that this was a huge problem for a lot of people. Radio Shack was enough to accept the phone back when I told them it had dust under the screen, but get this – I had to pay for the phone twice. When I bought the Optimus back in February, it was priced via Virgin Mobile at $149.99 and Radio Shack had the same price. When I went back to return the phone due to dust under my Radio Shack warranty-plan, the price had gone up to $199.99 via Virgin Mobile (possibly to do popularity or constraints). Radio Shack’s deal is to give you back a gift card for the value you payed them originally, so that was about $165 (149+tax), but since the phone had gone up, I had to pay another $79 anyway to get the phone again ($199+warranty plan+tax).
I wanted to make a Symfony 2 driven CMS but I couldn’t. Why? Because 1and1 fails to support the current stable version of PHP 5. PHP 5.2 has been out of favor by PHP.net for at least a year and there is still no progress. Since it’s so popular, I suspect many people want a solution to this problem.
Someone needs to make a GetPHPUpdated.org or something. That way, we can make a huge petition to get PHP on 1and1 updated, finally.
Once you get an Optimus V, you love it to death. Once you have it for a few months and use it consistently, you realize it does not scale well. The Triumph was a good phone on paper, but the build quality and the horror stories drive the masses away from it. There is still hope, that the Optimus Black may come to Virgin Mobile as a secondary top-tier phone to sit alongside the Triumph. Look at how many of us have that hope. Please, Virgin Mobile, please, give us a phone that does not suck.
I haven’t looked into this since I found it in summer, but it was odd to me that there was some PHP 5.3 stuff lurking around on 1and1’s servers. Through a toggle in the administration panel, you could easily make something appear. I think since then, the version has changed to PHP 5.4-dev, but again, it means nothing. I think this means the people want PHP 5.3 if there are two entries in this list.
There is nothing like paying $1500 and going home only to find out your new MacBook Air is 20% slower than it could be if you had been lucky. The SSDs used in the 2011 Summer MBA models varied, some slow, some fast. This post was an appeal to just find the answer, instead of having to watch a four minute long video. How about 40-words instead?
So, where is it Apple? Myself and many others want to know. In Safari, the standard for navigating back and forth between webpages is intuitive and easy, just a two finger swipe left or right. In Chrome, for months now, the same has been true. In the Mac App Store, there are back and forward buttons, but the functionality is missing. In the Finder too, the buttons are present but the functionality precedent is not there. So much for consistency.
In makes sense that when people were looking for other Lion gestures, they’d want some in Chrome too. Chrome’s implementation is interesting, since it does not provide previews. It just uses an arrow that gradually fades in from transparent to completely solid.
Can I ask you a question? Have you ever been out of memory? Has the memory ever been out of you? Well, if so, disable your plugins. WordPress is often installed on shared hosts with severe memory limitations. That causes a lot of problems when upgrading to a new version. Or it used to when WordPress would download all new files regardless of what has changed. Since it has a manifest, it can simply updated the changed files.
This year has been great, and there has been many wonderful posts. I hope this next semester brings out as much content as this fall, but as it usually goes, I go quiet from some point forward until summer when I am off on vacation yet again.
Have a good one.