Hi! So, at every step -- from conception to funding to building the team and now building the product -- we have done so to build a big, successful public company. Not only do we (the founders) share that conviction, but it is shared by our investors and employees as well. For better or for ill, we are -- as we memorably declared to one investor -- ride or die.

Also, if it's of any solace, I really don't think any of the existing players would be terribly interested in buying a company that has so thoroughly and unequivocally rejected so many of their accrued decisions! ;) I'm pretty sure their due diligence would reveal that we have taken a first principles approach here that is anathema to the iterative one they have taken for decades -- and indeed, these companies have shown time and time again that they don't want to risk their existing product lines to a fresh approach, no matter how badly customers want it.

Well the worst part was, their own Human Interface Guidelines even say:

“These options are usually visible, but can be hidden as a group, such as......, or individually disabled, such as when a full-screen app can't be minimized. ...... A title bar should be visible, but can be hidden in an immersive app like a game.”

Either way, this wouldn’t be in the top 1000 reasons for someone to request a refund for a game on the store so why is Apple even concerning itself?

In the cases of Brave and Moana at Pixar and Disney Animation respectively, the story definitely came before the tech was developed. I was an intern at Pixar during the production of Brave, and I worked on Moana, and I can say that in both cases, there was a mad scramble to develop the tech to catch up with the story. We didn't really have the water on Moana working completely correctly until like 6 months before the movie came out.

One question I like to ask is "Tell me about the worst day (work-wise) you've had in the last six months." Most of the answers I've had gotten generally have to do with escalations and I find that answers are quite honest and unpracticed. I think the way a team/company handles an unusual high-stress situation is in many ways telling of the team/company dynamic in general. And as a bonus, there's usually a good anecdote about a buried body or two in their codebase, process, you name it.

An argument I heard recently against this is, if abolished, politicians won't have incentives to campaign in rural territories, and they won't be accountable to rural territories. That basically makes sense. The EC is the only thing that really gives rural territories any stake, as the majority population has shifted to larger urban centers.

People who want to get away from the big cities and live a different kind of life with different priorities (and different legislative interests), shouldn't be totally shut out, should they? Even though I live in a giant urban area, I wouldn't want to feel pressured to due so due to lack of political stake if I move elsewhere.

It's very sad to see bitbucket dropping mercurial support. Now only Facebook and volunteers are keeping mercurial alive. Sometimes technically better architecture and user interface lose to a non user friendly hard solutions due to inertia of mass adoption.

So a lesson in Software development is similar to betamax and VHS, so marketing is still a winner over technically superior architecture and ease of use. GitHub successfully marketed git, so git and GitHub are synonymous for most developers. Now majority of open source projects are reliant on a single proprietary solution Github by Microsoft, for managing code and project. Can understand the difficulty of bitbucket, when Python language itself moved out of mercurial due to the same inertia.

Hopefully gitlab can come out with mercurial support to migrate projects using it from bitbucket.

For people who believe in self hosted solution can install Kallithea (https://kallithea-scm.org) or Rhodecode open source edition. Kallithea is used by Unity engine to manage their source code internally with mercurial.

I suppose it's because reposting is not considered an issue if some time has passed since the last submission