Let’s solidify the BSDs on the desktop! reddit / BSD ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 21:57 So, I have a proposition for anyone who’s interested. There’re lots of people who’re interested in FreeBSD as a desktop system, but the project simply isn’t interested in that. Additionally, there’re a few derivative projects that basically take the base FreeBSD system & customize a desktop on top of it. Still, there’s only so much that they can do. What I propose is a separate project that works on all of the necessary intermediate layers (the glue) for turning the BSD systems into real desktops. There’re a few subsystems that need to be created & I’m hoping that we can get together enough people to specifically work on those systems. So, who’s interested? ---------------------------------------------------------------------- xplosm · 2021-05-01 22:09 Have you heard of helloSystem? Sure it's based on FreeBSD but the developer is creating things from scratch, including a desktop environment based on the GUI guidelines from early Mac OS X and introducing new paradigms for current work flows. I think his ideas can be ported to other BSD families and can also be enriched by eager proponents like yourself. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 22:12 Yes, I’ve heard of it. While we do need a new desktop, I’m also looking beyond that. Specifically, we need things like driver frameworks, a new display server, unified configuration management, etc -all specifically for the BSDs. I’m not looking to be a clone of some other system, I’m looking to see what a truly desktop-focused BSD could be. ---------------------------------------------------------------------- [deleted] · 2021-05-01 22:16 I'm definitely willing to offer a helping hand. Documentation, makefiles, offering helpful input and perhaps even donating hardware to such an effort. I suggest making a matrix or IRC channel for this. ---------------------------------------------------------------------- [deleted] · 2021-05-01 22:17 [deleted] ---------------------------------------------------------------------- [deleted] · 2021-05-01 22:18 I don't really think Mac OS is the ideal personally and if we're just going to play second fiddle to someone like that then I wouldn't personally be interested. I really really pride functionality over looks, so for a DE I'd rather see something that looks basic but recognizable and easy to use. Enlightenment 16, CDE, IRIX Interactive Desktop, etc. Would be what I would suggest we base something off. I do like Haiku though, tracker reminds me of tool chest. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 22:18 I need to learn more about matrix, & about how to create an IRC channel. ---------------------------------------------------------------------- BubblegumTitanium · 2021-05-01 22:40 you dont like ghostBSD? ---------------------------------------------------------------------- Jeff-J · 2021-05-01 22:44 The only real weakness I see is needing wifi drivers. Then again, I don't care for DEs. I prefer something simple like i3, FVWM, Fluxbox, etc. As for CDE, have you tried the NsCDE theme for FVWM? I haven't yet, but will likely soon. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 22:45 I think you may be misunderstanding. What I’m proposing is software that’s consumable by GhostBSD & any other desktop-focused BSD derivative. The GhostBSD project can only do so much. For instance, they don’t do device drivers, display servers, nor unified configurations. I’m specifically looking to make life easier for such projects. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 22:48 I’m looking at more than just DEs -far more. Currently, the future of the BSDs as desktop OSes is at the mercy of the Linux community. There’s a lot of glue code that we need, but don’t have, so we get it from Linux. There isn’t enough manpower in the BSD projects to create & maintain that glue, so I’m proposing a project that does so. ---------------------------------------------------------------------- [deleted] · 2021-05-01 22:49 [deleted] ---------------------------------------------------------------------- life_on_marx · 2021-05-01 23:03 Ok, can you give us some examples of this glue? I'm not sure I completely follow what you want to do here ---------------------------------------------------------------------- [deleted] · 2021-05-01 23:13 [deleted] ---------------------------------------------------------------------- kraileth · 2021-05-01 23:16 Very much interested in a project like this! I especially like the scope: Not fragmenting the landscape with another FreeBSD desktop spin but looking to create something that the existing projects can consume. It also makes a lot of sense to target BSD in general and not just one single OS. What exactly do you have in mind? We could start identifying which gaps currently exist. That would make it easy for people to participate here even if they don't have the time or skills required to actually contribute code. Here's a couple of ideas that immediately came to my mind: 1. There's no common permissively licensed GUI toolkit. The closest that we have is [FLTK](https://www.fltk.org/) which is LGPLv2 with static linking exceptions. There's a couple of lesser known ones like [Fyne](https://github.com/fyne-io/fyne) (BSD 3-clause), but I haven't taken a closer look. 2. Some people insist that "Xorg is dead". While that's certainly not the case as even on Linux most desktop systems are not yet compatible with Wayland, the latter is definitely where things are going. OpenBSD has [Xenocara](http://xenocara.org/). The [Hyperbola project](https://www.hyperbola.info/) which is currently Arch Linux- based but looking into re-basing on OpenBSD, has adopted Xenocara and uses it instead of Xorg even on Linux. Could be interesting to try and bring it to FreeBSD and NetBSD as the common windowing system. Ideally in a way that it could be imported into the base system as an optional distset. Having X in base and never breaking would be very beneficial for any BSD desktop spin! 3. Linux allows for multiple users logged in simultaneously while this does not work on BSD (i.e. logging in, opening some graphical programs, going to the screensaver, selecting "switch user", logging in another one, logging out and after unlocking the screen still have the session of user 1 present). I don't know where this limitation comes from (session management? "seats"?) but it would be helpful to address them for a better desktop experience on machines used by more than one person. 4. There is no both graphical and native BSD display manager. For years we basically only had SLiM, now we also have LightDM with a basic greater. At some point we had PCDM which was not bad but it's Qt-only and it's as dead as the whole graphical TrueOS project. There's certainly more, but these 4 are some of the major pain points that I'd really like to overcome at some point. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 23:17 Well, for one thing, we need our own video driver API & framework, so we won’t always be stuck following the whelms of Linux video driver API changes. Also, we need a way to unify configurations (w/ an API included). Next, we need a new display server. The Linux world is moving to Wayland, so X will basically be dead. But let’s face it, for the past decade or so, most of the desktop stack has been based on X been mostly Linux-centric -with most of the development there being done by the Linux community. That isn’t an exhaustive list. There’re many more things that we need, but don’t have, leaving the core BSD projects no choice but to either try to get scraps from Linux or do without -with both options causing a definite lag behind Linux on the desktop. ---------------------------------------------------------------------- [deleted] · 2021-05-01 23:17 I run Intel with nvidia graphics. I can speak for that combination working well for a FreeBSD desktop. I don't use wireless networking personally, but from past experience with FreeBSD on a laptop, I didn't have any trouble with an 802.11n card. I still don't think 802.11ac is supported yet on FreeBSD ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 23:20 Just to clarify, the point isn’t to create another BSD, the point is to create glue systems that any of the BSDs can use. After all, sharing with each other is bound to work a lot better than trying to share with Linux. Who knows, maybe this could have the unintended side-effect of bringing the BSDs closer together. ---------------------------------------------------------------------- kraileth · 2021-05-01 23:26 When you say "configuration management" - what do you mean by that? A graphical application for system settings that understands that setting the hostname in FreeBSD means defining it in /etc/rc.conf as *hostname="something"* while on OpenBSD it'd be a line in */etc/myname*? Or something else? ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 23:30 No, I mean a new configuration system that allows all configurations to be in one file in /etc, with a unified API for accessing those configurations. The GUI app would use that API to manage configurations & to restart daemons that rely on those configurations. ---------------------------------------------------------------------- reddit_original · 2021-05-01 23:32 How would this be any different from any other desktop software you can install right now? How is it different than installing Gnome or KDE on Linux where you install the program on top of it (and FreeBSD, too)? I don't understand. ---------------------------------------------------------------------- msouza_rj · 2021-05-01 23:41 I would echo this suggestion. I had the same experience with KDE and would say we are not THAT far from having a great Desktop. If we add those nice conveniences like auto detection & etc no other platform would beat it. Cirurgic improvements could nail it and turn the Desktop experience way up. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 23:42 The point is to provide what’s needed to make a cohesive desktop system. What’s possible now on the BSDs isn’t a cohesive desktop system, it’s a command line system with a desktop duct taped on top of it. Linux is better in that regard, but not much better. At the end of the day, if we’re all honest with each other, the current desktop doesn’t actually feel like an integrated part of the BSD world. The core projects don’t have the manpower to provide what’s necessary for that, nor is it necessarily their goal to do so. ---------------------------------------------------------------------- kraileth · 2021-05-01 23:45 While I'd like to see something like this, I'm not sure if it would have a realistic chance to be accepted by most BSD users. Still I'd like to propose [Elektra](https://github.com/ElektraInitiative/libelektra) for that purpose. It's permissively licensed (BSD 3-clause), well thought-out and documented, very flexible and upstream would be happy to work together with the BSDs. I also like their "context-aware configuration" model. They haven't been terribly successful on Linux as each and every system component is being maintained by someone else, but on a BSD with full control over a dependable base system it has a lot of potential. ---------------------------------------------------------------------- [deleted] · 2021-05-01 23:45 > Linux allows for multiple users logged in simultaneously while this does not work on BSD (i.e. logging in, opening some graphical programs, going to the screensaver, selecting "switch user", logging in another one, logging out and after unlocking the screen still have the session of user 1 present). I don't know where this limitation comes from (session management? "seats"?) but it would be helpful to address them for a better desktop experience on machines used by more than one person. That's not simultaneous user sessions, that's just saving a session while another is active. The proprietary UNIXes have supported simultaneous user systems for decades (SGI and the CADDUO being a good example). Consolekit/Logind are what do that on GNU/Linux, but we don't actually need to go that route. Assuming the applications play nice, we can simply "save" a session's open programs, states and such when a user logs out, only to resume them. That's also tied partially to suspend/resume stuff. There's always multiple ways to attack a problem. The answer isn't always complexity. Xenocara is just X11R7/Xorg with greater security features. it has some issues with OpenBSD-native APIs such as bsd authentication and pledge that would either need to be adapted for the others, or else ifdefined out. ---------------------------------------------------------------------- [deleted] · 2021-05-01 23:47 [deleted] ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 23:47 I’m not opposed to using this. We don’t have to write all of the code ourselves. Pulling in other projects that’re BSD licensed is perfectly fine with me. Also, I’m not here to try to force the core projects (or any other project) into using what I’m proposing. My point is just to make it available. ---------------------------------------------------------------------- [deleted] · 2021-05-01 23:50 I can make it... but I don't wanna run it. ---------------------------------------------------------------------- kraileth · 2021-05-01 23:50 Makes perfect sense. If you succeed in gathering a couple of people, this would be one thing that I'd offer to look into. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 23:51 As I stated just a moment earlier, “...I’m not here to try to force the core projects (or any other project) into using what I’m proposing. My point is just to make it available.” Use it. Don’t use it. It really doesn’t matter. You’re not the only group of people who want a better BSD experience on the desktop. ---------------------------------------------------------------------- reddit_original · 2021-05-01 23:51 That doesn't answer my question. Well, actually, maybe you did. >Linux is better in that regard, but not much better. ALL operating systems are "command line systems" with third party software of this type installed on top of them with maybe Windows being an exception to a point. The only way to make it different is to integrate the software into base and that's never going to happen. Which desktop software are you going to permanently choose for the next 20 years? ---------------------------------------------------------------------- demetrioussharpe · 2021-05-01 23:55 Actually, not all of them are command line OSes with third party GUIs on top of them. That’s only prevalent in the *nix world, in regards to modern OSes. There’re other families of OSes that do it differently. For instance, macOS & Windows doesn’t fit into that category. Neither did BeOS. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:04 But let’s not act as if GhostBSD doesn’t use software that doesn’t come from the core FreeBSD project. As we all know, it uses OpenRC, instead of the standard init system. So, it stands to reason that the project just might need something that we end up providing. Maybe not today, but tomorrow is another day. ---------------------------------------------------------------------- kraileth · 2021-05-02 00:07 >That's not simultaneous user sessions, that's just saving a session while another is active. The proprietary UNIXes have supported simultaneous user systems for decades (SGI and the CADDUO being a good example). > >Consolekit/Logind are what do that on GNU/Linux, but we don't actually need to go that route. Assuming the applications play nice, we can simply "save" a session's open programs, states and such when a user logs out, only to resume them. That's also tied partially to suspend/resume stuff. Ah, I guessed that it'd be consolekit which was responsible for this. Thanks for confirming! However we've had that for ages and for some reason it didn't work while it does on Linux. Anyway - I'm not saying that we should mimic Linux in this case (or any other). I'm sure most people would welcome better solutions. >There's always multiple ways to attack a problem. The answer isn't always complexity. Certainly! Not even in the broader Linux community all people are happy with stacking layer upon layer and adding more and more bloat until the whole thing eventually explodes. If something can be solved simply and elegantly that's always preferable. >Xenocara is just X11R7/Xorg with greater security features. it has some issues with OpenBSD-native APIs such as bsd authentication and pledge that would either need to be adapted for the others, or else ifdefined out. Hyperbola doesn't use the unmodified upstream code. Guess that they've either ifdef'd out OpenBSD-specific stuff or otherwise modified the source. Still I think that Xenocara could be something that all the BSDs could agree on. OpenBSD has traditionally been very supportive in letting others also use their work. I'm thinking of all the -portable versions of their tools. ---------------------------------------------------------------------- reddit_original · 2021-05-02 00:07 I already mentioned Windows as an exception. BeOS is essentially dead. OSX on Macs is UNIX so, essentially, the same as the BSDs. This just isn't going to happen. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:12 I was taking specifically about families of OSes. BeOS is dead, but Haiku is replacing it. MacOS isn’t Unix, it’s a combination of custom Mac code, Mach, & BSD all wrapped together with its own windowing system -not a third party windowing system. While it includes BSD code, it’s definitely not the same thing as a BSD system. That’s made obvious the moment you try to use the command line. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:12 If you think it’s not going to happen, then there’s absolutely nothing preventing you from ignoring this post. ---------------------------------------------------------------------- [deleted] · 2021-05-02 00:15 [deleted] ---------------------------------------------------------------------- reddit_original · 2021-05-02 00:16 Ignoring the thread gives only one sided responses. One doesn't learn of the possibilities and impossibilities listening to only one side. ---------------------------------------------------------------------- reddit_original · 2021-05-02 00:18 >MacOS isn’t Unix [MacOS is certified UNIX](https://www.opengroup.org/openbrand/register/) ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:22 You don’t know what could possibly come up out of this post. You don’t know today what you might need tomorrow. Currently, you’re in the same situation as the rest of the BSD community -dependent on the Linux world for desktop software. One of three things is going to happen: 1. You’ll end up pulling in even more Linux software just to have a desktop. And make no mistake, at this point, the whole desktop stack is basically Linux software. 2. You’ll end up pulling in software similar to what I’m proposing. 3. You’ll realize that the only way to not do item 1 or item 2 is to either write the software yourself or drop your project. It’s inevitable. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:23 The only way to truly know the possibilities is to write the code. Anything else is merely wishful thinking. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:25 Having a Unix certification doesn’t mean it’s actually Unix. It merely means that it can fill in for a Unix system. There’s no actual Unix code in macOS. ---------------------------------------------------------------------- reddit_original · 2021-05-02 00:26 If you make a fool talk long enough, eventually they make it evident what a fool they are. You are a fool. There is no need to carry on this conversation with a fool. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:29 Before you call people fools, you should actually read your own evidence. This is on the site that you linked & it proves exactly what I said. “UNIX certification is a trusted and open system industry standard, ensuring that products conform to the most exacting criteria for portability, compatibility, and global interoperability. This enables buyers to specify UNIX conformance in procurements, facilitates Boundaryless Information Flow™, and enhances the perception of the UNIX system as a consistently stable, flexible, and reliable operating system.” [The certification guarantees conformance, it doesn’t magically turn something into actual Unix](https://www.opengroup.org/openbrand/register/) ---------------------------------------------------------------------- waitman · 2021-05-02 00:41 I've been using FreeBSD as a primary "real" desktop machine for a long time. I've used Gnome, i3, xfce, KDE. I get bored with one after several months and switch it up. They all run well. I don't remember seeing anywhere where "the project" said they weren't interested in it. But maybe it's true? I pretty close to having my remote FreeBSD desktop project working. So like a person can pay a dollar and use a FreeBSD desktop for a day. It's pretty much for people who travel. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:41 Intriguing. ---------------------------------------------------------------------- segfaulting · 2021-05-02 00:48 > necessary intermediate layers (the glue) ... There’re a few subsystems that need to be created Okay, what "glue" are you talking about? What is a "subsystem"? Give some examples. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 00:49 Read the comments. I’ve already done so. ---------------------------------------------------------------------- [deleted] · 2021-05-02 01:04 THANK YOU. People are actual definable idiots for thinking UNIX Certification is anything more than a political money manuever by the Open Group to get more $ ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 01:07 Facts. You can tell when you’re dealing with someone who probably isn’t old enough to know the difference. ---------------------------------------------------------------------- [deleted] · 2021-05-02 01:08 or someone that cares way too much about trademarks. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 01:09 Indeed. ---------------------------------------------------------------------- losthalo7 · 2021-05-02 01:17 Beyond BeOS, MS Windows, MacOS 9 and earlier, AmigaOS, and some niche products and things in development, it sure does seem like there's a desire for a gui-based OS and it's not easy to get one out the door with any longevity. It's obviously a lot of work and hard to maintain momentum because of that. Apple decided to bolt a proprietary gui on top of a BSD base and abandoned original MacOS. So, is the idea to come up with a gui that can run on top of any of the BSDs to leverage folks from across the BSD community to build it to get enough folks working on it and enough adopters to get longevity? I'm not sure there are enough folks that feel a need for a multi-user capable gui and aren't happy enough with what X11 and a window manager or existing DE can provide. ---------------------------------------------------------------------- jwbowen · 2021-05-02 01:17 Yeah, the state of Wi-Fi drivers is why I don't use a *BSD on laptops. Sure, I could use a USB dongle but with laptops cutting down on ports these days, I don't want to give up the slot. So I stick to Linux there. Using a *BSD on a system that always has a wired Ethernet connection is just fine, though. And I'm also the kind of person that uses a WM (I've gone back and forth between i3 and dwm) over a DE. ---------------------------------------------------------------------- [deleted] · 2021-05-02 01:22 (Note: I talk a lot about FreeBSD, but not as a way to exclude other BSDs. It's just what I know and have experience in.) I don't think we are at a point where we can compete with Linux on the desktop anymore. There aren't enough people to build up the same level of frameworks that the Linux community already has, and that we mostly already borrowed from them. In my experience contributing to several FOSS applications, linux folks' attitudes towards development were linux focused because that's what they use and care about, not because they are deliberately ignoring BSD (some are genuine Linux fanboys and don't care about breaking with BSD compatibility, here's looking at you GNOME, but most aren't.) BSD doesn't get as much support because there are fewer BSD contributors. They're making the products they want, and if we want them too we just have to step up and maintain BSD backends. KDE is a good example of a project that tries to abstract interfaces away from backend implementations, and opens the door for BSD to provide their own backends. For a good example, look at their hardware interface library Solid: [https://api.kde.org/frameworks/solid/html/](https://ap i.kde.org/frameworks/solid/html/) and in general more libraries here: [https://api.kde.org/frameworks/index.html](https://api.kde.org/framew orks/index.html) ​ We could bring BSD desktop up to Linux desktop standards by stepping up our contributions to those desktops. I mentioned KDE before, because they already have a lot of the groundwork laid to make a great FreeBSD based OS. You mentioned writing a new display server in another post... I'm not sure how realistic that is. Will vendors support it with drivers? Xenocara looks interesting, but if it lacks vendor support then it isn't going to be making any real inroads into the desktop space among general users. And those are the ones you're interested in attracting, because the power users are already capable of configuring a desktop BSD. ---------------------------------------------------------------------- [deleted] · 2021-05-02 01:28 [deleted] ---------------------------------------------------------------------- kraileth · 2021-05-02 01:30 Xenocara is basically Xorg + some OpenBSD modifications as well as a way to build it monolithically like it was before "modular Xorg". Especially the latter characteristic makes it an interesting thing for other BSDs IMO. Having (bare-bone) X11 in base would be an excellent thing for a desktop spin of any BSD OS. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 01:37 No, it sounded really real. The fact that GhostBSD is even bothering to present a desktop-centric BSD proves most of my points for me. The fact that most of that desktop software used by GhostBSD comes from the Linux world proves the rest of my points for me. Like it or not, most of the desktop software that’s supposed to be shared by the overall *nix community is written by the Linux community. As such, it’ll always have a Linux spin to it. Now, like I said, there’re only 3 paths ahead of you. Regardless of your feelings, you WILL go down one of those paths. Now there’re things needed by more BSDs than just GhostBSD. I’m trying to coordinate the development of those things. That’s what’ll make a difference. But you’re sitting here saying 2 mutually exclusive things. On one hand, you’re claiming that GhostBSD needs help. On the other hand, you’re claiming that you’d never use anything created by what I’m trying to arrange. Well, which one is it? ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 01:39 You might be right about there not being enough users that want something more than what’s currently available. There’s only one way to find out for sure. ---------------------------------------------------------------------- [deleted] · 2021-05-02 01:43 The fact that it is not a fork of Xorg, and tracks upstream development, is good. I didn't look to closely at vendor support. I got that idea from Hyperbola's wiki, which said nvidia users should use the nouveau driver. Maybe the one from NVIDIA would still work, I don't know? I suspect it might. I agree that having a stable X in base would be an excellent idea for a desktop-focused BSD. ---------------------------------------------------------------------- [deleted] · 2021-05-02 01:52 Anyone here old enough to remember 1 800 ITS UNIX ? ​ BSD isn't Unix either. lol ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 01:58 You’re right, it’s technically not. However, there’s BSD code in Unix. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 01:59 I remember using SunOS in the earlier part of m career. It was already old by then. ---------------------------------------------------------------------- [deleted] · 2021-05-02 02:27 [deleted] ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 02:33 Yes, I know who you are. You also know who I am “demetrioussharpe”. But this isn’t specifically about GhostBSD, it’s about the overall BSD community. There’re things that you’ve already told me would be nice to have, but you don’t see anyone doing the work. Well, I’m here trying to get some of those things organized, but you’re now acting like some of those things are no longer nice to have. Understand that I’m trying to help more than just GhostBSD users. There’s a large variety of people who want a desktop-centric BSD & most of them want different things. I’m trying to provide a focal point to allow those things to come into existence. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 02:36 Also, I NEVER said that GhostBSD will use my stuff. I said the stuff will be consumable by GhostBSD. At no point did I ever say that the GhostBSD project was going to use it. So, there’s no actual pressure from me for you to use any of it. ---------------------------------------------------------------------- [deleted] · 2021-05-02 02:55 [deleted] ---------------------------------------------------------------------- northrupthebandgeek · 2021-05-02 05:43 > ALL operating systems are "command line systems" with third party software of this type installed on top of them with maybe Windows being an exception to a point. Another exception here would be Haiku (and BeOS, by ascent). And at the end of the day, I'm starting to think that Haiku *is* what the OP's looking for. Haiku already pulls heavily from the BSDs for a lot of things (particularly drivers), and it doesn't seem unreasonable for that to be bidirectional - especially seeing as how Haiku is permissively licensed. Encouraging greater mutual intelligibility and interoperability between Haiku and the BSDs seems like it'd be of immense mutual benefit. ---------------------------------------------------------------------- kraileth · 2021-05-02 06:50 Hyperbola is a project of the "libre" kind, Stallmanites. They GPL3 everything, use the de-blobbed Linux kernel and so on. Proprietary packages are not acceptable for them at all - that's the sole reason for promoting noveau. If the proprietary nvidia driver was available on Hyperbola, there's really no reason it wouldn't work. ;) ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 06:59 I've been using FreeBSD as my main desktop for +6 years without any issues. I have an ASUS, a ThinkPad, and a Samsung ActiveBook Series 9, all running FreeBSD with DWM, composite screen, wifi, etc. I frankly don't see the need of creating a parallel development track to fix what it ain't broken... I know I am going to be trolled for this, but here it goes: FreeBSD (or any BSD for that matter) is not for beginners, what's wrong with that? I've been involved with Linux since the early days, and I've followed the evolution of the OS since 1996 (yup, I'm that old). And what you suggesting here sounds a lot like what happened with the Linux development: the desire to make it more popular, drove the community towards the current bloatedness of DEs with a gui for everything. It's just useless. ---------------------------------------------------------------------- kraileth · 2021-05-02 07:01 True. I'm also putting illumos on the table. It could use any help it can get, but at the same time there's some incredibly capable people around there from whose work we can profit. The already de-facto (and still increasing) monopoly of Linux in Open Source does not only threaten the BSDs but any other OS. I'd simply be unhappy with a lack of choice if Linux just didn't care about anything else. But there's evidence that they are in fact turning into the new bully (think e.g. GPL zealots very hostile behavior towards OpenZFS, overall getting more arrogant acting and so on). Might be high time to organize something like "project counterweight". ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 08:01 If you haven’t had any issues, then that’s great for you. However, there definitely ARE issues that many others have ran into. They need to be addressed, which is the whole point of this post. The proof of that is in the comments. You’ll notice that many others are agreeing with this post -that’s not by accident. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 08:07 Of course there are issues. If you want a dumb OS then stick with Windows or MacOS. BSDs, open source in general, will require your ability to think, learn, solve and adapt. What’s wrong with that? ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 08:12 What’s wrong with that is that the majority of people use computers to get work done, not to fight with the OS in order to accomplish simple tasks -nor to endlessly fiddle with settings. This has nothing to do with having a “dumb OS”. At the end of the day, a computer is a tool that’s supposed to make tasks easier. No one should have to “think, solve, & adapt” just to use their computer to do tasks that’re inherently simple on other systems. Sure, you can use a hammer to build a house, but there’s a reason that nailguns exist. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 08:30 You should take a good look on what is the purpose of BSDs then. Honestly, saying that no one should have to think, learn and adapt is demoting intelligence and promoting dumbness. That’s beyond usability or user friendless. ---------------------------------------------------------------------- kraileth · 2021-05-02 08:34 There are valid use cases even for people who are willing to dig into using more powerful albeit less intuitive things: Even if you're using a tiling WM and are an expert zsh, tmux and neovim user - maybe you have a wife that you share some of your machines with? While I'm sure that my wife *could* learn awesome or i3, there's nothing I can think of that would make her *want to*. So I'm stuck with machines that have both awesome and MATE installed. And there's really no reason why we shouldn't have the best possible desktop experience for people who like conventional full-blown DEs when it comes to the BSDs, is there? ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 08:34 You should take a look at what the purpose of a tool is. People aren’t supposed to adapt to their tools, their tools are supposed to adapt to them. You’re trying to make a case for using the BSD systems to be inherently difficult. People like you are the prime reason that most issues don’t get fixed. People have better uses for their time than to spend it perpetually fighting with their OS. Clearly, there’re people who disagree with you -you aren’t in the majority. ---------------------------------------------------------------------- kraileth · 2021-05-02 08:36 This! An ideal OS would allow you to customize it as deep down as you wish to - but not require you to do so if you don't. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 08:43 Exactly! I am not the majority of people. Just like BSD. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 08:50 I am making the case that using BSD systems should be focused on stability and security. User-friendliness comes second because if you want a desktop to do "simple tasks", macOS does that better than anyone. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 09:41 I understand the desire of sharing the power and the beauty of a FreeBSD desktop with more people. It's a noble desire, really. But it's also potentially pointless because just like the author of this post mentioned, people don't want to think and learn by themselves. They want everything done and ready, and they want to ignore the fact that ultimately, placing potentially performance and security impacting designs and decisions in the hands of someone else, it's a bad idea. And when things go wrong since they don't know what and why things went wrong, they blame the others, they blame the OS, they blame people like me...sounds familiar? BSDs are server-oriented OSes. It's an important reminder because their development is *NOT* desktop-oriented. They can make great and stable desktops, but that's *NOT* their *MAIN* purpose. There have been several attempts to create a BSD Desktop, but they all failed mainly because when you dive into DEs and what people are looking for in a DE, you quickly realize that much of the code that makes the happiness of penguins will never be integrated on the BSD Core. And there is a reason for that. Linux is not a UNIX descendant, Linux is at best a UNIX-like OS, created by Linus Torvalds because UNIX was too expensive. ---------------------------------------------------------------------- kraileth · 2021-05-02 10:34 I see your point and tend to agree. At least the blaming game *does* sound familiar ("stupid program / OS / machine!"). Such people also tend to see pretty graphics and think "beautiful!". Then there are the others who *love* the fact that their OS is stupid: It does what the user wants, doesn't try to be smart and thus doesn't get in the way all the time. Those people usually see the pretty graphics and think "what a horrible waste of resources!". Personally I'm clearly in the second camp: If a program requires me to use the mouse (and is not about, say picture editing and such) it's a potential candidate for a better replacement. I want to be able to build from source, I want to take responsibility for the effects of those tunables that I happened to mess around with without being completely sure about how they work. I learned touch-typing three times (initially my country's standard variant of QWERTY and then two alternative ergonomic layouts over the course of ten years). Love the adventure and don't mind the pain you go through for a while until things settle down and become second nature again. And still I'd like to see a flawless desktop experience in the mainstream sense of that becoming a thing on BSD. For one thing it will lower the barrier for people to come to a BSD and then start exploring at their own pace. For another I like choice (and am very concerned about the de-facto monopoly that Linux has built up). People being able to chose between a Linux-based and a BSD-based desktop without having to rule out the latter in most cases would be a 100% improvement of the current situation. If we ever really reach that point, chances are that I might venture off to help a bit in illumos land... And then there's an important argument that's not easy to dismiss: More people mean larger hardware coverage. One may like or dislike helloSystem, but it's a fact that it's ranking #3 on [BSD- hardware.info](http://bsd-hardware.info) just behind OPNsense and FreeBSD. Thanks to it more probes were collected than from OpenBSD! Even people like us who wouldn't use a full-blown DE on our BSD workstation profit from other people having the option to do that. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 11:00 No, you’re making the case that the BSD OSes are supposed to be difficult to use. But you won't show me in any of their homepages where they say such a thing. In fact, your argument didn’t even mention stability nor security. You’re attempting to “move the goalpost”. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 11:02 Precisely. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 11:03 Other people like BSD, too. They also like getting work done -which is actually the whole point of having computers in the first place. ---------------------------------------------------------------------- probonopd · 2021-05-02 11:25 For helloSystem we would like to see alternatives to stack elements that appear to have mainly been developed by Red Hat for Gnome on Fedora on GNU on Linux, and have then been spilling over to to other systems. Including: * XDG Desktop specification (does not take into account the dynamic nature of applications being able to come and go on removable media; what we need would be more like 'Launch Services' on the Mac) * D-Bus (too convoluted for simple IPC) * Avahi (Why not use the original, mDNSResponder across the stack) * gvfs (mounts network shares but draws in many Gtk-related dependencies and is poorly documented) * PulseAudio (yes there is OSS, but can it switch the current audio device without having to restart the application?) * Wayland (has been under development for ages and is still not working smoothly, e.g., with screen recording tools) * Pipewire (a partial workaround to fix what Wayland breaks) * polkit (similar to sudo but more complicated) * Many different configuration file formats (looks like FreeBSD wants to use a simplified form of JSON called UCL, but what is actually using it?) * Visually unpleasant surrogate fonts (Liberation, DejaVu,...) that make all "Linux" desktops look the same (and ugly) FreeBSD itself would be better suited for the desktop if its approach to packaging would ensure that Xorg and graphics drivers are always released in sync with the core, maybe as a "graphical core", and that packages cannot disappear from one day to the next in `quarterly` packages (by strictly freezing them once a quarter). ---------------------------------------------------------------------- northrupthebandgeek · 2021-05-02 11:25 Re: BSD code sharing bidirectionality, the CDDL poses the same issues as the GPL, so while I do happen to like Illumos and the various distributions thereof (even going as far as to have used SmartOS in production), I ain't sure if in this context the Illumos/Solaris ecosystem really leaves much that the BSDs can use without sacrificing permissiveness. But still, if at least collaboration efforts are permissively-licensed then all projects stand to benefit - even Linux distros, by having a modern alternative to the GNU/systemd ecosystem. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 11:27 I agree. ---------------------------------------------------------------------- kraileth · 2021-05-02 11:49 I prefer CDDL-style file-based copyleft over the implications that come with the GPL specifically any time. But in general you are right of course. Dual-licensing things could be an option for some components. Otherwise I don't think that the illumos camp has as much of a problem with permissively licensed code as some GNU zealots have. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 11:55 Oh, you raised a very good point, thank you! To wit: \- [Freebsd.org](https://Freebsd.org): FreeBSD, The Power to Serve \- [Netbsd.org](https://Netbsd.org): NetBSD is a free, fast, secure, and highly portable Unix-like Open Source operating system. \- [OpenBSD.org](https://OpenBSD.org): The OpenBSD project produces a **FREE**, multi-platform 4.4BSD-based UNIX-like operating system. Our efforts emphasize portability, standardization, correctness, [proactive security](https://www.openbsd.org/security.html) and [integrated cryptography](https://www.openbsd.org/crypto.html). I can only recommend that you take the time to read this paper wrote by people behind NetBSD: [https://www.netbsd.org/\~jschauma/netbsd- desktop.pdf](https://www.netbsd.org/~jschauma/netbsd-desktop.pdf) Are you sure I am the one attempting to "move the goalpost" when none of those BSD implementations are targeting Desktop usage? To be honest, we're both wasting our time. We can not possibly build logical reasoning capable of making the other one see the other side of the fence or re-evaluate its position. And the reason for that is I suspect that you don't really know or understand what you're getting yourself into, how the community works and code gets approved, and me, I can not understand the desire to put glue (your words, not mine), aka bell and whistles, in the most advanced OSes we have already out there, apparently completely disregarding the purpose of the aforementioned OSes. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 12:09 Here’s the problem: while you’ve clearly implied that the purpose of the BSD OSes were to be inherently difficult to use, I’ve never claimed that the purpose of any of them was to be a desktop OS. In fact, that’s the whole point of this post -to gather the people who DO want to use any of the BSDs as desktop OSes & to create the missing pieces in order to better facilitate that process. As I’ve told others on this post, no one is forcing you to use anything. If you aren’t interested in this, then no one was stopping you from skipping this post. It seems that your entire purpose for being here is to stop others from being able to use their computers the way they want to. What’s even more ridiculous is that you see things such as better configuration management & sane graphic stacks as bells & whistles. That’s preposterous. If you want to stick to flipping switches on an Altair 8800, then do that. But if you thought you were going to hold up progress by wasting my time here, then you’re sorely mistaken. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 12:12 Fair point. By all means, go ahead and let's start a new BSD. I'll bring the beer. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 12:14 You’ve missed the point. Creating a BSD isn’t the goal of my proposal. The point is merely to make available missing pieces for people who want a better desktop experience. That’s it. In fact, the goal is to be usable for ALL BSD systems, to avoid further fragmentation. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 12:20 And that's where your mistake is when you refer to fragmentation: BSD is not Linux. Here is an interesting reading: [https://www.freebsd.org/advocacy/myth s/](https://www.freebsd.org/advocacy/myths/) ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 12:25 I haven’t made a mistake. I know that BSD isn’t Linux. You do realize that fragmentation doesn’t just suddenly happen, right? You do realize that there’s usually a starting point, right? To date, we now have 5 separate BSDs & a few derivatives: NetBSD FreeBSD OpenBSD DragonflyBSD MidnightBSD The fact that there’re 5 means that there’s already fragmentation. There was fragmentation when there were only 3. My goal to NOT increase that number to 6. I think you know all of this. In fact, I think that your goal is to be purposely contrarian. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 12:34 Give me the TL;DR about my previous post and I accept it, you have a point there. But since you didn't read it, you can't argue and everything you'd say is just opinions, not facts. This is a citation from the link I provided you just above: *"Myth: The \*BSD projects are at war with one another, splinter groups form each week* *No. While occasional advocacy may get a touch heated, the \*BSD flavors continue to work with one another. FreeBSD’s Alpha port was initially heavily based on the work done by the NetBSD team. Both NetBSD and OpenBSD used the FreeBSD ports collection to bootstrap their own port sets. FreeBSD and NetBSD both integrate security fixes first discovered by the OpenBSD team.* *The FreeBSD and NetBSD projects separated more than twenty years ago. OpenBSD and DragonflyBSD are the only new BSD projects to split off in the last twenty years."* I am not a contrarian, I am pragmatically telling you that I don't see the point of trying to solve a problem that does not exist... ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 12:38 I read that & it’s actually false, in regards to OpenBSD & DragonflyBSD being the only groups to split off. In fact, I’ve even listed the other one -MidnightBSD. So, while I DID read yours, you didn’t read mine. MidnightBSD was first released in 2007. Just because YOU don’t see something at a problem doesn’t mean that the problem doesn’t exist. [MidnightBSD homepage](https://www.midnightbsd.org) ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 13:41 Well, I'm just quoting here: **Myth: You cannot make your own distributions or derivative works of \*BSD** You can. You just need to say in the documentation and source files where the code is derived from. Multiple derivative projects exist: \[List of derivatives...\] * [**MidnightBSD**](https://www.midnightbsd.org/) **is a FreeBSD derived operating system developed with desktop users in mind. It includes all the software you’d expect for your daily tasks: mail, web browsing, word processing, gaming, and much more.**" So, as you can see, the BSD community has no issues with "DERIVATIVES", it's encouraged really. And there is nothing wrong with that because, opposed to what happened with Linux (fragmentation), the BSD core remains consistent and stable even when a **derivative** becomes a **stand-alone** project choosing to pursue its "own distinctive approach." ==> splitting. Your intention, although noble, if carried seriously and to its end, will end up creating a new derivative of one of the BSD core projects just like all the others, clearly defeating your purpose. Why? Because BSD is the core system, not a desktop-friendly or unfriendly OS. BSD derivatives have **Lumina Desktop.** If you want to achieve "unity" within the desktop framework, then you should be talking with all DEs developers out there. Specifically, addressing your suggestions to KDE, Gnome, LXDE, Xfce devs. Now, that's a real challenge. I've spent years diligently contributing to KDE development, debugging, testing, and providing feedback, and consistently seeing the enormity of bugs resulting from people's disregard for LSB. BSD does **NOT** suffer from the same issues. Or maybe I'm too narrow- minded to understand your goals. Either way, carry on, I don't want to stop progress, even if, now and then, I admit it requires a detour on wonderland. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 13:43 You do realize that the FreeBSD project doesn’t speak for the entire BSD community, right? Additionally, nothing that you’ve posted counters my point about fragmentation. So, once again, you’re being contrarian. Why’re you here? ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 13:53 You just have to show me where else on the BSD community there are visions contrarian to the FreeBSD project and I will be on my way. Again, very good question. Why am I here? Because you're talking with me... ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 14:40 Actually, I don’t have to show you anything. This post is for a specific group of people, of which you’re obviously not. So, why did you even bother coming to this post? This post clearly wasn’t talking to you before you came. I wasn’t talking to you before you came. And since this post obviously isn’t for you, why’re you here? ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 14:47 This is under the BSD flag which concerns me. So I equally don’t need to justify my presence here neither. If you’re so not interested on my view of your opinion about the needs of the BSD community, you have the choice to ignore me. It still doesn’t explain why you feel so aggravated by my vision of your proposal ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 14:47 Since nothing about my proposal actually concerns you, it sounds like it’s simply time to block you. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 14:51 Please do it. It’s easier to silence the reason rather than question it’s own ideas. ---------------------------------------------------------------------- grahamperrin · 2021-05-02 15:13 > … imagined working on a tailored version of KDE Plasma for FreeBSD, along with just a few nice hardware management tools would make a great desktop. … If you haven't already seen it: * https://forums.freebsd.org/threads/78594/ – five pages, but much of the noise is unrelated to KDE. ---------------------------------------------------------------------- grahamperrin · 2021-05-02 15:45 > … learn more about matrix … The FreeBSD channel, https://matrix.to/#/!IBdGSejslGivmIcnQs:matrix.org Daniel there might help. I also have some experience (from using Element, and its predecessor Riot for four or five years) … never needed to create a channel, but I'm sure that it's not difficult. ---------------------------------------------------------------------- grahamperrin · 2021-05-02 15:56 > … own video driver API & framework, … new display server. … Very thought-provoking. Kicking the ball around … what timeline would you *imagine*? ---------------------------------------------------------------------- grahamperrin · 2021-05-02 16:04 > in quarterly packages (by strictly freezing them once a quarter). Too strict. Think of vulnerabilities. ---------------------------------------------------------------------- tcmart14 · 2021-05-02 16:16 I'd be interested in helping out in anyway that I can. I am still learning my way around the BSDs, but can do a little bit of coding. ---------------------------------------------------------------------- grahamperrin · 2021-05-02 16:21 ### BSD > … the BSD community has no issues with "DERIVATIVES", it's encouraged … Derivatives exist, but are additional derivatives actively encouraged? ### FreeBSD I sometimes look first to the list of open source products under https://freebsdfoundation.org/freebsd-project/what-is-freebsd/ … at least one of the links there is outdated, I'll request a correction. ---------------------------------------------------------------------- grahamperrin · 2021-05-02 16:23 > the reason Or the unreasonable. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 16:26 Both reflect the unwillingness of one to engage and enrich oneself by looking into different perspectives. But at the moment you start taking my different view as a personal attack, the learning opportunity is over, for both you and me. ---------------------------------------------------------------------- grahamperrin · 2021-05-02 16:29 I'd like to occasionally help … … although I should probably describe my interest as the UX side of things i.e. things being better as an end result of the *glue*. (I'm married to KDE Plasma.) ---------------------------------------------------------------------- grahamperrin · 2021-05-02 16:32 It's not just the difference. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 16:41 It’s far too early to consider timeframes. We don’t even have an official project, nor actual members. This was merely a proposal. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 16:50 "Encouraged" is probably unnecessarily strong wording, but I don't see any resistance to making a derivative. I guess the emphasis should be on the "CAN" rather than "SHOULD". Thanks for the note. ---------------------------------------------------------------------- rEded_dEViL · 2021-05-02 16:53 Most certainly not. ---------------------------------------------------------------------- [deleted] · 2021-05-02 16:56 [removed] ---------------------------------------------------------------------- [deleted] · 2021-05-02 19:07 [deleted] ---------------------------------------------------------------------- sazaland · 2021-05-02 19:13 I use Slackware Linux on the Desktop currently: I considered OpenBSD strongly but ultimately found the limitations too great for what I’m trying to do(mostly have a good gaming and personal use system). All things being equal I’d probably prefer using OpenBSD, they just aren’t currently. Slackware is by far the most BSD-like of the Linux OSes, and resists a lot of the things that introduce unneeded complexity into Linux, like dependency resolution in package management, systemd, etc. IIRC PAM was only very recently implemented. My point is Slackware functions as a haven in Linux for people who want a simple UNIX like system for the desktop. I literally find Slackware easier to manage long-term on a desktop than more popular systems like Ubuntu, because it avoids the ease of use complexity that likes to break and create conflicts. I think the person you’re responding to is interpreting your goals with BSD as looking to introduce the complexity in question: (something that would drive otherwise-interested people like me away as well). From my perspective that could be the case(I’m not sure), but it’s certainly not necessary to make BSD more workable as a desktop, with Slackware being the case in point from the Linux side. Really BSD from my perspective needs drivers(graphics especially), maintenance/porting of key libraries which tend to get dropped by upstream for BSDs, and an answer for the kerfluffle going on with Xorg/Wayland(not looking forward to Wayland myself, curious to see how Slackware handles it down the line, Xenocara is a real possibility). FreeBSDs Linux binary layer is also quite useful in my limited experience even if it’s not an ideal solution on any level. ---------------------------------------------------------------------- Snaffu100 · 2021-05-02 19:45 Ultimately if you have a vision probably the best way to kick it off is get a basic framework functional and show it to folks so they have an idea of what you are trying to do and they can then jump in and help out. Otherwise you could easily end up spinning in committee and never have any code at the end of the day, just a lot of ideas. Most of the projects that are successful have their beginnings with a BDFL that ultimately drives the development direction. As you can see by the comments a lot of folks have ideas and a lot of their points seem valid but they also many times conflict. Someone needs to be the person who resolves that side of things and decides the direction. The majority of people on here agree with your premise that the desktop could use some serious improvement. Sharing with Linux will ultimately not work as we are seeing with Gnome and KDE, they are heading in a direction that won't work for BSDs as they have dependencies on things like, but limited to, systemd and wayland. If people want to continue to use fluxbox or fvwm for the next 20 years in BSD that is fine. I'm not digging with that comment, I use i3 personally currently. For the masses they don't work though. Having a cohesive desktop is a great idea, albeit a huge, and I do mean huge endeavor. I remember doing a checkout and compiled Gnome before it was at V1 to try it out and remember how much I didn't like it, but look at it now... look at the time it took them to get where they are now. Ease of use brings users, which brings apps which means adoption... that is pretty much the path that seems to work well. Being user friendly doesn't mean selling devs and power users short which used to be an argument I'd hear. I think MacOS has broken that glass ceiling. I'd be willing to bet that the majority of devs on here also have MacOS systems. Give it a shot, have fun with it and see where it leads you. That is pretty much all I can say. Ultimately the user community decides where it is going to go. Either way, you will have learned something about coding and yourself also along the way. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-02 20:07 This is probably the best comment on the post. ---------------------------------------------------------------------- _supert_ · 2021-05-02 20:56 Or, mined in several locations around the world, gives people the freedom to choose which one. Good cop/Bad cop.. If you think *I'm* deranged, you must be: this is my most salient observation today.. ---------------------------------------------------------------------- _xsgb · 2021-05-03 02:37 I remember the first time I installed FreeBSD as well as other operating systems and desktop-environment components for my daily use computers. I've also deployed and managed many different operating systems to family members and friends and more importantly in my company creating specialized cross-platform servers and desktops development tools so I can share some bits of my experiences about obtaining computing resources to achieve goals as a desktop user. So I'll also talk about my experiences maintaining GNU/Linux for others. I've always been very curious about computers and their usages. That's a plus motivating people for actually looking at operating systems and installing one of them on their computers. The great human thing about this is that I've met a lot of people in my case. It's definitely a specialized subject but it's in my point of view very widespread in the world. The reality I imagine is that still, the vast majority of humans are very curious for other things that choosing their computer OS, even more if they don't really need a computer. And that's an important point I think. Something I often say to people doing other things is that probably one of the worst thing that could happen to their enterprise is imposing a computer where there's no need for it. And that may be non- obvious. Most of the non-IT people asking me for a computer and software are mainly interested by communicating over the Internet, accessing their multimedia files, storing important documents, doing office stuff and maybe playing some games or run a mandatory windows application. Except for the game part and the mandatory windows app, this would be easily achieved by most operating systems. In addition to that, there's many other specialized tasks that will require a specific operating system just because the others won't have the software ecosystem and/or the required functionality available. Which could turn to be a feature. That's the art of knowing which software to run where and how. In my experience on a modern PC (eg: not your own old hacking thinkpad from 10 years ago) , I've found that a GNU/Linux system like Debian or Ubuntu is able to cover with very good results, the most desktop use cases I did encounter. To say it clearly, I install Debian or Linux Mint or Ubuntu to someone, tweak a few things, install the required applications, ensure there's a coherent configuration for his or her needs and voilà, It's ready to use, easy to maintain and it lasts long. Time to time there can be some questions but 95% of the answers are positive and do only takes a few minutes to be understood and applied by the user. ( Questions arise to me with Windows or OS X as well but the positivity-rate and my answers is generally far lower and I tend to become grumpy ). I also know many bad GNU/Linux experiences I had with some people, such as no graphical option to do something considered simple, badly tested packages and integration, failing upgrades, or failing post- upgrade (when the upgrade went fine but the system became unusable after), random guys installing edgy distros respecting zero standards and reinventing the wheel and just exploding in flight, left not usable with a boot failure after triggering a bug in their revolutionary super-flat themed GUI settings, a whole bunch of angry people don't accepting other people having other needs than theirs and feeling smarter because they managed to format a hard drive and to call pacstrap from the archiso but in fact having no idea about semantic versioning or regression testing. Well, many situations that can leave your computer just being a brick if you don't know what to do. There's where in my opinion BSD derivatives are already providing great results as a desktop for IT tasks and general desktop usages. I've actually never installed one to someone as a desktop but.. Believe me or not I did consider doing it to a friend having Linux Mint upgrade issues a few minutes before checking Reddit and reading this post... Outside work I've been deployed TrueNAS systems for home NAS servers to people and results were very great ( I was surprised when I heard about IXSystems future OSes based on Linux ). And I run my own network services with OpenBSD since 2014. Before that I've been installed FreeBSD on my main desktop in the AMD Athlon64 era. Following the official handbook remains me with a working X environment and a whole set of possibilities with the base system clearly documented. But that's definitely not something a person not curious about computing will ever do. And that's to consider. I did also used OpenBSD as a desktop for a time and I think it fits me better. The fact Xenocara is shipped with the install image is very handy and well integrated. And again. It's not for everyone. But it's there, it not only works, it's stable. On FreeBSD I was impressed by the consistence I had in the performances no matter the load. Everything was smooth, delivered in time. Running many usual graphical applications on FreeBSD and OpenBSD went fine for me. I'm happy with some parameters, X, cwm and a few apps. There's some points that could be enhanced like the default FVMW configuration that could make heart attack to someone seeing your computer. But I like that by design it invites you not spending too much time on your computer or if you shall do, forcing you to configures it so it fits you and makes you more efficient with it. However there's some fields the BSD derivatives ecosystems and features are actually behind Linux for my desktop usages, notably studio-audio with real-time. That's probably the main reason I use Debian with Jackd and the Pulseaudio jack sink. That's stable and it performs well with PCI, USB and Firewire interfaces. There's a lot of pro-audio software available. Having Debian also allow me to sometimes spawn Lutris and fire a random windows game trough wine without many problems and with no performance issue (there could be but it's usually easy to fix). Finally I'm only using BSD derivatives as servers actually and do appreciate their advantages here and in the same time, I'm always enthusiast for finding new uses cases. I'm convinced they're already providing the desktops many people are expecting and hope their advantages can profit more people. I've been very impressed by the work done by the hello team, which innovates to go outside the good old graphical UNIX paradigm as well as the work made to ship ready to use BSD based desktop systems featuring good desktop environments for everyone. I think maybe the care should focus on handling USB devices and their configurations, mounting various filesystems seamlessly in the desktop, installing software graphically as well, getting easier access to mass features trough GUI wrapped scripts (youtube-dl, imagemagick, renaming files...), gettings users out of "OS is the bootloader of the web browser" way, having integrated backup systems and so on. All that would probably require on the ground research, analyses of needs and expectations of the potential users. ---------------------------------------------------------------------- grahamperrin · 2021-05-03 05:53 > Gtk HOSTed BSD Ah, I never knew that … never thought to look in the wiki, but it's there https://wiki.ghostbsd.org/index.php/FAQ and more prominently https://wiki.ghostbsd.org/index.php/GhostBSD#Name > bloated, ginormous Translation: full-featured, functional `:-)` > Having a nice desktop experience doesn't take away from the minimalists if that's what they want... Some minimalists find pleasure in describing full-featured, functional systems as bloated. Don't feed the animals `:-)` ---------------------------------------------------------------------- TorMazila · 2021-05-03 08:04 "How to patch KDE-2.0 for FreeBSD?"(c) ukrainans - a question for the president Yuschenko Easier said than done: It's been decades till manufacturers have started to provide drivers for Linux, let alone other non-windows OS's. And device drivers are the fundamental thing for desktop-oriented OS, unless it's Mac OS with its own set of hardware :). "Desktop environment" is not just a fancy window manager (I used to live with TWM and all sorts of tiny window managers on a 16MB box) and a couple of softwares - it's about uninterrupted interaction with the rest of the world, gaming and so on. Niche usage like the above mentioned "I'm a c++ coder and I code in KDevelop" is one thing - easy to do but "anybody's desktop" is still years away even for Linux. ---------------------------------------------------------------------- TorMazila · 2021-05-03 10:05 How do you expect to address modern wifi and video drivers issues with their manufacturers not disclosing neither source nor programming guides&specifications? Reverse engineering isn't the best option, it's a "last resort" thing. Simulating MS windows api - is better but you have to deal with new issues again. And with video drivers for modern GPU's the situation becomes almost desperate - the only way things will be able to change is when some rich weirdo decides to launch some sort of gaming console using FreeBSD and invests many millions of $ into it. And even all of the above miraculously gets resolved - we will still face the simple fact: there's simply not enough software. Without MS Office - Linux is just for geeks, unlike OS X. And FreeBSD has even less commercial software compiled for it. And don't shout "Open/LibreOffice" - they are not 100% compatible (even if they cover 150% of needs of an average user) and any business will not tolerate potential issues. Gaming is an endless pain also - just look at Linux vs Windows stats in Steam. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-03 10:38 This is merely a proposal. Surely, you don’t expect me to already have the answers to that. Each problem will have to discussed & address to the best of our abilities. And honestly, lots of hardware is going to still not be supported, just as they aren’t supported today. The goal is to make things better. We’re not going to be able to make things perfect -especially on the first few passes. ---------------------------------------------------------------------- [deleted] · 2021-05-04 12:59 [deleted] ---------------------------------------------------------------------- demetrioussharpe · 2021-05-04 13:05 I’m not looking for Haiku, I’m simply looking to make the BSDs drastically better on the desktop. ---------------------------------------------------------------------- northrupthebandgeek · 2021-05-04 15:32 What I'm getting at there is that Haiku might give us some ideas and even code in that direction. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-04 15:36 Fair enough. In the past, I’ve considered what FreeBSD would be like if it used the BeOS architecture of incredibly pervasive multithreading with multiple server processes handling the user experience. In the end, I wasn’t sure that FreeBSD’s threading system was up for it. ---------------------------------------------------------------------- northrupthebandgeek · 2021-05-04 15:39 Sounds like a good reason to tune up some threading systems to me :) ---------------------------------------------------------------------- demetrioussharpe · 2021-05-04 15:45 Mind you, that was just an assumption of mine. I never tried to port those systems from Haiku to FreeBSD -or port the FreeBSD kernel to Haiku. ---------------------------------------------------------------------- opseceu · 2021-05-04 16:06 I'm using fbsd on the desktop for over 20 years, so: Which things can be improved ? ---------------------------------------------------------------------- opseceu · 2021-05-04 16:07 So, a pkg repo for the desktop use case, seperatly curated to handle all those issues ? ---------------------------------------------------------------------- vgk8931 · 2021-05-04 20:42 Hello System is trying to do exactly this. [https://hellosystem.github.io/docs/](https://hellosystem.github.io/do cs/) ---------------------------------------------------------------------- jimbyjpb · 2021-05-05 00:52 This has been tried numerous times. PC-BSD was one of the better ones, but iXsystems never gave it full support. Kris Moore was doing most of it on his own. I don't think the repo even exists anymore. When that hit the fan, Project Trident, started by Kris' brother Ken picked up the torch an went a really long way. They had a full desktop, including their own desktop manager (Lumina), they had a large number of custom utilities and a pretty sizeable following. The problem has always been that the FreeBSD project is 'really slow' to get upstream commits approved, especially for things are are not in their wheelhouse (they focus on server code, not desktop). Many upstream code submissions were just ignored (bluetooth fixes, wireless fixes, and a lot of other stuff). It got really hard to maintain their own 'patch tree' that aligned with the FreeBSD sources. Ken and his small team had finally had enough. They repurposed all their code to run on Void Linux after researching the best alternatives. Their write up is here: https://project- trident.org/post/os_migration/ If you want to dig into all the drama, check the Project Trident Telegram channel around mid 2019. It's all there. I decided to stick with FreeBSD, and went back to rolling my own - https://www.jimby.name/blog/2019/10/two-roads-in-a-cyber-forest/ Good luck. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-05 00:53 I have to wonder why others didn’t do as DragonflyBSD & MidnightBSD did -fork... ---------------------------------------------------------------------- demetrioussharpe · 2021-05-05 01:07 After reading your links, you’ve given me lots to think about. Honestly, if the FreeBSD project was slow on patches (even from a commercial company that was trying to help), then maybe it’s not even worth it to keep trying. It seems that the only actual way forward would be to fork. However, they were more likely to have the resources to fork than me, but chose not to. That leaves little hope for anything I can muster up -especially with so many members of such a small community being against any form of modernization. I’m not so sure that I should continue. ---------------------------------------------------------------------- jimbyjpb · 2021-05-06 02:35 I'm sorry if I discouraged you, that's not my intention. It's just a large undertaking, even for a talented crew. Look, I know and love FreeBSD on my desktop, but I also know it's got limitations that I just have to live with. Have a serious look at Project Trident. They have ported all their stuff over to Void Linux, and they have kept it going. If you want a really good desktop that is not Windows, not Mac, give it a try. You might find you like it just fine in spite of it being based on Linux. If you are skittish, try it in VirtualBox. It runs fine. As Ken used to say, at the end of the day, he just wants things to work. ---------------------------------------------------------------------- demetrioussharpe · 2021-05-06 02:43 It wasn’t you, it was the links that you posted. They led me to go look at the messages from 2019 in Trident’s telegram channel. In the end, what I want is a rock solid workstation OS that I can also use for play & that doesn’t require me to use my degree in order to set it up or use it. FreeBSD needs a better infrastructure & a broader ecosystem. But the truth is that I now think that what’s actually holding FreeBSD back just might be the community, itself. The problem has now devolved into a chicken/egg situation. ---------------------------------------------------------------------- GafiQ · 2021-05-07 20:36 Hi, linux user here. I like BSD and it seems great, but software availability is a big deal. Discord doesn't even have a native version, and I already don't like running things with wine. Although, maybe even someone can do smthn like Linux FX did and make any exe launch with wine when clicked on, so you can do that and the same for Linux executables - which will also try to install and run a deb by unpacking it and put the files in their place, to be ran with the compatabilty layer. Also, I'd live to help if I can. ---------------------------------------------------------------------- dynseli · 2021-06-07 16:14 Use Openmdns for Zeroconf which is available for OpenBSD for the Avahi/Bonjour replacement. Dbus needs to be replaced. For sound, ALSA is still prevalent in FreeBSD, while Pulseaudio isn't. Portaudio, sndio and OSS cover many programs and work well as replacements. libcanberra needs to be replaced. JACK will still be needed for special purposes. Use the best parts of Wayland, and replace parts of Xorg with that. Let all window managers and compositors work with that. Use doas, instead of sudo. A CUPS installation that builds with bmake and uses Openmdns instead of Avahi for Zeroconf. Omitting Doxygen, and replacing it completely with Sphinx for documentation. There's a few programs from OpenBSD and NetBSD that are already replacements. A big problem with ports, is that it caters heavily to Gnome dependencies, so packages are always compatible with it. No one will agree. The FreeBSD ports tree needs a fork, which can be run on other BSD operating systems, that a base package system can be done in the most simplest way, which would be easier to maintain. Gnome has too much influence in the ports tree, and it contributes too many unnecessary dependencies for backwards compatibility. Use BSD dependencies when possible, over the Linux/GNU alternatives. Keep end user programs which are of GNU. ---------------------------------------------------------------------- deojfj · 2021-08-25 13:45 Have you decided if this new desktop project will use Xorg or Wayland? I would suggest checking out the Arcan desktop engine as a potential alternative: https://github.com/letoram/arcan It has a more simple and secure design, and supports running X and Wayland programs. Perhaps it is not mature enough yet, but nontheless I'd suggest reading these blog posts that compare its architecture against X and Wayland: [The X Network Transparency Myth](https://arcan-fe.com/2018/11/16/the- x-network-transparency-myth/) [A12 – Advancing Network Transparency on the Desktop](https://arcan- fe.com/2020/10/28/a12-advancing-network-transparency-on-the-desktop/) [Arcan versus Xorg: Feature parity and Beyond](https://arcan- fe.com/2020/12/03/arcan-versus-xorg-feature-parity-and-beyond/) ---------------------------------------------------------------------- demetrioussharpe · 2021-08-25 14:48 I would prefer neither. X is now a deadend, because all of the X developers are basically from Linux & they’re all working on Wayland. But if we move to Wayland, we’d just be in the same situation as we were with X in reference to drivers. We need something else. However, what we need is something that we can build an identity behind. We don’t need multiple window managers nor desktop environments, we just need 1. There aren’t enough GUI BSD users to support tons of options anyway. I’ve been looking at Arcan & consider it a potential replacement for X. But I don’t care about network transparency or anything like that. What I care about is how easy/hard will it be to create a solid driver architecture under it in order to have the best quality GPU support that BSD can get. Lots of things need to change for the BSDs. This is the opportune time for that change to happen. ---------------------------------------------------------------------- deojfj · 2021-08-25 18:35 > I’ve been looking at Arcan & consider it a potential replacement for X. That's good to hear. Have you reached out to the developer? > What I care about is how easy/hard will it be to create a solid driver architecture under it in order to have the best quality GPU support that BSD can get. True, that's really needed. Will you make a post in the future with an evaluation of Arcan detailing if it is fit to the task? And do you have other engines in mind beside Arcan (perhaps one from scratch)? ---------------------------------------------------------------------- demetrioussharpe · 2021-08-25 21:57 >That's good to hear. Have you reached out to the developer? No, not yet. I have more research to do. ​ >True, that's really needed. Will you make a post in the future with an evaluation of Arcan detailing if it is fit to the task? I'll try to. ​ >And do you have other engines in mind beside Arcan (perhaps one from scratch)? I've contemplated doing something from scratch, but I'm not sure whether or not that's feasible, yet. I do think that this would be the better strategy for the long run. For now, it might be better to go with something like Arcan & then adding custom code to it in order to make sure that we end up with a solution that's just right for BSD on the desktop. ---------------------------------------------------------------------- deojfj · 2021-08-26 06:51 From what I've read, Arcan follows the two philosophies that are important: simplicity and security. It does seem good enough for now and has a lot of working code. I find it unlikely that any Linux distro adopts Arcan as the default desktop engine, so in the event that any BSD goes with Arcan, the author himself could decide to focus more on the BSDs. In that case, perhaps there wouldn't be much conflict of interests. And also, I think that starting a new project is going to be too much work, unless all the BSDs get behind it early on. When you have more information you should ask the *BSD devs in their mailing lists what is their opinion, and based on that go for scratch or Arcan. Cheers! :) ---------------------------------------------------------------------- demetrioussharpe · 2021-08-27 12:17 >From what I've read, Arcan follows the two philosophies that are important: simplicity and security. Yeh, I agree with that. ​ >It does seem good enough for now and has a lot of working code. > >I find it unlikely that any Linux distro adopts Arcan as the default desktop engine, so in the event that any BSD goes with Arcan, the author himself could decide to focus more on the BSDs. In that case, perhaps there wouldn't be much conflict of interests. Indeed. ​ >And also, I think that starting a new project is going to be too much work, unless all the BSDs get behind it early on. All new projects are going to be too much work. However, that doen't change the fact that they needed to be started. That's the same situation that we find ourselves in now -there're things that we need done & they're too much work, but they still need to be done. ​ >When you have more information you should ask the \*BSD devs in their mailing lists what is their opinion, and based on that go for scratch or Arcan. I'm not going to bother them with it. In fact, I think that once I make a decision, I'm going to just go ahead & go forward with my decision. I know that they're focused on building the OS that they want & that's not necessarily in line with what desktop users want.