Google lays off hundreds in Assistant, hardware, engineering teams::undefined

  • stevecrox@kbin.run
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    9 months ago

    The FAANG companies have an internal kind of elitisim that would make staff less effective.

    If you look at any Google Java library, GWT, GSon, Guava, Gradle, Protobuf, etc… there was a commonly used open source library that existed years before that covered 90% of the functionality.

    The Google staff just don’t think to look outside Google (after if Google hasn’t solved it no chance outsiders have) and so wrote something entirely from scratch.

    Then normally within 6 months the open source library has added the killer new feature. The Google library only persists because people hold FAANG as great “Its by Google so it must be good!” Yet it normally has serious issues/limitations.

    The Google libraries that actually suceeded weren’t owned by Google (E.g. Yahoo wrote Hadoop, Kubernetes got spun away from Google control, etc…).

    • lolcatnip@reddthat.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      Every big company suffers from “not invented here” syndrome. It’s not always just because of arrogance. For example, as an engineer at Google, it can be less hassle to use a first-party library than a third-party one.

      Also your list of examples is pretty bad. Guava is one I remember filling a real need when I worked at a small Java shop, and as I recall there was no widely used alternative to Protobuf when it came out. Gradle isn’t even from Google at all!