Recently I've been trying to make something like the refreshing Jasmine Lime Cooler by brewing a big pot of jasmine tea, steeping for an hour or two and keeping that in the fridge to add a splash of lime cordial to (Bottle Green rather than Roses, as it has a lot more lime and a lot less sugar). I'm not sure if it needs fresh lime or a bigger slug of cordial to approximate US limeade - or margarita mix ;-) - as it's not quite as tangy and limy as Peet's.
Usually I wouldn't brew jasmine more than a couple of minutes; for drinking hot, long brewing brings out far too much tannin that overwhelms the jasmine. For drinking cold I think it needs the longer brewing to get strong enough to retain flavour in a cold drink; I often brew a second pot with the leaves after I've put the first pot in a jug and it's too light in flavour to stand up to the lime as much, but very refreshing.
Obligatory nugget of incorrect common knowledge ;-) Brits should be called lemonies rather than limeys as Cook used lemons to avoid scurvy in his crew; limes don't have enough vitamin C to help.
Office 365 is compelling in several ways and it wins hands down in one specific situation; where you're not putting everything into the cloud and you already have Microsoft IT in your business. I've also been thinking about the implications of this hybrid approach.
Lead on cloud - or the business will work around you: my view on why Microsoft's view of the cloud is one of the more pragmatic approaches, written to accompany my interview with Kenon Owens about System Center 2012 where we decide "IT departments can't ignore the cloud. If they fail to deliver systems that are fast and easy to set up, business teams will just sidestep them and sign up for a cloud service — whatever the consequences for security or compliance".
Talking to Microsoft execs about that view of cloud, I got a nugget about the way Microsoft runs the business that I hadn't known before. Microsoft execs: paid by results
Microsoft has gone back and forth between treating SPs as feature packs.
With Windows XP, service packs were significant upgrades; XP SP1 added tablet PC functionality, SP2 was practically a new version of Windows.which was fairly major; XP3 had .NET features brought in from Vista as well as various security features (admittedly for business in most cases) rather than simply rollups and hotfixes.
Even Vista SP1 was a major update, improving power management, network speed, search speed and adding hardware support like Blu-ray burning to bring it up to the same performance as XP SP2 (according to Microsoft - it arrived just as Windows 7 was in beta so it never had a chance: I installed it on the way to the airport the day it came out, tested it and went right back to the beta of 7).
But although it included significant updates for business users using remote connections to a work server, for most people Windows 7 Service Pack 1 was little more than a rollup of updates and hotfixes (although it actually adds significant features for businesses using certain kinds of virtualisation from Windows Server). That's what Microsoft has been aiming at for years; service packs that don't add new features and that you already have if you've been accepting automatic updates.
The general popularity of Windows 7 makes that easier to achieve. So what does that mean for Windows 7 SP2 and when will we see it?