--
You received this message because you are subscribed to the Google Groups "TigerVNC User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tigervnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/a086c2b1-0ec0-45d1-b4b5-97b401ec5b86n%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "TigerVNC User Discussion/Support" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tigervnc-users/VRhSEYSj_ao/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tigervnc-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/6354D077.23450.1182D1EA%40mikes.guam.net.
On Oct 23, 2022, at 5:11 AM, Luveh Keraph <1.4...@gmail.com> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/CAFy1yb2rL7w-28BWLAPVs9UNveiZuAZq%2BY1qnSyGvhpu5Zysqw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/BD7358F2-D96A-450E-9955-57CB54028C12%40virtualgl.org.
On Oct 22, 2022, at 11:23 PM, Michael Williams <michael.gle...@totalvu.tv> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/CAPJOi9C%3DiJxnEpKf2TxSD1pfW%3D302pqQTs%3DqrZK37-MdLZ-R5A%40mail.gmail.com.
On Oct 23, 2022, at 10:13 AM, Luveh Keraph <1.4...@gmail.com> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/C14B8F02-6B11-4C6D-945A-903F874B1A54%40virtualgl.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/CAFy1yb0E2KSLXdmNjuy35sTVVRAwt%2B3fhSue%2BCFstsZ%3Dh2SpYA%40mail.gmail.com.
TurboVNC is managed more like an
enterprise product (think RHEL or Ubuntu LTS), whereas TigerVNC
and noVNC are managed more like a rolling release (think Fedora
or Debian Unstable), so you have to pay for a commercial
implementation of them (ThinLinc, Kasm, etc.) in order to have
any assurances that the code is production-quality. Ideally,
enterprise O/S vendors like Red Hat and Ubuntu freeze a version
of TigerVNC and provide long-term bug fixes for it, but there is
a limit to what they can do, given that an upstream "stable"
branch of TigerVNC is usually abandoned as soon as the .0
release from that branch drops. As an example, RHEL 7 is still
using TigerVNC 1.8.x, and any time someone posts up on here
regarding a bug in that frozen release, the TigerVNC developers
shrug and tell them to use a newer release. The reality is that
organizations with large-scale deployments of Linux remote
desktop software don't want to upgrade their O/S or their remote
desktop software unless they absolutely have to, which is why it
makes sense to separate the two. Thus, I tend to view
O/S-supplied implementations of TigerVNC as basic remote desktop
functionality for the O/S rather than as production-ready
solutions in and of themselves.
I'm not saying any of that in an
accusatory manner. The projects have a very different project
management style that is, per below, necessitated by very
different funding models. I don't want to seem like I'm
hijacking the TigerVNC Users group to promote my own project. I
just recognize that there are some use cases and deployment
strategies that TigerVNC isn't suitable for, and I would rather
inform users of the alternatives (including ones that I don't
develop) so they can decide for themselves. ThinLinc and
KasmVNC are production-quality releases based on TigerVNC and
noVNC, but they aren't free. TurboVNC is free and
production-quality, but since I'm a one-person shop, I can't
provide the same support options that a company like Cendio or
Kasm can provide.
DRC
To view this discussion on the web visit https://groups.google.com/d/msgid/tigervnc-users/22d15284-114d-4b47-aa14-62c271cf7330n%40googlegroups.com.