While I agree with the core of your comment - a disagreement isn't really news - your comment is two adhoms and a contentless snark, so I downvoted it.
1. Who shared or commented on an item. The search above I knew I had liked the picture, so I constrained the search to only things I’ve liked.
But I didn't know Robert Scoble liked the picture, so it wouldn't help me find it.
2. How many comments or likes are on an item.
Good if you happen to remember it, but also something Twitter could add - search filtering on how many @replies/retweets something got.
3. What was said in the item.
You can't comment on a tweet, but you can @reply/retweet or just tweet again moments later with your comment. It's not the same as friendfeed but it's not dramatically far away. I'm not convinced it's such a big difference that twitter can't overcome it with search improvements.
By chance, I was looking at Mac Minis in the UK online Store this morning (GMT), and the price of the lesser-spec'ed unit was £391. Now the price of the new lesser-spec'ed unit is £499.
It's a good thing the economist runs its purchasing power against burgers and not Apple hardware! Although that would be interesting for its own reasons.
You're getting screwed by the GBP exchange rate plunge. (some might say: correction, and having lived in the UK during times of the €1.50 pound, I'd tend to agree) Euro prices have stayed the same. And yes, ordering Apple gear via the UK store or UK Amazon was a bargain for mainland Europeans for a while because Apple only seems to adjust for fluctuations when they update products. Shows you what kind of mark-up they're using to be able to afford to do that. On the plus side, you'll be able to get cheap Apple gear from the continent if the pound picks back up.
Without wishing to belabour the point, the prices for the same unit (the lesser-spec'ed Mac Mini) also seem to have gone up in the Irish and German stores (to pick but two), from €499 to €599.
I just checked amazon.de and you're absolutely right, sorry. For some reason I thought the old minis were €599, too. 166MHz and 40GB more, the nvidia chip, and losing the remote are worth €100? Hmm.
Nevertheless, around 50% of the GBP 392->599 increase is down to correcting for the new exchange rate. Not that that helps you at all.
Basically any note played on an analog instrument has a set of overtones of various frequencies. If these tones were played a bit louder, you would hear a chord rather than a single note.
good programmers are forced to program simply so that future generations of bad programmers can read their code.
Is this necessarily a bad thing? I generally try follow the "code such that nearly anyone can understand" mantra. Helps keep things simple and concise.
I actually don't like forced readability like the python whitespace as I think it stifles creativity, and the only way it makes code better to read is by forced formatting (the forced white space) while your code can still have hard to read logical loops, blocks, variables.
In a way, it stiffles creativity just for a small gain of formating/readibility.
Plus, with modern IDEs it is very simple to format the code the way you want. In eclipse you have RightClick -> Source -> Format then viola, your code looks the way you want.
Having worked with both python and java, I have enountered more hard to read code in python than in java, (maybe this is due to the superior tools/IDEs in java).
As for ada, i thought it was a great language to start learning programming. Exceptions are verbose, and it is an easy language to pick up, as it looks a lot like Pascal.
I learned it my freshman year, but I never used it in a production capacity and I wouldn't consider doing anything serious with it right now.
'and the only way it makes code better to read is by forced formatting (the forced white space)'
Indentation is required when writing in any language as a matter of courtesy. Python just doesn't ask you to delimit your blocks of code a second time by unnecessarily requiring brackets.
I'd argue that there is nothing crippling about it. You can define functions anywhere, if you need a multi-line lambda just define a function and be done with it. Multi-line lambdas are messy... this constraint keeps your code sane.
You can nitpick all you want, but the fact is I can start reading just about anyone's python code and feel like it's my own because styles are consistent across the board. A lot of this has to do with the tight community, but the fact that it's all reinforced through syntax constraints is a huge plus.
This is cool and all, but what's the utility? You can already isolate individual windows and arbitrary screen regions with the built-in OS X screenshot grabber.
You have a webpage open in firefox, safari, IE (via parallels). You grab all three in one go and reposition them on top of each other to get pixel accurate offsets?
Agreed. While I can see that it's a clever thing and nicely done, I can't think of anyone who routinely needs to screenshot all (or at least multiple) windows at once but separately.
Someone who saves a ton of time using this, please tell us what you're using it for!
As someone who does a lot of UI mockups, something like this would be extremely handy. As someone else pointed out, if this saved me an hour of my life, it would pay for itself. If it saved me two hours, it would be saving me money. And an hour of set-up time occupied by taking and assembling selected separate shots of various tool palettes, settings windows, and main editor screens, for instance, would not be out of the question.
It's the "one fell swoop" aspect that is appealing. Just being able to open every possible window in an app and then hit "capture this to Photoshop" when starting on a UI clean-up pass mockup, or for creating a master document of all windows when taking a desktop app from 1st pass programmer art to shipping resources, and sorting them into Photoshop layers and folders, would skip a lot of currently requisite document setup/prep time.
The suggestion to use this to more quickly build manuals and tutorials is also spot on. Grabbing the current state of all windows in an app at "step 3" of a tutorial, and then being able to nudge them around to best facilitate the required tutorial/manual text, without having to manually capture all elements separately, is pretty sweet.
I just sent it to someone who publishes Photoshop tutorials for a magazine--lots of shots involve multiple windows and the layout people love to be able to play around with that sort of stuff.
