cjantz

4 ms·

1.
FBI is asking Congress to weaken iPhone and Android security(theverge.com)
1 points by cjantz 12y ago|0 comments
2.
by cjantz 12y ago
I wonder how the new iMac 5k Retina is going to influence sales for their iMac line numbers. They increased but I don't think it's just because of this release?
3.
by cjantz 12y ago
It's the soft double tap gesture apple introduced because of the huge screen. This way you can use navigation panel elements without moving your hand that much and it's less likely that you drop your phone.
4.
Hybrid Mobile Apps: Providing a Native Experience with Web-Tech(smashingmagazine.com)
1 points by cjantz 12y ago|0 comments
5.
by cjantz 12y ago
Exactly! But why do you need to squash while merging? The concept of merge tells that a branch is merged into the history by adding a merge commit. This commit reflects all differences. It's done automatically if possible - you need to
6.
by cjantz 12y ago
You shouldn't push dysfunctional branches anyways to keep the application working and always testable. We have a CI server testing every branch for every push - I'd regard it as rather bad to have failing builds 20 times a day. Wo
7.
by cjantz 12y ago
If you take it like that you can also say ignore the squash and keep the merge commit clean. That way you don't push all your development commits to the remote and ensure a clean streamlined history. A problem some teams I worked with
8.
by cjantz 12y ago
I think Apple needs to check on this very careful just because of some services like Uber offer services through the app and don't sell a physical good. The opposite of this is, that you can't use Apples tier-pricing for services
9.
by cjantz 12y ago
How and when to comment should be a decision made by the contributors working on the feature, but squashing is something I always disallow for any team I work with just to keep the history and be able to follow the programmer when chasing d
10.
Our First Four Months Building Underdog.io(medium.com)
2 points by cjantz 12y ago|0 comments