1) The idea of the web is that the boundary between consumer and creator is very blurred. It is a world-wide, distributed environment. Making the tool you consume also the tool to create empowers a lot of people. Consider yourself a budding publisher on a very bad connection in an emerging country: you download a browser to surf the web, and that one now also enables you to create something for it. Downloading xCode or Android Studio would take ages. For developers, this is also an advantage: you use the same browser your end users have. In the past developer add-ons interfered with the rendering of the page and the performance of the browser. This gave you false results.
2) Whilst devtools make any browser bigger in initial file size (including Chrome and IE), it is not a large part of the main download (fonts are actually a huge one). The performance hit is to the overall computation (much like a standalone tool would) but isn't impeding on the browser performance itself.
Not really comparable. Composer was a WYSIWYG editor for web pages; the WebIDE is an editor, but more importantly it manages the packaging and creation of manifest files of apps for you. I started with Composer and the output was so awful that I learned HTML instead. This doesn't hide any code from you or generates things you don't want. The templates of the apps are maintained by the community on GitHub.
X-Tag leverages the joint polyfill Google is the general maintainer of (Mozilla contribute code to it). It's the same one at the base of the Polymer stack.
Polymer, in comparison to Brick has a much more ambitious approach to being the framework to build apps with instead of aiding the creation of apps. Comparable with Dojo or .NET instead of jQuery.
Frankly, I just messed this up as my job takes 120% of my time and I hardly ever have a good connection to mess with the internals of the blog. I'd rather write :)
You are totally right, I have moved the blog from my old domain wait-till-i.com to my name about a year ago and realised in November that all my ads got killed that way (see how I game that system) :)
This was the first to come in, and I felt rather torn about it. It was needed to get one in to get the affiliate program (which changed owners in between, another thing that is kind of fishy) kickstarted again.
The good bit about these is that all they want is a link. No JS, no Flash, nothing, which is why I considered them in the first place anyway.
Utterly fair points though, so here's a fat header above them and a nofollow on the link.
This is one of the ads I have on my blog that came through an ad affiliate program. So yes, I have ads on my blog, which is my right as a content creator. You can, of course see this as a conspiracy or something evil. :)