Keep an eye on Providence. As Boston gets hotter and hotter (read more expensive), there's likely to be spillover to Providence. Providence is a truly cool little city in the BOS metro, and costing a small fraction of the few equally cool places in BOS proper.
no amount of rose colors can change the fact that it is an enterprise product, a delight of middle managers who measure progress by the total percentage of hours logged so far on all the SCRUM tasks across the department.
If I was very very rich and I really hated other people, I'd start a company making miserably slow, unintuitive project management software. Say what you will about the Aussies, their software is slightly less awful.
Yes, but what is the implied life expectancy? I'd guess pretty low.
Also note that policies like this require ongoing maintenance payments, otherwise you forfeit past payments and benefits.
The problem with claiming that the life insurance market is a predictor for death statistics is that firms tend to keep the most important data and calculations used to derive their pricing schemes secret. The firm is only concerned with keeping to projections as far out as they can model.
The consumer has no real input into the model (except as a selector of alternatives) and therefore cannot obtain much knowledge about actual death statistics (except perhaps a near meaningless lower-bound).
It's very generous to give the current life expectancy stats about a 50% chance of being valid by the time you reach the age to die. If the historical growth rate in life expectancy continues -- or at minimum doesn't go to zero -- there's a 0% chance. Moreover as we witness regularly on HN there are many reasons to believe that the growth rate in longevity will accelerate.
It's surprising to see this announcement in the wake of the Alphabet restructuring. Because of privacy concerns, I suspect they'd sell many more of these under the Nest brand, than they will under the Google brand.
Providence, RI puts you on I-95/Amtrak/Acela/MBTA an hour from Boston and 2.5 hours from New York. While not cheap, it's much cheaper than either of those cities. The art, music and food scenes are awesome. There are a lot of innovators and entrepreneurs.
We've had to use asana for a particular customer project recently and it's really not that great. For me trello is a far better implementation of task management.
i dont think so. i have used asana for my team and couldnt make it stick. we used trello which was better but isn't perfect either. it just seems to me that I shouldn't have to learn another software just to organize my to-do list.
The value of such of tool though points to one of the reasons why web technologies will ultimately prevail over native for most applications -- ease of use.
I hope to see the day that given the right development attention one can make a web app that feels fast like a native app. It might already be possible for some kinds of apps.
There are apps popping up that are really an ember or angular one pager wrapped in a native shell.
HTML/CSS on Webkit gives you an amazing layout engine for free. Building UI for native apps feels like "web coding like it's 1999" with a lot of absolute positioning and use of sprited images. I wonder if things improved in iOS7.
That's an iOS issue, not one inherent with native apps. Android/Qt/Windows Phone/literally any other toolkit provide flexible layouts which are much more powerful and often easier to use than CSS. And if you need a custom layout, you can actually write a new layout manager which is just as fast or faster than the built in ones, no javascript to set absolute positions on everything.
> why web technologies will ultimately prevail over native for most applications
All your users care about is UX and features. Native sdks provide more features than web apis, are more powerfull and your users feel the difference. Native sdks are not going away anytime soon.
While I don't think that native SDKs are going away any time soon, there are huge classes of applications where those additional features aren't needed, and even more that can us in between solutions like phonegap. I think that very few applications outside of games really need features that a web-based UI can't provide on modern mobile devices.
Didn't Facebook famously switch from HTML5 to Native for their iOS app? If a company with the resources of Facebook can't do it effectively, I think you underestimate the problem or overestimate web-tech capabilities.
