From owner-freebsd-questions@freebsd.org Tue May 12 11:21:57 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C19582EAF75 for ; Tue, 12 May 2020 11:21:57 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49LwPK3W3sz45ZP for ; Tue, 12 May 2020 11:21:57 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de ([94.222.0.87]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPA (Nemesis) id 1N0Fh1-1jDEdI2VtP-00xLMT for ; Tue, 12 May 2020 13:21:55 +0200 Date: Tue, 12 May 2020 13:21:55 +0200 From: Polytropon To: freebsd-questions@freebsd.org Subject: Re: Microsoft Teams for Linux Message-Id: <20200512132155.dfaccc07.freebsd@edvax.de> In-Reply-To: <20200512071116.0000356f@seibercom.net> References: <20200505093624.00001df2@seibercom.net> <223da1b3-a83d-b2e8-36dc-468dcb219305@suszko.eu> <20200508113438.00006adc@seibercom.net> <9329b8e5-c973-c65e-2261-c529dbfc5e7d@suszko.eu> <20200512071116.0000356f@seibercom.net> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:rroC+Ydsmrr2frG2XYZxCpz4QhgQmV3ptbLOV3h9dtyOteYMBqZ miVsuT8RMGzX1V0SvoK4o13UIxd1uSeMMqji42/thrqXd6ykxK6d7urTtXCU0ix0ecksVG+ cjXVn+PfE2V4U4Klh9B5/Flb8OGanEPGdYJahrDpivgmnfHA9ucWuP/eWkakihC2McfM92b FXvY4U27YjKZZNya1xXAw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:03qds10SKy4=:vVOA2qiY7eVeShd/pwX8l7 v86gJaX/cL02q2kVKoA+v6Cae4tLJjJFxn/+y8rHzKVEDrKQKUD4S18Ma/VLHY0vf5UqiWHVi jxBqsktlsFWndv2/FH4AP5GRTw+aLeTgq1PmjzCgjXQSFt3wnrkxWEBFxxNy8YeB9DfhErTnQ iXid/cnheQJ1XhLW/U9PlZGStB0VL7mMWy930H6/wXVV3+x2iIGhwTAWoNAnfFvXCD3eiSurg xOA5rdDw9h0RmpzHJlDtSEsQSyQJ1nyFwLVJcXII31qfOcjRYD+hZDPZXa/lxWp4FFR5zPEaN 7jqz+pD0YPUg64nq7c98WVuyhCHDy5S90fvDbii8GLXkmKQmv0+RBkxiJ5kvjpF4mt8iGajed e33g0esvxSFjpqUjHNjNaBTiNx1zKJC8DQ/9kj+JTPefAovlmBNwPjj6CNMsTXM729xb1oNwf 9C+JHqKrs4FEMnFNcwbyLgXfv4AZRnopWhuifjkCjaxz7T/xAtyP697mnMi15wjsgRbvrr7l5 jXoAMk+mdnBsQnNcv1keEUq9JpEtFBlompoZPFGqJTAfuPNtgjgY2TuHPiZUBQM1HMk27wrBZ jGKsOftSBzft7WgJGo4/O8Q9Sicppo7+bxf/EEKnYRz5RfqgLY0dpKGGrkIk0Ux6e+Fcfwzri 8j7tGlH/Z4EYGv6U/ZwajDKFrwoT9+ln5+v2AS6fGeolO5v0vSgy74CKekyP+4uUmBiGqC5hB dMZy6XAERvwnGVGGL0xETJhtiFptRG+6etfPntIJgWJxD6Mo8VC1dr9Uymu/IZjrRR7IhI2Ao ivUjRgnqmf58kzk66i9xgGI85k1HSdnnPc6Lx3N2sobPkg8ueHFOe4L/GQjIV/28sT9q3gD X-Rspamd-Queue-Id: 49LwPK3W3sz45ZP X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-6.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 May 2020 11:21:57 -0000 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. 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. > The bottom line is this in not Microsoft's fault. That is correct. Chrome is supported, Chromium is not. And Chrome is not Chromium. And not Firefox. > To address the second portion of your post, I had a telephone > conversation several years ago with a technician from 'Brother USA.' > Yes, it regarded printer support. I wanted to know precisely why they > wrote drivers, etcetera for Linus, Debian, Mac, and I think one other > besides mobile. In any case, he told me he uses Linux at home and likes > it. He went on to say to me that writing for FreeBSD is not easy > because: > [...] > 3) He also went on to say that FreeBSD, when compared to Microsoft or > Linux or MAC, was considered too decentralized. Being decentralized can be an advantage. However, printing on Linux and on the Mac is now centralized using CUPS. So why should it be a problem to create drivers that work with CUPS on Linux as well as CUPS on the Mac, but not on CUPS on any of the BSDs? Is the difference so big? Yes, I know, it sounds like Java: "Write once, run everywhere", but it doesn't actually work like that... ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...