![]() ![]() There's a difference between free and free with strings. Security people don't like RATs (remote access/administration tools) because the are almost always security failures and require trusting some 3rd party, who often isn't under any financial contract. They are downgrades.Īs for teamviewer or any remote access tool that requires a third party to be involved. Canonical has a N-I-H syndrome with many of their forced changes - I can't call some of them upgrades. In 2017, they first tried to make Wayland the default. Canonical has a history of pushing new projects before they are ready just to see how bad it is. Right now, I'm blaming the distros for forcing Wayland before it is ready to be used. I'm fully confident that the Wayland guys will get a stable, production-ready, version in the next 5 yrs. ![]() I was an X/Windows programmer in the mid-1990s and wrote a number of X11 programs at the time, but the world has changed and X has changed since then. OTOH, being a F/LOSS developer in any long-used project has got to be tough with all the 'helpful' experts making uninformed comments. I have to wonder if the Wayland folks didn't consider making a local-system subprogram that could be used with X11 when the X/server and X/client were running on the same hardware, then all the remote stuff could still exist and work flawlessly as complex network agnostic sub-functions were replaced, overtime. In the last 15 yrs, lots of GNU tools added the -h option (human readable) which has completely changed how I work. When sort added the -h option, I nearly cried with joy. That doesn't mean they cannot be improved. After all, we still use ls, du, df, mv, cat, grep. Just because something is old, that doesn't mean it is flawed. OTOH, there are 15 other X11-based tools which work fine. While I love the Gstreamer can handle Wayland for screen capture, there are so many issues with Gstreamer outside of that specific use that make it unacceptable. The Wayland devs have assumed that users don't use remote X11 and X11 forwarding through ssh in sufficient numbers to have been a priority for their efforts, I'm guessing. ![]() These holes have been there 30 yrs and are well understood at this point. 1 release for those enterprise packages.Ī few of my workflows are completely dependent on security holes in X11 to work. I get the feeling the project team doesn't even look at the latest LTS until after the first. #Wayland detected teamviewer ubuntu full#Some of the programs I use won't be supported on 22.04 for a year or more as the underlying software packages are slowly updated to provide full system support. That was a Microsoft-ish move.įairness disclosure: I've been using Wayland for some time with Fedora and have had little trouble. Wayland would have been nice if, from the start, the developers had understood that their job was to provide the what user needs rather than dictating the rules. ![]() The Wayland developers did finally dispense with their intransigence, but now they are behind the eight ball and trying to catch up, even as Wayland has been forced into the starring role - and developers of other packages are trying to serve their target audiences. A better attitude from the Wayland developers would have gone a long way towards making this all more seamless. That is why developers, like those of TeamView, are having to move mountains to make things work. That is in part due to the initial snotty attitude of the developers as they took it on themselves to decide what it is that a user should and should not do on their own machines. Another instance, one of many, indicating that Wayland is not really ready for the role. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |