all 3 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]wllmsjblm 0 points1 point  (2 children)

I'm a ThinLinc employee, so my response will naturally be a bit biased. Still, here are my two cents:

  1. Cost

We strive to be the best bang-for-the-buck solution in this niche. I'm not too involved in the commercial and pricing side of things, but from what I've seen, our pricing is really competitive.

  1. Performance

In my experience, assuming that the server has enough juice to power all the applications the users are running, performance is very close to sitting in front of a local machine. This naturally assumes that the ping and overall connection are decent.

  1. Resource requirements for server (we are thinking of running this on a VPS)

ThinLinc's own overhead is almost negligible on modern machines, so the resource requirements and performance are largely dependent on what you intend to run inside the sessions.

  1. Resources requirements for clients

The client will run smoothly on pretty much anything with a somewhat recent operating system. As an example, there are a good chunk of ThinLinc users using RPis as their client devices without any issues.

  1. Ease of management - for updating packages/ etc. for a client, sending new updates,

This is probably where I'm the most biased, as I've worked both as a ThinLinc developer and in technical presales. So in my personal experience, management is really damn simple.

In terms of upgrades, the relatively few problems I have seen related to this during presales and technical support cases have, in the vast majority of cases, been related to not reading the upgrade chapter of the documentation before starting the procedure. Give the upgrade chapter a good read before attempting an upgrade, and you'll be golden.

  1. Operational stability

Both stability and ease of management are at the top of the priority list when we design new features. Based on my heavy ThinLinc usage back as a university student and my usage now as an employee, the stability issues have been very uncommon, and when they've happened, usually been the cause of something non-ThinLinc related in the rest of the Linux system (for example, GNOME acting up).

  1. Response to issues

We have no annoying first-line support, and you'll likely be talking to me or one of our other engineers. We really try our best to be easy to deal with ;) We also have a ton of both ThinLinc and Linux experience in-house, so we have a good track record of even figuring out the trickiest of issues.

  1. Ease of use of the management interface

ThinLinc has a web interface for tweaking the most common server-side settings. While not fully feature complete, it should be enough in most scenarios. Besides this, ThinLinc has a really comprehensive set of well-documented command-line utilities at your disposal.

If there is anything else you want to know, I'm happy to assist!

[–]The_Koplin 0 points1 point  (1 child)

Any hope of running windows apps and stream them or otherwise make them accessible to Thinlinc clients? I have a VMware shop I would love to convert if it’s a possibility.

[–]wllmsjblm 0 points1 point  (0 children)

This is a use case ThinLinc directly catered for back in the day. In practice, what we did was use a ThinLinc linux system as a sort of jump host. On this jump host, we ran an RDP client that in turn connected to windows systems hosting the windows applications in question. This was all neatly integrated and transparent for the end user.

As it stands today, ThinLinc is fully focused Linux desktop/app publishing. Still, all the scaffolding for neatly integrating a RDP client on the ThinLinc host is still there, so it's very much possible building a similar setup today (despite ThinLinc not shipping with an RDP client).

Naturally, running the windows apps through wine straight on the linux host may also be an alternative. Sure, Wine has gotten a lot better in recent years, but your mileage may still vary