tgandrews
Joined 16 years ago
Joined 16 years ago
> linuxvoice.com Server: 8.8.8.8 Address: 8.8.8.8#53
Non-authoritative answer: Name: linuxvoice.com Address: 104.28.6.18 Name: linuxvoice.com Address: 104.28.7.18 > www.linuxvoice.com Server: 8.8.8.8 Address: 8.8.8.8#53
Non-authoritative answer: * Can't find www.linuxvoice.com: No answer
* Startups for the rest of us
* Bootstrapped with kids
* Freakonomics
Chrome definitely doesn't have any level of domination over the enterprise market like IE6 on Windows did. That was the problem with IE6 not the browser per se - it was revolutionary when it was released, MS just killed the team. The chance that enterprises will stick with Chrome is very unlikely.
As it stands at the moment, the only downside is the duplicated development between the Safari and Chrome teams. Webkit will suffer, but the web won't. Apple don't care enough, the web isn't the top of their priority list.
If anything, the iOS monopoly of mobile web traffic (in the first world) is a problem which certainly isn't changed by this fork.
That's my two pennies worth.
I don't understand why Ice implies webkit, it could be presto like Opera Mini/Mobile (rendered on server).
With a non-relational DB the idea is to attack it with map reduce and possibly in app calculations. This may not be ideal, but the benefits of easy placement and access of the documents outweigh the aggregation problems on most of the problems I have dealt with.
Neither solution is perfect you just need to make a prediction based on the projects requirements and make a choice.