I don't think anyone was arguing that adopted children are any less meaningful than biological children, but if a 60 year old business owner adopts a 40 year old manager who works at his company that's really not the same thing.
It is the same family, though it would be more amazing if they adopted and raised younger kids kids without consideration for whether they would inherit the business or not, and still manage to keep the business in the family for 1300 years.
But the act of passing the business down to non-blood related adults for 1300 years without going belly up is amazing.
So if you adopt a child and raise it as your own and that child takes over your business, is it still a "family business? Yes.
But can you say it's still a "family" business if it's gone through the Japanese custom of adult adoption? Arguably yes, because that person was brought into their family as a legitimate heir.
On the other hand you could argue that it's no different than a family business being sold in the western sense, it's just that in ancient Japan you couldn't really buy and sell businesses, they were owned by clans, so this was their mechanism for ensuring business continuity when there was no suitable male heir.
I'm not taking a stance on whether it's still a "real" family business, but it's important to understand that what the Japanese mean by "adoption" in this sense is not at all what westerners mean when they use that word.
My adopted Children when Adopted (10, 20, 22) They were in my house at 7, 11, 15 from the same mother. LONG story but I ended up adopted the two older ones when they were ready which wasn't till they were adults.
Nobody is arguing that adoption per se isn't the same as "the same family". The practice being described here is that the adoption is specifically adopting someone _because_ they're going to be the next owner of the business. I'm sure you can see that there's a salient difference between your case of adopting to build a family vs the case here of a 65 year old guy adopting his 50-year old successor as part of a tradition of that business.
I keep my free Dropbox account, but I won't pay them any money while they have Rice on board. (I was a paid member of Loom, which they acquired. As a result of the acquisition I was to become a paid member of Dropbox's photo syncing service. Instead I demanded and got my money back.)
NYC: Front End (JS/CSS/HTML) and/or Python Engineers. Also, Test Engineers.
Axial enables small-to-medium-size companies to connect with advisors and sources of capital at a scale not possible in the offline world. We use Python, PostgreSQL, Backbone, and Angular.js. We have automated tests for many things.
We're located in the Flatiron district near Union Square. Well funded and growing fast.
For me it was when I ran out of savings, sold all my stocks, ran out of that money, and still didn't have a shipped product. My cofounders are still going at it, and I wish them all the best, but we spent the critical months of our startup designing and redesigning a thing without ever getting user feedback.
For all the other folks out there at Google or other largish companies, who are considering quitting and forming a startup: Don't do it until you have at least once seen a project through from conception to launch.
I recently joined a NYC company with "unlimited vacation days", and they do actually mean it. I mentioned this very trend when I was interviewing. They responded by saying they expect me to take AT LEAST three weeks of vacation a year.
Now, some of my coworkers are workaholics and won't take that much. But I have had success in just saying "I want to take these weeks off."
All you have to do is use sys.stdin.buffer and sys.stdout.buffer; the caveat is that if sys.stdin has been replaced with a StringIO instance, this won't work. But in Armin's simple cat example, we can trivially make sure that won't happen.
I'd be a lot more willing to listen to this argument if it didn't overlook basic stuff like this.
I like Python 3's unicode handling but I agree that this seems strange. It is because people expect to see "characters" from these interfaces after treating them as ASCII-only for so long. If Python 3 had insisted on real purity with bytes objects I think it would have died a long time ago. Which is sad.
> I'd be a lot more willing to listen to this argument if it didn't overlook basic stuff like this.
Just because there's a way around this particular issue doesn't mean that the attitude of Unicode by default of Python 3 isn't problematic. There's also sys.argv, os.listdir, and other filename stuff which Python 3 attempts to decode.
And if computer science were a field in which men have historically been underrepresented, with company after company having culture issues about "femprogramming culture", your Turing Initiative might have a reason to actually exist.
Well, this is awfully disappointing. I'm in the process of migrating my stuff off of Dropbox due to the Dr. Rice issue (only problem is a lot of apps use it as their sole syncing service); I have no desire to move gigabytes of photos into Dropbox's control.