vaughan

Thanks for the insight. Good to know I'm not alone.

It feels orders of magnitude easier to make the internal repo the source of truth when developing and a huge sacrifice to productivity to split something out.

If there was a good solution I think it could really help allowing more open source company sponsored projects to get out there in the wild.

Thanks, hadn't heard of this one.

Looks a bit heavy though for my liking but maybe they have some good ideas.

> Copybara requires you to choose one of the repositories to be the authoritative repository

Looks like it is more angled at mirroring private to public.

The goal is to allow development to happen on the OSS side. Unless you are a Google or Facebook with the ability to properly resource OSS, the 1st approach just leads to abandoned projects.

> this obviously takes more work managing the new external repo, cutting releases and the like, but is more valuable to the community at large.

I guess to gist of my question is how to keep the benefits of a monorepo while allowing a OSS development workflow.

It feels like OSS works best when there is a single Github repo that does not depend on a ton of other dependencies that change often.

> why does the package you want to split out need to remain part of the monorepo

It becomes more difficult to maintain and you lose the advantages of a monorepo (atomic commits/branching, etc.)

Submodules doesn't work well with branching, and publishing to package manager now means you need to symlink.

It becomes quite painful quickly if the open-sourced dependency changes a lot.

I've been minimalist running daily for 5+ years now. I've never been injured that prevented me from running. Only thing that stopped me once was sprained ankle from landing badly on rough track and the flu.

It took about 6 months to adjust my running style to front foot striking. The biggest change was the size of my calf muscles.

If I try to run in padded Nike's I get terrible knee pain.

There have been times when my achilles started burning and I also had some bad plantar fasciiitis, and some intense ball of foot pain too. However I kept running through it and it went away. Switching between front foot striking and mid foot striking helped me push through it. Funny thing is that I used to get bad RSI from using a mouse too. Now switching back and forth between laptop touch pad and mouse have completely resolved the issue. Same with standing/sitting at a desk. The ability to adjust my form to rest some muscles is a common cure for me.

Anecdotally I feel that barefoot had helped me avoid injuries I over the years.

There are so many more small muscles being activated without the cushioning that help you build stability and support. Most people never engage them because they run in padded shoes from a young age. When the padding wears down, which it always does, it places wierd forces on your weak leg muscles leading to injury.

The key is that it takes time to adapt...and sadly I don't think people want to commit to the period of adaptation, and they are quick to look for a scapegoat for any problems they face when trying a new approach.

I recommend Asana. It is simple when you get started, but can also grow with you as your project increases in complexity with numerous task organization options.

Useful features:

- Browse tasks with keyboard like a text file.

- Tasks can be in multiple projects.

- Tasks can have sub tasks.

- Big ecosystem - lots of integrations with other tools.

I use the following alongside it:

- Everhour for time tracking.

- Unito to sync my tasks to Github to track commits.

- Github issues.

- Instagantt for gantt charting the Asana tasks to see how reliable your time estimates were and plan ahead.

I use IntelliJ/WebStorm. I open a Google Drive folder which contains a markdown file for each day.

I have been waiting for this for a long time. :)

Should have got Harper Reed and the Obama campaign tech team to knock it up in Rails on AWS.

Great work guys. Would be excellent as a mobile app. If only there was some way to replicate the Tinder "match" aspect. Maybe constraining matches to a price range, brand choice, mutual friend likes or providing random discounts.

A pivot: how about you try the clothes on in a change room, take a photo and then people can say buy or don't buy. I'm sure its been done.

I was recently working on an iOS app where I needed a 1-to-1 chat feature. I was surprised that there wasn't an established market leader in this space considering how many apps use such a feature. When I saw this post I immediately thought "yep, that is a gap I'd seen in the market".

Some existing platforms included Scringo, Lobi SDK, QuickBlox. None seemed polished or customisable enough for my purposes. See more here: http://www.quora.com/Are-there-any-existing-APIs-for-impleme...

