I like the fact that FreeBSD doesn't surprise me.
Windows is constant surprises, often unpleasant.
Linux is somewhere in between.
Windows is constant surprises, often unpleasant.
Linux is somewhere in between.
Not too surprising for me. While FreeBSD is vastly different than GNU/Linux (yes, need to include the GNU userland tools here for sane comparison), both systems aim at POSIX compliance, so there are already enough things that "work the same" from the user perspective. Of course, here you will notice lots of differences as well.I am still surprised by the how easy migrating has been.
You guys who use FreeBSD as a daily driver on desktops.
Just curious, why you've picked FreeBSD instead of Linux, Mac...? IMHO, it would be great to have this kind of information up to date in 2023.
I agree X11 is much better than VNC and other remote desktop systems but X server is abandoned and it sounds (for me) that X11 is with similar fate.For desktops, I also find a network aware display system an important factor. Quartz and Wayland are pretty much out since they can only really do VNC which is pretty much a Windows 95-era technology. Windows RDP is by far the best but X11 is actually pretty close if you don't use a ridiculous GUI toolkit. So since "modern" Windows is basically unusable in other critical ways, I guess FreeBSD (and OpenBSD) with X11 win by default!
It was a worry for me some years back. But most of it is FUD and an attempt of self-fulfilling prophesy (possibly as a sleazy campaign for Red Hat's Wayland to reach maximum market penetration). Make no mistake, we will all have died of old age before something appears that will replace X11 fully.I agree X11 is much better than VNC and other remote desktop systems but X server is abandoned and it sounds (for me) that X11 is with similar fate.
No, it is not.but X server is abandoned
This xrdp solution uses Xvnc underneath. It really just translates the protocol so you can use the RDP client.I never tried Wayland, so just have to ask this. Yes, RDP easily "beats" remote X11, so I prefer it. And there's net/xrdp which comes with an optional plugin (or driver?) for Xorg to support RDP directly in the X server.
It can do that, but also has the option to implement RDP directly in the X server, see x11-drivers/xorgxrdp.This xrdp solution uses Xvnc underneath.
This is almost useless nowadays as fewer and fewer applications use "standard" widgets (e.g. implemented in COMCTL).It unfortunately misses out on the best part of Microsoft's RDP. The network aware systems (including the network aware UI widgets).
I seriously doubt that, but unfortunately can't verify because for me, xorgxrdp segfaults, so I have to take the deviation using VNCMicrosoft's RDP and X11 (not via SSH/X11) still are orders of magnitude faster.
You'd be surprised. The other day I had theOh, I also doubt plain X11 ever performs acceptably (that is, as soon as you're using anything more complex than e.g. athena widgets).
This is almost useless nowadays as fewer and fewer applications use "standard" widgets (e.g. implemented in COMCTL).
If by that, you mean "oh, VNC will solve it", then yes. But, why not more implementations of RDP? In my experience, this works remarkably well and performant, even without any "standard widgets" (instead, even playing a video in some remote GUI worked accetably for me ....)However, we definitely seem to be going the wrong direction.
I was unaware that the RDP implementations did something outside of Xvnc which you mentioned they do in your last post.But, why not more implementations of RDP? In my experience, this works remarkably well and performant, even without any "standard widgets" (instead, even playing a video in some remote GUI worked accetably for me ....)
And *this* is a good question, but I never did the necessary research, so I can only guess: there must be more options than just "render widget on remote" and "send compressed raster-image". Most likely, there's also a way to send other rendering commands (around the lines of GL, DX, ...?).I guess the question is what does RDP do differently that is improving performance?
Strange. I use VNC regularly, but the Mac OS specific version. Why? I have a desktop Mac in an office that's next to a bedroom, and that machine is used for scanning and document management (because two large scanners and piles of paper just need a big desk). But late in the evening, when family members are asleep in the bedroom, I don't want to be sitting in the office and work right there, since it would wake them up. So instead I use the Apple flavor of VNC from my laptop, while sitting in the living room. The internal network is decently fast (wired 100-base-T for the desktop machine, 802.11n WiFi for the laptop), and I can work on the remote machine with just minor delays. And most of the work involves using PDF file previews of documents, and web pages (using Safari as a browser). It's not quite as snappy as sitting there directly, and the screen resolution gets somewhat screwed up, but for this application VNC works just fine.VNC was... well it worked but just as horribly as it did 20 years ago.
In all fairness, it could be a number of things. I could also be overly pedantic about what I classify as a decent remote experience. I also tend to prefer smaller / lower resolution monitors to most people so in many ways I would assume my experience is one of the faster ones. All I know is that crusty old X11 forwarding does seem to yield better results.I wonder whether your performance problem is not so much intrinsic to VNC, but a specific problem of Firefox' rendering, or a bad integration of VNC with X.
Plasma 5.27 has them, and I actually like them... I didn't like those menus in GNOME, but KDE pulled the idea off pretty nice, IMHO.ridiculous hamburger menus etc..
Then... why?I intend to get a PC (I use Mac) and try to use FreeBSD seriously as a desktop OS.
I'm also considering OpenBSD as some say that it works good on laptops (suspend/resume for example) and that the documentation is the best. I don't find the latter to be true, there is no equivalent to the FreeBSD handbook for example.
Sorry if this is off-topic.
The FreeBSD handbook is good (although it did used to be a little more consistent before it became a glorified wiki).I'm also considering OpenBSD as some say that it works good on laptops (suspend/resume for example) and that the documentation is the best. I don't find the latter to be true, there is no equivalent to the FreeBSD handbook for example.