$35 is nothing. I totally believe in supporting a good product with a very reasonable price.
Compare $35 for Reflector to $800 for TypeMock... $200 for Resharper... $300+ for dotTrace.
If you use something daily, <$50 is nothing... even <$100.
(Just in your example, we are already at $1335 not including the price of Visual Studio itself since the free express edition does not support add-ins such as ReSharper and other productivity tools)
> this mentality seems like it really does a lot to stifle hobbyist exploration of the platform ...
It definitely does seem to stifle innovation on these platforms. Although if you need to use a bunch of commercial widgets in order to try out an idea, you're probably doing it wrong.
Speaking as a 27 year-old-married-with-two-kids Rubyist, it's entirely possible to make a living charging for your work and still give away useful tools and libraries. I keep a GitHub account and publish code there, usually under MIT or BSD licenses, and while I don't publish everything I write, I have benefited so much from the open source that others have written that I contribute back to the community where I can, and somehow manage to get the bills paid at the end of the month.
It's not a reflection of the quality of the software or the quality of the engineers - it's just a fundamentally different culture.
I don't mind paying for good tools (and I would absolutely class Reflector as one), but there seem(s/ed) to be this very top-down mentality in the .NET world that everyone in every step of the chain has to make a buck. Reflector was a shining example of a great free tool in a sea of pay-for dreck, and it's quite sad to see that example die.
It's a bit disappointing, because this mentality seems like it really does a lot to stifle hobbyist exploration of the platform when it's doing cost you $48 in assorted widgets to build the toolset you need to try out an idea.
Edit: I should clarify that I don't think this is a bad thing, and I absolutely feel that Reflector justifies the price tag. The story just sparked some memories of my time in .NET that go a long way towards explaining why I'm not a .NET developer today. My time doing .NET development was in a professional context for my employer, so it's not like I couldn't get the tools due to cost issues, but the massive culture gap left an impression on me.