Date: Tue, 12 May 2020 13:35:26 +0200 From: Maciej Suszko <maciej@suszko.eu> To: Polytropon <freebsd@edvax.de>, freebsd-questions@freebsd.org Subject: Re: Microsoft Teams for Linux Message-ID: <5894ef55-29e1-05cd-6359-e84e779cded0@suszko.eu> In-Reply-To: <20200512132155.dfaccc07.freebsd@edvax.de> References: <b64d57e2-f4d7-7618-c711-6501a652a6ac@suszko.eu> <20200505093624.00001df2@seibercom.net> <223da1b3-a83d-b2e8-36dc-468dcb219305@suszko.eu> <db68d8c4-cf3e-5a2f-63d9-f16f0b4f9559@lidstrom.eu> <fecdd83b-2061-a6c0-f927-c380cbc2b500@suszko.eu> <a0828175-6f75-92c4-ab48-bfd395e1a91d@suszko.eu> <ce6fe689-777f-7285-3483-76fb73ea3e82@suszko.eu> <f3a86f00-7e81-ec9d-2f29-c4d9bc3e0094@lidstrom.eu> <b28e6141-04bc-4f66-93e3-658929500c0c@suszko.eu> <CAM8r67Boe0dQt%2B1T8rdoubxNKaeDCaQ5UkY1nThM8UahF=WU3g@mail.gmail.com> <20200508113438.00006adc@seibercom.net> <CAM8r67DqhC37qoU99iBXPvSZAVVPezPCfKipOD-2xiig95-0TA@mail.gmail.com> <9329b8e5-c973-c65e-2261-c529dbfc5e7d@suszko.eu> <20200512071116.0000356f@seibercom.net> <20200512132155.dfaccc07.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --oPhGeWdYwqKiHtphf6QhdJGowdqt3wwHT Content-Type: multipart/mixed; boundary="nzX7JTBU5C8N7nKvfs4RLXcAVUMLCCrQs" --nzX7JTBU5C8N7nKvfs4RLXcAVUMLCCrQs Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 5/12/20 1:21 PM, Polytropon wrote: > On Tue, 12 May 2020 07:11:16 -0400, Jerry wrote: >> It is my understanding that FreeBSD does not support Google Chrome. >> That is not Microsoft's fault. That is a failure on the part of >> FreeBSD. You should be taking the problem up with them, or perhaps >> Google. Whether there is no one willing to maintain the port, or a >> systemic failure on the part of FreeBSD is the real question here. >=20 > As Chrome, unlike Chromium, is not distributed in source form > (i. e., it is not open source), distribution would only be > possible as a binary blob, as for example nVidia does it. > The interesting question could be: Why does nVidia provide > a binary blob used by the FreeBSD port, and Google does not? > You would guess that a graphics driver is much more dependent > on bein tied closely both to the OS and to X, whereas a web > browser is, more or less, "just" a user application program > that should be quite portable. >=20 >=20 >=20 >> The bottom line is this in not Microsoft's fault. >=20 > That is correct. Chrome is supported, Chromium is not. > And Chrome is not Chromium. And not Firefox. What's the difference between Chrome and Chromium that is a stopper for Microsoft to support this browser? What's wrong with Firefox that it can't be used... or maybe what it lacks? So we have the situation having two modern browsers mostly useless in such web applications. --=20 regards, Maciej Suszko. --nzX7JTBU5C8N7nKvfs4RLXcAVUMLCCrQs-- --oPhGeWdYwqKiHtphf6QhdJGowdqt3wwHT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEIoJrn47KEjxeB5CF95cXLotfKhkFAl66if4ACgkQ95cXLotf Khl27ggAo3PyKOlBLNgZLH77Mkt36i6ITwDqPeRO1ydtr4Hqc6pbYHLBPaasQwRw ywiKgVkrkWAjWEJFegA+KZirdgzr/Cx/GRAOq0ccEkbaxBZMbzjzUcTfBHRdcmFB aL3FeDz0Gw3eNsliuwtGWDH2CnOaUCBF5TgTswt2jk8ytilQl6xOw3wvsPFaZM+N bvZWs8lcsWcIe3qkGTf5M0C9BYJuG/UkYXQsD6ITyrnLYt14B44k/rs7oswsOakC ooOgdHFEo5uTD5YiiYZ1er9WKXVKoUYNzqKZXTqh8ROD1t/7SaGIDCZtqbsQdlB9 A8msNKUT9cnJ5DfNNniN0y0WDEzFmQ== =axcm -----END PGP SIGNATURE----- --oPhGeWdYwqKiHtphf6QhdJGowdqt3wwHT--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5894ef55-29e1-05cd-6359-e84e779cded0>