It *does* make an other account with little-to-no privileges. That's the point.
Think of email attachments. You double-click on an email attachment, and it contains malicious code. What's the worst it could do?
If it has root permissions, it could install an arbitrary virus into your system. If it only has user permissions, then it could still do some bad stuff -- like, say, encrypting all of your documents and then demanding some money sent to an overseas account to "get it back" -- but it could not fundamentally change the rest of the system. Its malice is limited to /home/drostie/, and cannot spread to system-critical directories like /bin/ -- or even to other accounts like /home/girlfriend/.
In the olden days, everybody ran Windows XP with Administrator privileges, which made it very easy for viruses to take over your system. I don't know how much has happened with Windows since then, because I made the switch to Ubuntu at the close of that era, rather than learning to use the crap that was Vista. But it was a serious problem that led to a proliferation of rootkits and so on.
And it doesn't have to be that way. When you are checking emails and browsing the web and reading PDFs, you don't need to install software. You don't need those root permissions. When you finally want to say "okay, there's a new program that I want to install," okay, you can use the superuser account to install such things seamlessly.
The program sudo is actually pretty nice here. It lets you specify in a separate file some commands that you want to succeed automatically without password. So, for example, I have a shell script installed in /usr/local/bin which restarts some services; it is listed in my "sudoers file", so that I can just type "sudo do_stuff" and it runs as root without a password.