6 ms·
Seems like this gets re-posted every few months. We don't actually have a single repository, although Google3/Piper really is huge and dominant. Android, Chrom
by cmrdporcupine 7y ago
Seems like this gets re-posted every few months.
We don't actually have a single repository, although Google3/Piper really is huge and dominant. Android, Chrome, Fuchsia, and myriads of other projects don't exist in the monorepo (well, they are mirrored there) because the tooling and libraries there are really geared towards server deployment, not devices.
- melling 7y agotosh and others do a lot of reposts, Wikipedia links, etc karma farming?
- tosh 7y agostumbled upon it (again(?)) in a recent comment on "Is Git irreplaceable": https://news.ycombinator.com/item?id=21980556 https://news.ycombinator.com/item?id=21980556 and thought this might yield an interesting discussion
- Tomte 7y agoWhy does it matter to you? Does this submission hurt you?
- melling 7y agoI’m simply pointing out why we get lots of repeat submissions. Some stories are great and worth seeing every few years. Your anger gave away the fact that you do the same thing: https://news.ycombinator.com/submitted?id=Tomte https://news.ycombinator.com/submitted?id=Tomte The one downside is that it creates a lot of noise on HN. It forces new stories off the first page quicker. Also, stories about Jerry Lee Lewis’ marriage to a 13 year old isn’t HN, for example.
- Tomte 7y agoI'm not angry, actually. I just wonder why you're so invested in what I'm doing. I'm actually proud of it. More people should un-earth cool stories and submit them. About Jerry Lee Lewis: I disagree. The sheer fact that moral compasses were so wildly divergent between America and England, of all pairs of countries, so recently, is quite on-topic, in my opinion. Also, I think it's great that you found only one story you disagree with in the thirty stories my submission page shows. Clearly you approve of my selection. > I’m simply pointing out why we get lots of repeat submissions. That's explicitly okay, as the moderators point out all the time.
- melling 7y agoYou joined the conversation. I mentioned another user. I quickly looked at your account once you became indignant. I scanned your last submissions page and saw you’re karma farming too and picked out the most egregious submission. I didn’t say it wasn’t ok. I’m sure I do it occasionally. I’m waiting for the first person to write a karma farming AI. Take great stories, determine a decay time, then repost. “HN Karma Farming with Deep Learning (in Rust)”
- fierarul 7y ago> I’m waiting for the first person to write a karma farming AI. Take great stories, determine a decay time, then repost. > > “HN Karma Farming with Deep Learning (in Rust)” This probably doesn't even need any AI, just some scrapping and scripting to determine when it's worth resubmitting. Somebody should implement this, seems like fun. Of course, if it's done with deep learning... then it would be something else. Maybe even determine correlation with other themes in the other news of the day/front page, or month, etc.
- willvarfar 7y agoMachine learning is just a currently popular approach that is called “AI”. Expert Systems are also AI, and a title that called a karma whore bot AI wouldn’t be technically misleading...?
- hombre_fatal 7y agoYou’re forgetting that people actually have to upvote submissions. Presumably not everyone sees every submission on HN every time thus are candidates to upvote it. Sure, write that karma farming bot. Seems like a good service to those of us who want to see good content we may have missed, generate new discussions on classic content. Complaining about “karma farming” has always seemed like a weird jealousy thing to me. Where you presumably care so much about karma that you’re annoyed over your arbitrary concept of karma-fairness. Who cares? If someone can get karma by reposting classic content for HNers who missed it the other times, more power to them. They reposted the content to an audience that wanted to see it. You can’t always take it personally or lash out at others just because you’re not part of that audience.
- geofft 7y agoIn a well-designed karma system, karma farming is something to encourage because it means users are posting content that helps the website. (I don't know many well-designed karma systems, but, that's at least the goal. The feedback cycle exists for a reason.)
- bradleyjg 7y agoI have five figures worth of karma. I don’t see what it gets me exactly or why anyone would want to farm it, but I guess there are all kinds of different hobbies.
- dang 7y agoOn HN, a small number of reposts is ok if a post hasn't had significant attention yet in the last year or so. This is in the FAQ: https://news.ycombinator.com/newsfaq.html https://news.ycombinator.com/newsfaq.html. It's true that repostiness per se is annoying, but it's more annoying for good submissions to miss out on attention because /newest is something of a lottery. Allowing a small number of reposts is a way to mitigate that randomness, until we can maybe work out a better solution.
- OzzyB 7y agoCould we have this pinned because the whole "Google uses a Monorepo and so should you" has become a huge meme and grown legs. And you're right this topic is on a circular timer.
- tosh 7y agoimho the problem space of evolution + stability of systems is becoming more zeitgeisty (more people are aware of the challenges and stumble upon monorepo as a tool to deal with this among other things) related: * unison * clojure (immutability, spec, …) * blockchain * microservice architecture
- cmrdporcupine 7y agoI mean honestly, having worked with a monorepo here, I'd definitely consider it for other places. It has advantages.
- lanstin 7y agoThe only arguments I have found against monorepo that don’t seem wrong are “the developers aren’t that good at git and can’t handle it.” Other wise it’s just making it harder to find out what code is where.
- rakoo 7y agoWell Google's monorepo is not git, and not even a "standard" one because it's not just a VCS: it's also a storage and a build infra, all in one. So while it's true that many developers wouldn't be comfortable using monorepos in git, it's not the right criticism. The real one is "there is no unified tool to do it correctly". Or at least I don't know of any.
- jefftk 7y agoAnother thing your examples of projects developed outside of the main repo have in common is that they're open source. When I was working on an open source project at Google (mod_pagespeed) we initially developed it in the main repo with exports to GitHub. Then we moved our source of truth to GitHub to make it easier to work with external contributors. (Speaking only for myself, not for Google)
- cmrdporcupine 7y agoNot all are open source, I just refrained from referring to internal projects.
- jefftk 7y agoMy understanding is that >99% of internal-only projects are in the main repo. If you think I'm missing something, perhaps write me internally (same username) and if I'm wrong I'll post here saying so?
- forwhomst 7y agoThe outcome kinda depends on how you want to count the Linux kernel.
- cmrdporcupine 7y agoAlmost everything I work on hasn't been in the main repo for the last 5 years. I work in the hardware PA, and before that Fiber. I mean, it's all mirrored _into_ there, but work happens in separate git repos, using gerrit. Prior to Fiber, yes, I worked in Google3. I've been @ Google for 8 years.
- jayd16 7y agoThat still sounds like a monorepo. Google is using external projects and has public facing projects so isn't mirroring the way you should handle it? In what way could it be more monorepo like?
- cmrdporcupine 7y agoThese projects are mirrored _into_ Google3, not the other way. And not all projects that aren't in Piper/Google3 are external facing. In fact only a minority of them are. I'm just not going to name them, for obvious reasons.
- opportune 7y agoMirroring only allows dependencies in one direction. Let's say package A is only in the monorepo and package B is mirrored into the monorepo. A can depend on some snapshot of B, (of, say, a client library) but B can't depend on packages from A, because outside of the monorepo B has no knowledge of A. Also, one main advantage of a monorepo is you can make changes across many packages at once. The canonical textbook example is changing the API of my service: I can find all the instances in the monorepo of where that API gets used and change both the API and update all the calling instances in an atomic operation. You can't (or at least, shouldn't) do that to mirrored projects because the mirror in the monorepo is downstream from the source of truth for the project.
- konschubert 7y agoIf you make backwards-incompatibilities API changes like this, you also need simultaneous/atomic deploys across all services. On the other hand, if you aren’t doing simultaneous/atomic deploys, then having a monorepo may actually be an obstruction.
- opportune 7y agoYeah, that's the part I left out because it does get complicated when it comes to releases. For simplicity's sake, let's say everything actually gets bundled into one binary and released together.
- Cyph0n 7y agoCisco uses a monorepo approach for IOS-XR. All platforms exist within the same repo, but the build system picks up only what’s needed to build the required platform’s image. Of course, the scale is much lower, since it’s a really a single OS.
- Someone 7y ago"We don't actually have a single repository” This article doesn’t claim that. Its title doesn’t imply it, and its second sentence denies it: ”today the vast majority of Google's software assets continues to be stored in a single, shared repository”
- colejohnson66 7y agoIt seems to imply it. Maybe not deliberately, but it confused me at first.
- hacker_newz 7y agoYou are being pointlessly pedantic. A lot of people still think Google has only one repo because I articles like this.