• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle



  • Waymo doesn’t give a shit if their cars are ugly and can cover them in dozens upon dozens of cameras and sensors. They’re not selling them to consumers who care about looks, they are renting them to riders who don’t want to die on the short trip. They also only operate in a small region of the country with limited weather conditions and frequently stop service when weather is bad.

    Tesla is run by an idiot who insists that a pair of cameras and a single lidar sensor that they keep deciding to disable can somehow magically always work in all weather and lighting conditions and is selling to consumers who don’t want an ugly car and expect to be able to operate their purchase at all times

    Different constraints leads to different levels of success




  • You usually run into issues if you are trying to use off the shelf tools and git providers. IMO GitHub and GitHub actions sucks hard for monorepo. The fact that all actions have to be stored in a single directory for example almost certainly is unmanageable rats nest waiting to happen at any sufficiently large business with a sufficiently complex product or set of products.

    This is why companies like google run their own forms of git with custom wrappers to let you do things like pull a segment of the terabyte sized repo or run partial builds with tooling that basically runs some kind of graph against the changes. Bazel for example had to be invented to help solve that problem at Google and pants similarly for twitter (who also has a monorepo)

    If you are willing to invest in using tools like bazel and own building all these complex wrappers then it can be fine. But if you want to off the shelf gitlab or GitHub actions and use your IDEs built in git tooling it’s not going to be for you. That’s the difference between what’s possible or a good idea at a medium shop vs a company with 40k engineers

    In my experience at a company that just moved away from monorepo, half the off the shelf vendors and foss tools out there balk at you if you expect monorepo support. We moved away specifically because at our current company size it is more tolerable to have our different products separate and eat the occasional pain of mass pattern adjustments across the repos than to build out a team to manage the custom tooling required for a gig plus sized monorepo

    Plus, even google doesn’t have a true monorepo. Chrome and Android are not in the same repo as search for example. Find your seams and manage them appropriately


  • unique screens have unique canvas fingerprinting.

    Exactly what I just said? Don’t use unique screens and you are less identifiable. The most anonymous browser is a freshly wiped two year old Apple device running safari or chrome from a university campus or coffee shop. A million other laptops have the same base canvas fingerprint.

    Fewer people use Linux. Fewer people use specialized browsers. Fewer people have external displays. All those things make you easier to fingerprint than a vanilla machine.

    Is it possible you misread what I typed?





  • For me it’s that arbitrarily not pairing them gives a higher end experience than pairing them. You can play music over multiple by just selecting them all when you air play. The only difference is the lack to stereo, which if you have them all over your house you wouldn’t want anyway.

    Meanwhile if you do pair them, then it’s stereo only. So if they are placed around the room, then arbitrarily you can’t hear some notes or vocals out of both speakers. Plus if you use Siri, for some reason only the left speaker speaks. We have an open concept kitchen and had one speaker in the counter and one in the living room on the tv stand and it was just overwhelmingly stupid to have only the speaker in the kitchen speak back.

    It’s also stupid I can’t buy a single big home pod and pair it with 2-4 minis to make a 7.1 surround. Or even just pair more than 2 minis.