sharepoint - SSRS 2008 vs SSRS 2012 -

i've been trying figure out if makes sense use ssrs 2012 powerview vs using ssrs 2008.

i've following questions:

1. what's better in ssrs 2012 without powerview(ie without using sharepoint)?
2. what edition of sharepoint need make powerview work ssrs 2012?
3. does make sense learn , use sharepoint if can barely utilize pluses of sharepoint or powerview instead of ssrs 2008 or ssrs 2012 without powerview/sharepoint?

i can address overall question not first 2 bullet points have not used sharepoint enough give version differences on it.

powerview have ever done dll allows report object created add on excel. these objects can hosted in sharepoint in library. downside need have dll's , add on sharepoint use it. far know committing user's going sharepoint option. make kind of neat though make believe call 'powerpivot' client dataset made in excel file report off of. option shop works sharepoint extensively. have not heard of many places using client facing front ends or external reporting.

ssrs's newest invocation ssrs 2012 have seen in development exact same thing ssrs 2008r2 except put 2012 in namespace. there may minor tweaks on naming , intellisense , under hood things langauge identical. saying ssrs 2012 free advanced tools ssrs , can port front ends want: html in form talking it's service, asp.net, client app winforms or wpf. created , host reports , can access them anywhere.

the real question people is: "which reports cooler , easier use?" go ssrs, know more of learning curve of understanding sql , little bit of xml , visual studio(very light). powerview more graphical it's parameters , options end user , has highlighted things can mapping interactivity ssrs cannot do. biggest detractor ssrs imho 2 things:

1. it not event based @ all. shows whenever doing mapping or want zoom or perform actions produce other actions or 'events'. can 'click' not on same page necesarrily. trick open new form 'drill through' or use javascript trick cheap man's version of hover on reporting opening form when click.
2. to continue off of 1 way on default behaviors of values of parameters , passing them down. ssrs made happen once @ execution , else happens leave form, not stay there.

saying still ssrs better. tends handle large datasets when presenting them better. not time @ getting them powerview optimizes set locally @ expense of huge excel files. sort of psuedo cubes. fast, have big file size expense. lot of data tend clunky excel based. yes query @ end return faster have huge file. when in reality if skilled @ sql server creating report warehouse indexed off of metrics , cube stuff many reports. ssrs more developers of tsql, versus powerview more analysts know little sql love excel. want 'select * (table)' , form data, not know how advanced groupings on set first , want present finished product someone.