I ended up using an open-source iOS chat UI control (https://github.com/jessesquires/MessagesTableViewController) and Firebase (here is a sample project of a real-time iOS chat app: https://github.com/firebase/firechat-ios). It was incredibly easy to setup a real-time chat app and provides me with full UI customisation and a flexible and scalable data backend.

Send and receive code:

    // Setup.
    self.firebase = [[Firebase alloc] initWithUrl:kFirechatNS];

    // Listen for messages (real-time).
    [self.firebase observeEventType:FEventTypeChildAdded withBlock:^(FDataSnapshot *snapshot) {
        // Add the chat message to the array.
        [self.chat addObject:snapshot.value];
        // Reload the table view so the new message will show up.
        [self.tableView reloadData];
    }];

    // Send message.
    [[self.firebase childByAutoId] setValue:@{@"name" : self.name, @"text": aTextField.text}];

Thoughts on Layer

If Layer was around when I was looking I would have tried it out, however I am happy with Firebase as my backend now. The API looks insanely easy to use though.

Media sharing features would be difficult to implement using what I described above so Layer would be advantageous here.

Great branding.

Also Layer, please make your iOS framework available on CocoaPods.

There are some problems with preferential voting in the Senate though as Antony Green raises (http://www.abc.net.au/news/2013-08-29/green-senate-ballot-sy...).

95% of Australians will defer to their parties' chosen preferences, rather than stating their preferences explicitly. This is mostly because you have to number hundreds of boxes if you chose to vote "below the line".

Some argue that parties' preferences will not always reflect the intention of the voter - but they get away with it because its too difficult to vote preferentially.

I am working on it!

https://github.com/OpenParliamentAu/law-beta

All bills are in Microsoft Word.

1. Convert all bills to perfect Markdown for nice looking diffs.

2. Parse amendments (e.g. "Section 1: Omit paragraph 1, replace X with Y".) for bills currently before parliament and create consolidated versions of the bills to view changes in context.

3. Fork GitLab.org and create a pretty interface for law makers to use.

Exactly what I do. I've just started using IntelliJ change sets which are really useful.

Just discovered GoodFilms! Brilliant idea - I will be back often. I've felt a similar frustration with jsFiddle not supporting Coffee+friends so kudos for that one too.

Here, here. I'm from Australia where medical care is also free. This idea of dying quickly as to not burden your family with medical expenses is ridiculous, given the success that single-payer health care has had in many countries all over the world.

I understand that some conditions cause insufferable pain with very slim chances of surviving, but there are many success stories from people who have battled through. Its often these same people who provide the courage to others to battle on and raise money to support the families of those who have had similar experiences. We shouldn't be thinking about optimising our lives for our own happiness, but for the generations yet to come.

I will always fight for my life to the bitter end. There is no way I would leave my children to come to grips with why their father gave up without a long, hard fight.

MacBook Pro 13" 2009 C2D 2.66 4GB

Dell 24"

Microsoft IntelliMouse Explorer 3.0

Thunderbolt 3D accelerator will be out early next year. ViDock G4 Micro (http://www.facebook.com/VillageViDock?sk=app_202980683107053...)

I'm the same as aparadja. Using the built-in keyboard is great because the trackpad is in the ideal position below the keyboard which I use all the time for gestures and scrolling. I have a mouse next to the computer which I use sometimes.

Try the Plugable UGA-2K-A (http://www.amazon.com/Plugable-Multiple-2048x1152-1920x1200-...) to add another 24" monitor.

Or you can wait for the ViDock G4 Micro (http://www.facebook.com/VillageViDock?sk=app_202980683107053...) which allows you to use an external graphics card with 2 displays - full GPU acceleration.

I'm trying to make the exact same decision.

I used to use a 3x24" monitor setup with Windows, now I am using a 2009 MBP 13" C2D in front of me with a single 24" monitor. The problem with this setup is the 2009 MBP is unbearably slow - it lags when closing tabs in Chrome and I do miss having a 2nd 24" monitor. I use IntelliJ for dev. I have full-screen IDE, half-screen browser, half-screen terminal and then I like to have a browser open for documentation/textmate/etc.

1. Seems bad to get MBP when their will be a big refresh 2012 - with MBA 15". If the 15" MBA was available today I would buy it. Macs have good trade-in so it might be worth getting an interim solution - I'm actually considering a low-end 27" iMac so that I can buy 15" MBA next year and use the iMac as server/external display.

2. ViDock is bringing out a Thunderbolt external PCIe solution so you'll be able to drive 2+ monitors from all Thunderbolt Macs. This should be out early January/Feb. From tests you get 90-95% performance of GPU compared with desktop card! Pretty cool. No need to buy the MBP 15" for dual monitor capabilities. http://www.facebook.com/VillageViDock?sk=app_202980683107053...

3. Antiglare high-res on 15". For coding I love having plenty of space, which makes the 15" seem better choice.

I still have no idea what to choose - please let me know what you go with.

I've ordered the Plugable UGA-2K-A which can drive an external 24" so I'm going to wait to see how effective that is with my current setup.

How do you connect two monitors to your MBA?

I would expect they mean special people with well-known stage names like Madonna, Sting etc. similar to how Quora enforces it. But I guess if Larry is making the rules he gets to decide if he is special enough :)

I disagree - he makes a reasonable assumption. G+ allows you to share things that are public and share things that are private.

If someone was sharing things that are private (our assumption), wouldn't it follow that they are sharing things that they have indicated (via some other means) are public?

For example, David Drummond's post on the Google Blog regarding Android patents (http://googleblog.blogspot.com/2011/08/when-patents-attack-a...). He has authored this post, indicated this is public but failed to share it publicly using G+. Is this not the purpose of G+?

These execs attend press events often where they openly voice their opinion in the public domain. It's a public company too and these people are actually accountable to the public.

However, it seems that although they share publicly when asked to by reporters and their open-ended questions they do not see G+ as a means to publicly share. They do not understand the value of information sharing and user generated content, the cornerstone of web 2.0. They are still stuck in a pull-based world driven by journalists asking questions. Facebook and Twitter understood the value of this change well by living through it (http://vaughan.io/post/10476571077/live-the-problem).

What we can draw from this is that its not going to be Google who jumps on the next big trend in social, if they can't even understand how to use their current product to its intended effect. They only built G+ because the concept was proven by Facebook and now they are just replicating it. Facebook will continue to lead the market here until the top executives like Larry, Sergey, Alan Eustace, etc. can understand their own product, its weaknesses and its strengths.

David Drummond has blogged publicly on the Google Blog (http://googleblog.blogspot.com/2011/08/when-patents-attack-a...) a few times. Surely it would make sense for him to publish this on his public G+ feed.

Google+ has made a point to enforce a real names policy - no pseudonyms allowed. Surely high level executives have things they would like to say publicly or comment on posts which they see. Reading articles is one thing, but taking the time to form a cohesive argument or opinion required to make comment on public articles can greatly enhance comprehension of a topic. Responding to criticism is also a part of this.

Are we to believe that people rise the ranks to a position of power where they suddenly need not debate issues in the public sphere and take the criticism that goes along with it?

Surely not. So wouldn't it then make sense to at least allow pseudonyms?

Strange...Alan Eustace has made 3 public posts on October 5, 2011. Perhaps he's a HN reader.

I would say Google+ is a core product for Google now. The OP submits this article to back this claim up: http://www.oregonlive.com/business/index.ssf/2011/06/googles...

Eric Schmidt admits he "screwed up" by not seeing the importance of social and the threat of Facebook. If Eric Schmidt really lived the problem (http://vaughan.io/post/10476571077/live-the-problem) he would have been actively using Facebook and Twitter too and would have reacted faster.

This is even more of a reason that Google execs should use Google+ publicly. They would then understand this problem exists for this type of user and push for solutions. Perhaps some sort of priority inbox feature for Google+?

Zuckerberg would have come across this problem and would have prioritized it. Features like the Social Inbox and the constant revisions of the feed might be examples of this.

Google+ explicitly doesn't allow the use of pseudonyms.