5 ms·

does anyone know why chrome can't do containers, this is also why i use firefox

• black_puppydog 4y ago
  It would seem its again the interest of one of the biggest contributors to the open source code base of chromium...
  • charcircuit 4y ago
    For discussion about it. https://groups.google.com/a/chromium.org/g/chromium-dev/c/IZ7peQHHWiE https://groups.google.com/a/chromium.org/g/chromium-dev/c/IZ... In response to asking about supporting multiple profiles between different tabs. >Extraordinarily difficult. I would expect person-years of effort for this, as the link between profile and window is deeply ingrained throughout the code. Chrome doesn't support containers because it would take a big investment that no one is currently willing to make. Google doesn't want to spend millions of dollars and deprioritize more important work for a niche feature that not that many people benefit from.
    • cute_boi 4y ago
      It is a lie when we know ghost browsers essentially do the same. I think it is just not in the best interest of Google because it might hurt their bottom line i.e. ads.
      • hgsgm 4y ago
        You can open a new window for a separate session, just not a new tab.
    • sirsinsalot 4y ago
      I am doubtful about the person-years of effort. It's an indirection.
      • bayindirh 4y ago
        Or the code is specially laid out that way over the years to make this a person-years effort.
        • sirsinsalot 4y ago
          Come on, no software project is ran with that level or "what if" foresight. I'll go with incompetence over conspiracy.
          • bayindirh 4y ago
            No "what-if" is needed to pull of that kind of thing. As an advertisement company, just never prioritize this separation, and do not discourage this "integration" in PRs. You're done. Build while fresh. P.S.: Microsoft is actively rigging its software, lastly VS-Code just for these things, but it's another can of worms I have no desire to open again.
      • stuaxo 4y ago
        In this writeup [1] about adding Rust to Chromium there is a note on the architecture shared state in the architure which may explain the difficulty "... Chrome is built on foundational but really wide C++ APIs, such as the //content/public layer. We examined what it would mean for us to build Rust components against these types of APIs. At a high level what we found was that because C++ and Rust play by different rules, things can go sideways very easily. For example, Rust guarantees temporal memory safety with static analysis that relies on two inputs: lifetimes (inferred or explicitly written) and exclusive mutability. The latter is incompatible with how the majority of Chromium’s C++ is written. We hold redundant mutable pointers throughout the system, and pointers that provide multiple paths to reach mutable pointers. ..." [1] https://security.googleblog.com/2023/01/supporting-use-of-rust-in-chromium.html https://security.googleblog.com/2023/01/supporting-use-of-ru...
      • deleted 4y ago
        [deleted]
• ajb 4y ago
  It does have profiles, which can be used in the same way. Haven't used it in a while, I think the limitation is that you can't use a different profile per tab; you need a whole new window
  • chupasaurus 4y ago
    FF has that profile system too.