If you have multiple Slacks, it's not. You can cycle through all your connected Slacks with the app.

See this 2012 thread https://github.com/torvalds/linux/pull/17#issuecomment-56546...

I'm a bit disappointed there are no tests. I've always wondered how Google handles testing on internal Android projects (especially since it's a bit of a sore spot for Android [1]). It would've been great to see a "real world", official example.

[1] https://github.com/JakeWharton/gradle-android-test-plugin#de...

I really like how Gradle has solved this problem. You check in the Gradle wrapper (http://www.gradle.org/docs/current/userguide/gradle_wrapper....) into your source control (it's only 56K), and it automatically fetches Gradle for you if you don't have it. Updating the project's Gradle version is just a matter of changing one or two lines.

It's cool to think that the only requirement for anybody to jump into a Gradle project is to have the JDK installed. "git clone <project>", "./gradlew assemble" is all it takes for you to fetch all your dependencies and build the project.

I think it'd be interesting to see if Vagrant could incorporate something like this; it sounds like it would help your use case.

> It's cool to think that the only requirement for anybody to jump into a Gradle project is to have the JDK installed.

Sounds like a commercial. Many people have good things to say about Gradle's functionality, but too bad about the programming language I have to use with it, i.e. Groovy, at an old 1.x version, with a bloated grammar spec using an old 2.x version of Antlr, i.e. http://svn.codehaus.org/groovy/trunk/groovy/groovy-core/src/...

Too bad I can't use a language with a simplified easy-to-remember grammar, like Scala, to program Gradle.

The latest Gradle release notes http://www.gradle.org/docs/current/release-notes always mention both Groovy and Scala when describing how to build projects, but all the build script example code is in that Groovy language. Will Gradle ever expose an API so developers can choose to use the same language for the build scripts as they do for the projects they're building? Perhaps even ship Gradle with different build language options?

You could always set the script to only run the tests on certain branches on pre-commit. (i.e. if branch name is not master, exit 0)

If you haven't already, it might be a good idea to vote for that feature: http://youtrack.jetbrains.com/issue/VIM-448 and http://youtrack.jetbrains.com/issue/VIM-518

Which would you recommend to read first?

The little Schemer

Don't worry if the last few parts don't make too much sense.. I went back and forth between the two quite a lot

Personally, SICP. I found that the format of LS got old fast.

Not to mention the patronizing "Now go make yourself a baba ghanoush pita!" and "This space reserved for jelly stains."

Maybe the humor was just lost on me...

Unsubscribe from the default subreddits and you'll find more intelligent discourse.

I think having Google retail stores would've been great and given them some exposure and credibility with people less familiar with phones. That said, I would have also found it unusual given their push to sell things in the Play Store and the fact that they don't have that much hardware to sell.

I think it would make more sense to work out deals with existing retail stores to have small 'Google' sections much like happens with other brands. They could use that as a chearper/quickly/lower investment way start learning whether or not a real store would be viable.