jennings223

The flying Octocat is pretty slick.

I like the idea of collecting news for individual Github repos. At least it's something I don't see on other Hacker News readers.

Yeah. I'm aware that Apple has made some great contributions in Open Source. However, that doesn't change the fact that they live on proprietary technologies and investing in OSS is just a strategic business action.

This article here explains this: http://sealedabstract.com/rants/beyond-open-source/

Or maybe Apple.

If you have to set options or even program to get it started, it's definitely not so smart.

Is this the post you are looking for?

https://news.ycombinator.com/item?id=7838772

Or are you looking for the Strip api doc?

https://stripe.com/docs/api

Or just some goodlooking docs?

https://github.com/PharkMillups/beautiful-docs

I got the exact feeling as yours at first. :)

My understanding of your concern of rebase is that if they are gonna change that (or get rid of that), it will be a change of the workflow instead of just a simplification of it.

I used to rely on merge other than rebase when my local tree is diverted. That usually ended up with two commits (one for my local changes, one for the merge). But later I learned to use rebase. It would only result in one commit, which I feel is kinda nice coz you have a cleaner and more correct(time-wise) commit history. I don't know if this is the fundamental purpose of rebase. Advice welcome.

Thank you so much. I think they should definitely put something like your explanation in their documentation to show the difference in a more expressive way.

As a novice git user, I can't really tell how Gitless is really different from Git in daily use cases. Any explanations?

At first I assumed they have a large collection of templates for shops just like web templates with different styles. But I was wrong. All their shops look alike, with a minimal style. It's a total mystery why they have so many lines of css for such a simple design.

I seriously wonder if it could achieve the rendering quality/usefulness as it advertised. The combination of portability/3d performance/battery life/comfortability usually doesn't produce good results. Google didn't solve this. What should I expect from Microsoft?