Currently I am using the local calendar adapter for Google calendar, from F-droid. Works well. There is a similar CalDAV adapter too - doesn't it work nicely with owncloud? I was hoping to use it some day.
The issue I'be had with it is that it doesn't really do merging, it does 'server always wins'. This means that if you delete an event locally, on the next sync it will reappear. It's fine for new events created on the device and for events created elsewhere if you just want to view them on the device. I use owncloud on the server and iCal on my laptop and editing things on either of those is fine.
Anyway, that was my point. Google and the other big 4, really do good UI - much as I hate to expose my data for their inspection.
The reason I stopped using the search engine was that they made a UI that pissed me off enough to make me quit. I've not found Google UIs to be particularly well designed in general - I could file a few hundred UI bug reports on the general Android system, including a lot that are regressions.
While I personally see a device like this (sorry... ROBOT!) of rather limited use for testing prepared dishes, I can see great utility for it for testing ingredients. You could have a standardized, unambiguous way to rate the quality or at least properties of a given product, be it meat, fruit, vegetables, etc. I bet cultivar breeding programs in particular could really benefit from this - "Well, I was hoping that this new mango would be a huge innovation, but actually it's almost identical to a Keitt. Though to be fair its mouthfeel is somewhat like a Carrie, and it does have a small amount of a new novel aromatic compound..." Just a single mass produced sensor package that measures a wide range of different properties at once in a repeatable, universal manner. If such a thing could become widespread, I'd bet half of the "cultivars" out there would pretty much disappear, having been shown to be essentially identical to others.
One use case that's often touted for this kind of thing is having appliances that can work on spot pricing for electricity. Over the course of the day, you get spikes from solar and wind (and tidal and so on) production when electricity is cheap. You get periods when power plants need to reduce capacity for maintenance when it is expensive. There are massive power storage facilities that profit from this: there is one near where I used to live that pumps water up a hill into a reservoir when electricity is cheap and then lets it flow down again and generate power when it's expensive. Now imagine if your fridge or freezer could get this information in real time and could run the compressor a bit more when electricity is very cheap, then use the cooled coolant to keep your food cold when the price goes up.
Almost 50% of the electricity generated in the USA is wasted because the supply can't adapt to demand fast enough. There are some very big savings to be made by having demand adapt to supply.
It's not abusing anything Google apps work better and use less resources than the competitors which is 1 reason why they are doing this.
Really? About the only Google app that I haven't replaced with something better (and open source, so money / distribution rights are not an issue) is Google Play, and that's only because my bank and a few other companies only make their app available via Google Play.
Oh it parses it just fine. It was just a dumb idea to parse it in the first place.
Re-read the latest CVEs. There are bugs in the parsers that can be exploited, so even if you're never invoking the functions they're already run through the parser and the parser is breaking things for you.
The EPA guidelines are in line with the level of risk: very, very little. If you want to cut your mercury exposure, don't stop using CFLs, stop eating seafood.
As for the Bridges case, you should read the Maine EPA's account. CFLs were new back then, and they had decided to use her case to learn more about what sort of advice they should give for dealing with broken bulbs. So they sent someone with a meter because they wanted to learn more, not because that's standard practice. The carpet was already intended for removal as part of a rennovation. They took readings all over the room. The only place with "high" levels was right where the bulb broke - not in the ambient air, not anywhere else on the carpet, not on the toys, not even under the carpet where it broke. I say "high" because even the levels right where it broke weren't actually high, just over Maine's long-term exposure guidelines (which is obviously not applicable to a temporary event). Moving the meter even six to eight inches away rom the breakage point dropped the levels way down. She was told that the bulb breakage was "of negligible health concern". However "the homeowner expressed particular nervousness about exposures to mercury even in low numbers", so they told her what she could do if it bothered her, one of which was calling a cleanup contractor. And of course any private cleanup contractor will charge you an utter fortune. The Maine EPA came back two days later after the story hit the news, before anything had been done in the house. The area where the bulb broke had dropped down below Maine's limit.
The case was ridiculously blown out of proportion.
My whole family got really fed up very quickly after walking into a dark room, hitting the switch and having to stand there for 5 seconds until the light actually came on
I find this really hard to believe. I've been using CFLs exclusively for over 10 years - mostly buying cheap ones - and I've never seen one that takes more than about half a second to come on. The time taken to get to full brightness I can almost agree with (this was actually why I started using them originally - having a bedside light that took a couple of minutes to get to full brightness was nice) but in recent ones (i.e. ones from the last 4-5 years) the warm-up period has been 5-10 seconds, although growing to about 20 seconds after 3-4 years of use.
If it's not an abacus, it can't count. Most of the rational people have quit fet due to database failures, update disasters, an incredibly primitive unthreaded discussion format and a contingent of highly abusive individuals. Abusiveness and primitiveness has done for tech forums, too, which is why Kuro5hin has been in death throes for some time.
A community is never stronger than the people who stand behind it and, in sadly far too many cases, the people standing behind the community are crouched down and in hiding.