KDevelop 4.7.0 Released
There is a huge amount of FOSS that has an entire "front" web page that tells people in exquisite detail what changes have been made, who contributed, how others can get involved and what bugs are outstanding without ever mentioning what the hell the project does, or what benefits it brings the world. This just adds one more to the tally.
It's not the project's fault that the submitter/editors linked to the release notes rather than the main page.
From the main page:
"KDevelop is a free, open source IDE (Integrated Development Environment) for Linux, Solaris, FreeBSD, Max OS X and other Unix flavors.
It is a feature-full, plugin extensible IDE for C/C++ and other programming languages.
It is based on KDevPlatform, and the KDE and Qt libraries and is under development since 1998."
So, your statement about "adding one more to the tally" of projects that do not "mention what the hell the project does" is incorrect.
Though, I would agree with the sentiment higher up, that editors really should be including a brief summary on many of these things, even though I knew what the project is, myself.
Users Rage Over Missing FireWire On New MacBooks
The reason I'm not thrilled about the idea of the refurb (or the last gen white macbook) has to do with perceived availability.
If I make the switch, I'm going to have a little investment (upgrades to Photoshop and Illustrator) to cross platforms. If I go with the last gen unit and something happens to it, it may then leave me in a position where the only available replacement (now that I'm committed) is to move to the current MBPro. The $700 price difference for something where I only care about the $5 part is hard to tolerate.
If the current MB had firewire, I'd at least feel comfortable with the idea that there would be replacement when/if needed. I know they are continuing the white MacBook, but consensus seems to be that it is only for a while to burn off inventory and so they could launch being able to say "starting at 999".
Google Chrome, the Google Browser
I know you're being snarky, but if you actually think about it, the address bar really *does* belong under the tab bar.
The address is a property of the current page. Placing it above the tabs puts it into the same space as the persistent elements like the file/edit menus. Those are application-wide. Below the tabs puts it into the same space as the page content, which makes sense as it isn't an application-wide property, but is directly related to the selected tab.
I'd never thought about it before, and can't say I'm bothered with the current setup (address above the tabs) but there is a sense to it.