There are so many computer features that we’ve become accustomed to. Who hasn’t used Ctrl+F to search for text on a Web page or a document? Who hasn’t used Ctrl+C & Ctrl+V to copy and paste something? (…obviously, I’m not targeting people who have never used a computer before, or who manage to use them without a keyboard)
If you could have any of these keyboard shortcuts as a real-life (super)power, which one would you want? Vote below.
So far, the results have been interesting. Looks like most people don’t want to deal with real life.
It’s the end of another year and the end of a ground-breaking decade. Let’s look back at what’s been accomplished in the years of 2000–2009, focusing on technology.
Windows has entered a new era
The decade—indeed, the century—began with Windows 2000, which I consider the first great version of the operating system. XP was the version that brought widespread success, and people just seem to refuse to upgrade; even today, almost three quarters of the computers on the net are on XP.
Despite the dismal failure of Windows Vista, it too brought change, which was followed by the enhancements of Windows 7. Compare my desktop today to the ugly screens of a decade ago:
Apple deserves an honourable mention for the ground-breaking work they’ve done on the Mac, elevating it to a newly trendy status.
Portable media players have completely changed
A decade ago, CD players and tape-based Walkmans were still the norm for ‘portable’ audio players. The iPod, launched in 2001, entirely changed the game. (I suppose this and the iPhone were the “comeback of the decade”.) It was no longer a device that played removable media. That was followed by thousands of other portable media players, to which the public generally refers inaccurately as “MP3 players”, reflecting the popularity of the 15-year-old MP3 format that has also been notorious for illegal file sharing (see below).
Cell phones and mobile devices have become ubiquitous
These devices used to be ugly, huge and heavy objects. As we move into 2010, cell phones have become more compact (usually this means thinner and lighter) and more powerful.
Mobile devices have become truly powerful. The iPhone, purportedly the most popular cell phone of 2009, is one of the biggest platforms for software development. And it has a touch screen. RIM’s BlackBerry, initially launched in 1999, is the most popular smartphone among business users.
Ordinary people begin to embrace ultra-portable netbooks for lightweight computing. The move to mobile is probably the most noticeable trend in end-user gadgetry in this decade. Continue reading “Happy New Year!”
I’ve been receiving these letters every single year a few months before any one of my domains is set to expire.
This company is clearly harvesting WHOIS data in violation of their ICANN agreement to send official-looking “expiration notices” to domain owners, many of whom unwittingly send in payment, unaware that the “Domain Registry of Canada” is merely a company attempting the entirely unethical practice of domain slamming.
Since 2001, this company has been soliciting domain transfers under the guise of renewing the registration with the existing registrar. Of course, their prices are ridiculously expensive — $40 per year for a domain name — and that’s part of why I didn’t fall for it, since I operate my own domain registrar and I know the value of domain registration services aren’t that high.
An early example of the domain letters from 2002 is published online.
In 2003, the Federal Trade Commission settled with the sister company “Domain Registry of America” to stop their misleading business practices. The way they decided to comply was by adding a little blurb that blended into the text, one that few people seeing an official-looking letter would read.
They’ve changed it a bit now, to uppercase and bold text, but the premise of their operations is still the same.
The envelope is misleading. Indeed, the colour and layout of the envelope nearly exactly matches that of an official Canadian government letter, except for the return address in the top-left. And there they’ve neatly placed a maple leaf, knowing that it is associated with the country, and by extension, the government.
Even the NAME is misleading.
The letter has been changed in recent years, but still carries the same layout that I recognize from as early as 2005. The prices are ridiculous; a .net domain isn’t worth $40/year. (I know; I was selling them for $7.99 last month.)
That letter just irritates me. Sentences like “take advantage of our best savings” when you actually pay $30 more, misleading phrases like “You must renew your domain name to retain exclusive rights”, and worst of all:
“Failure to renew your domain name by the expiration date may result in a loss of your online identity making it difficult for your customers and friends to locate you on the Web.”
It’s rare for me to be this angry. But it’s a ripoff.
This is the first part of my posts about Office 2010. Last night, I received an invitation to the Office 2010 Technical Preview, and today, I am attempting to install it on my Windows 7 RC machine.
Legal notice: since this isn’t a private beta, I am allowed to discuss the preview and my experiences with it. However, I am not allowed to share product keys, installer files, and documents to which I have access by virtue of the invitation. The contract that binds me with reference to the technical documentation quotes as follows:
You […] agree: (a) to refrain from disclosing or distributing the Confidential Information to any third party for five (5) years from the date of disclosure of the Confidential Information by Microsoft to Company/You; (b) to refrain from reproducing or summarizing the Confidential Information…
Thankfully, there’s a public pressroom for Office 2010 information, from which I was able to get equivalents of the stuff in the confidential documents. Here’s some information for you.
Office 2010 is designed to work on computers with very limited resources; after all, many businesses were concerned that they would once again need to upgrade their hardware. Office hasn’t really necessitated hardware upgrades in the past; Office 2003 ran very well on old Dell OptiPlex machines on Windows 2000, and Office 2007 ran quite well on older XP laptops.
The installers are rather compact; the Technical Preview 32-bit/64-bit installers for Office 2010 Professional are no more than 600 MB each.
I’m currently on Windows 7 RC 64-bit edition, but I resolved ultimately to install the 32-bit edition of Office 2010. This is due to the following reasons:
The 64-bit edition of Office 2010 does not support most add-ins.
Users of software with add-ins in Office programs will find that most of them do not work with the 64-bit edition of Office 2010. Software vendors are expected to release newer 64-bit add-ins, but users must use the 32-bit edition for compatibility with older add-ins.
One cannot upgrade Office 2007 to Office 2010 64-bit.
According to the technical documentation, “2007 Office system cannot be upgraded to native Office 2010 64-bit.“
I don’t work with spreadsheets greater than 2 GB in size.
The documentation listed a number of benefits of using the 64-bit edition. The central point was being able to open large Excel spreadsheets. Since I don’t do this, the benefits of the 64-bit architecture are insignificant when it comes to Office 2010.
Screenshots of my installation will come in the next installment of these posts. That is, after I manage to install it. At the moment I’m getting the following error with the 32-bit installer, after customizing the install and even going through a few minutes of the installation progress bar.
If this persists with the 32-bit installer, I may have no choice but to try the 64-bit installation.
I mentioned previously that I wanted to post how Subversion works (on the surface, for beginners) and how I use it for my development needs.
To create my WordPress plugins, Simpler iPaper and Simpler CSS, using SVN has been a must; after all, the only way to release new versions of the plugins is through SVN. I also keep this site’s WordPress installation up-to-date on the development version using Subversion. Additionally, in my current efforts to develop a working solution for HDTV’s in business and organizational settings, Display UI is being developed using Subversion for version control.
You get the idea. I use it on a daily basis, and for practical purposes. I don’t claim to understand the fine details, but hopefully this post gives you an idea of how I use it and how you can, too.
So what is version control? Simply put, it’s a way of keeping track of the changes made to files. It’s often impractical to make manual backups of a file before every set of changes to it, so version control systems like CVS and SVN emerged to help people — especially developers and programmers — keep track of their files, share changes with team members, and prevent stupid mistakes.
Accidentally deleted your code? Revert your changes. Came up with an ingenious way (that works) to do something? Commit your changes. Need to get the latest revision of all the files? Update the working copy.
Perhaps the most practical application of systems like Subversion is in team development. When three or more people are working on the same set of files, it’s useful to be able to merge the changes seamlessly, see the changes others have made, or even work separately on branches (kind of like forks) and tags (usually released versions that are being maintained).
Let’s talk about how to use it. Hard-core programmers often choose to use the command line tools, where they type commands like svn up to update the files. Beginners will be glad to know that there are implementations with GUI‘s, like RapidSVN and TortoiseSVN. Eclipse users may use Subversive or Subclipse, “team providers” that let coders easily perform version control tasks inside the IDE.
Assuming that you’re using the command line binaries — which you can get from the Subversion site, and I recommend official CollabNet builds where possible — most of the basic tasks are rather easy.
Instead of right-clicking and picking options from a menu, tasks are done by typing commands.
First of all, a ‘repository’ is a hosted location containing all of the code, revisions and metadata. Often, one can access a repository via HTTP, as in the case of WordPress, which is found at http://core.svn.wordpress.org/ .
To ‘checkout’ a repository means to make a local copy (known as a ‘working copy’) of the contents. That’s what we have to do first when working with an established project: get the code from the repository.
To do so, type the following at an open shell (on Linux/Mac OS X) or command prompt: (don’t type the ‘$’ — that’s just a placeholder for the prompt you’ll see, such as frederick@ubuntu-pc:~# or [frederick@fedora-vm Desktop]$ — the specific prompt will differ depending on your machine and platform)
Awesome! WordPress has just released the release candidate of WordPress 2.8, which seems to contain an awesome amount of improvements over WordPress 2.7 (most of them subtle and unexposed to the end user). I’ve been running the trunk version of WordPress for months now, and I have to say that WordPress 2.8 is stable and usable.
If you want to stay up-to-date with WordPress, you can try running it from SVN. I’ll post a little guide on how I do it soon.