Bazel – Correct, reproducible, fast builds for everyone • Hacker News Board

Re: Bazel – Correct, reproducible, fast builds for everyone

#181

Post by nevir » Wed, Mar 25, 2015, 5:56 PM UTC

hueving wrote: post #156

beagle3 wrote: post #126

Earlier quoted context omitted.

Can you give a (very quick) pointer/explanation to what about Thrift didn't cut it for you?

It wasn't invented in Google and is therefore inferior. Google has a massive incentive to develop projects specific to their requirements and then open source and evangelize them to stomp out approaches not optimized for them.

Don't forget that there is a constant inflow of developers to Google. They all bring the tools and practices that they know, and will definitely leverage what they can.

It's not like we're run through a brainwashing machine when walking through the door :P

There just happen to be a lot of challenges to make things run on Google's infrastructure - and not all the tools we know and love happen to work well on it. Some of that is legacy, some of that doesn't have many parallels externally.

So, we write solutions that work well on Google's infrastructure. Some of that gets open sourced, in the hopes that it's also useful to the greater community.

But I definitely would not consider Google-written code to be superior to other solutions out there - just an alternative option to choose from - and certainly not the best for many situations.

Re: Bazel – Correct, reproducible, fast builds for everyone

#182

Post by [deleted] » Wed, Mar 25, 2015, 9:50 PM UTC

nevir wrote: post #180

dpark wrote: post #178

Earlier quoted context omitted.

No, it's something that Perforce allows (because it scales sufficiently). It has nothing to do with C++. You can impose order within the monolithic repo by partitioning projects into their own branches or directories and only pulling down the necessary pieces. Whether this is better than a bunch of small repos is debateable.

Perforce (the product) doesn't really scale sufficiently for the Googles/Amazons/Microsofts of the world, sadly. I think they've all moved to custom forks/implementations due to the insane SPOF that Perforce servers are (and their hardware requirements). But up til that point, heck yeah!

[deleted]

Re: Bazel – Correct, reproducible, fast builds for everyone

#183

Post by dpark » Wed, Mar 25, 2015, 9:50 PM UTC

nevir wrote: post #180

dpark wrote: post #178

Earlier quoted context omitted.

No, it's something that Perforce allows (because it scales sufficiently). It has nothing to do with C++. You can impose order within the monolithic repo by partitioning projects into their own branches or directories and only pulling down the necessary pieces. Whether this is better than a bunch of small repos is debateable.

Perforce (the product) doesn't really scale sufficiently for the Googles/Amazons/Microsofts of the world, sadly. I think they've all moved to custom forks/implementations due to the insane SPOF that Perforce servers are (and their hardware requirements). But up til that point, heck yeah!

Well, Perforce in its default state may not scale sufficiently, but at least two of the companies on that list have managed to make it work (presumably with a lot of investment, though). :)

I didn't know Amazon was using Perforce. I interviewed someone from Amazon recently and he indicated they were on Git for most things now.

Re: Bazel – Correct, reproducible, fast builds for everyone

#184

Post by gagomes » Thu, Mar 26, 2015, 4:11 AM UTC

dpark wrote: post #183

nevir wrote: post #180

Earlier quoted context omitted.

Perforce (the product) doesn't really scale sufficiently for the Googles/Amazons/Microsofts of the world, sadly. I think they've all moved to custom forks/implementations due to the insane SPOF that Perforce servers are (and their hardware requirements). But up til that point, heck yeah!

Well, Perforce in its default state may not scale sufficiently, but at least two of the companies on that list have managed to make it work (presumably with a lot of investment, though). :) I didn't know Amazon was using Perforce. I interviewed someone from Amazon recently and he indicated they were on Git for most things now.

Amazon has phased out perforce a year ago. There is very little left, most repositories (perforce, svn, etc) were migrated to git repositories.

Re: Bazel – Correct, reproducible, fast builds for everyone

#185

Post by rpereira » Thu, Mar 26, 2015, 6:11 AM UTC

OneMoreGoogler wrote: post #104

habosa wrote: post #4

Working at Google, Blaze is one of the technologies that amazes me most. Any engineer can build any Google product from source on any machine just by invoking a Blaze command. I may not want to build GMail from source (could take a while) but it's awesome to know that I can. I think this could be hugely useful to very large open source projects (like databases or operating systems) that may be intimidating for contri…

> Any engineer can build any Google product from source on any machine A little too optimistic :) You can't build Android, Chrome, ChromeOS, iOS apps, etc. via blaze.

http://i.imgur.com/zQ1m75U.gif