For the time being, using the model A on purpose because it is the most resource-constrained RPi. Performance-wise, it feels like a sluggish P2/P3 era machine trying to cope with a Windows XP install that has everything and the kitchen sink installed.
Yes it runs a modern web browser, and surely it would run a full office suite too (LibreOffice in this case, not any of Microsoft's office suites). As soon as you drop back to the commandline though, there's no performance issues to complain about. 512 MB RAM (model B and B+) provides more headroom, the newer RPi 2 comes with 1 GB RAM and a much, much more powerful CPU part so that would surely work.But if that kind of thing is the intended use, then (imho) you're using the RPi wrong. For those things you'd be better served with say, one of Intel's NUC (Next Unit of Computing), a cheap mini-ITX size PC, a Mac Mini, or something like that.
Better regard the RPi as a mobile-phone-hardware in a box / modern-tech Acorn BBC / microcontroller on steroids. With up-to-date (but not necessarily that powerful!) video hardware, and (most important!) a set of general purpose I/O pins, to attach DIY electronics to.
The biggest advantage that I see here, is a) that's its cheap, b) that it's small, c) that it's cheap,
and d) that it's very easy to swap operating systems on, each of which can run "on the bare metal". Including exotic ones like Risc OS, Plan9, Inferno, or whatever gets ported to the RPi @ some point. Oh and and e) let's not forget the tinker-oriented community around it!Indeed, that is what's announced by Microsoft. So not yet materialized (and no 100% guarantee it will, either). Note that's limited to the RPi 2. Also there's talk of Sailfish OS on the RPi 2 (another Linux based mobile OS).RWAP wrote:The new RPi (2015) will apparently have Windows 10 at some point
So that took a bit of Googling, and edit a config file to force optimal screen resolution. Another bit of editing some config files, and internet connection using my Wi-Fi dongle was in the air. 
of course a big % of that is libraries, 20 different programs for the same task, dummy/documentation packages, etc. But obviously you wouldn't run out of things to try... 