*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There is no single "BSD" development project. However many people conflate FreeBSD with "BSD" merely because it is the largest of the currently active operating system projects. You might be one of those who assume FreeBSD = BSD.
The four main active development projects -- DragonflyBSD, FreeBSD, NetBSD, and OpenBSD -- are all separate projects with separate staff, seperate goals, separate strategies, and separate direction. These systems have diverged over many decades, though all are based upon one of the releases of original Berkeley Software Distribution, or are forks of each other.
There is no single "BSD" development project. However many people conflate FreeBSD with "BSD" merely because it is the largest of the currently active operating system projects. You might be one of those who assume FreeBSD = BSD.
The four main active development projects -- DragonflyBSD, FreeBSD, NetBSD, and OpenBSD -- are all separate projects with separate staff, seperate goals, separate strategies, and separate direction. These systems have diverged over many decades, though all are based upon one of the releases of original Berkeley Software Distribution, or are forks of each other.
Disclaimer: I gathered this information via the Internet, via Google, in about 10 minutes. An experimental Wayland or Weston development noted or available for testing does not mean that the individual project has stated any direction to remove or supplant their X11 software. For more information on strategy or direction, please refer to to the individual projects.
DragonflyBSD
Latest release: 4.8.
X11: third party (dport or package) X.Org 7.7
Other direction:Wayland, experimental
FreeBSD
Latest release: 11.0.
X11: third party (port or package) X.Org 7.7
Other direction:Wayland / Weston, experimental
NetBSD
Latest release: 7.1.
X11: integrated X.Org or XFree86, or third party (pkgsrc) modular X.Org
This wasn't the question that was asked, though this was noted in my reply above as "third party." FreeBSD and DragonflyBSD treat X11 as an add-on, OpenBSD integrates it, while NetBSD users have a deployment type which depends primarily on platform architecture.
I don't see X11 disappearing any time soon. Wayland is something designed by X11 developers, but is ultimately freedesktop.org stuff and thus "Linux driven" and dependent on Linux DRM/KMS drivers. It's in early development and while the Red Hats of this world may jump onboard sooner than most, it's not yet a given that it will eventually completely replace X11.
I don't see X11 disappearing any time soon. Wayland is something designed by X11 developers, but is ultimately freedesktop.org stuff and thus "Linux driven" and dependent on Linux DRM/KMS drivers. It's in early development and while the Red Hats of this world may jump onboard sooner than most, it's not yet a given that it will eventually completely replace X11.
I hope that you are right...
It would be terrible to start about 20-30 years again development for make again WMs. All X11 applications would be completely waste... 20-30 years of waste of time.
Well like it or not, simpler compositors seem to be lined up to replace the whole X11 kitchen sink and window managers. This is the kind of thing which other platforms had since the 1990s. I don't exactly look forward to it nor dread it, I find myself indifferent. If we get more responsive desktops, cleaner code and better security, it has to be better right?
Well like it or not, simpler compositors seem to be lined up to replace the whole X11 kitchen sink and window managers. This is the kind of thing which other platforms had since the 1990s. I don't exactly look forward to it nor dread it, I find myself indifferent. If we get more responsive desktops, cleaner code and better security, it has to be better right?
Bigger complex codes that are heavy are the destination which is going Linux. You will have some day no choice, since most distros take modern things / graphical compositor codes.
Soon or later, you will have to move to BSD... you won't have any choice. This is happening already with SYSTEMD.
No, on the contrary, it doesn't come much heavier or complex than X11.
I would say that there's always a choice. Slackware Linux does not use systemd as is the case with some others and Gentoo Linux and Linux From Scratch gives the option to build without it. Red Hat and Debian would seem to be the wrong way to go if you want to avoid systemd.
Linux went maintstream and some people don't like the result. gnome, KDE, et al and all the underlying automagic, messagebus and *kit stuff has existed for years, but there were few complaints or references to "UNIX philosophy" from end users. It's all inevitable really while you have much of these projects being corporate funded/controlled, rather than in the hands of hobbyists/academics.
No, on the contrary, it doesn't come much heavier or complex than X11.
I would say that there's always a choice. Slackware Linux does not use systemd as is the case with some others and Gentoo Linux and Linux From Scratch gives the option to build without it. Red Hat and Debian would seem to be the wrong way to go if you want to avoid systemd.
Linux went maintstream and some people don't like the result. gnome, KDE, et al and all the underlying automagic, messagebus and *kit stuff has existed for years, but there were few complaints or references to "UNIX philosophy" from end users. It's all inevitable really while you have much of these projects being corporate funded/controlled, rather than in the hands of hobbyists/academics.
LINUX is made for everyone.
People who come from MS Windows, willing for change, will install KDE or GNOME.
People who do some research will install TWM, CTWM, GNUPLOT, and LATEX/XETEX/ whatever TEX and their bibtex, for serious stuffs.
People, who are learning programming will install Java, Python, Mono,... believing that C/C++ is a loss of time.
and people, who are responsible of famous Linux distributions, will bring Systemd, Pulseaudio, heavy libraries, and remove for fun, all the working part of Linux for modern unstable, most unwanted, programmes.
People who come from MS Windows, willing for change, will install KDE or GNOME.
Maybe, not sure what your point is...?
Quote:
Originally Posted by Xeratul
People who do some research will install TWM, CTWM, GNUPLOT, and LATEX/XETEX/ whatever TEX and their bibtex, for serious stuffs.
It's more likely that people will install whatever they want to install.
Quote:
Originally Posted by Xeratul
People, who are learning programming will install Java, Python, Mono,... believing that C/C++ is a loss of time.
Disclaimer I am not a programmer, the days when I dabbled in C are long gone (the MS-DOS days):
The language you learn and use depends on what you want to do. e.g. if you want to hack device drivers, then you need to learn C. But if you're writing some other application, then other languages and toolkits are what you want. Ideally you want to be linking to exiting code, rather than reinventing the wheel. This is how modular systems are put together and how the free software eco system "works".
Quote:
Originally Posted by Xeratul
and people, who are responsible of famous Linux distributions, will bring Systemd, Pulseaudio, heavy libraries, and remove for fun, all the working part of Linux for modern unstable, most unwanted, programmes.
You perhaps misunderstand what "Linux distributions" are. If you are not one of the developers, involved in the project or donating money, then you don't have a say. If you don't like what a distribution is doing, you don't use it.
You perhaps misunderstand what "Linux distributions" are. If you are not one of the developers, involved in the project or donating money, then you don't have a say. If you don't like what a distribution is doing, you don't use it.
I just want to point this out as the entirely backwards thinking that plagues certain controversial software projects. A distro and the software that its composed of is nothing without its community, if there are no users then there will likewise be no one reporting issues, solving them or otherwise maintaining it.
I think all projects welcome users and bug reports - that's a given. But software development projects are generally not democracies (or anarchy) where anyone can suggest anything (and then let someone else do all the work implementing that).
Your Linux distribution, Slackware, for example is a benevolent dictatorship. You get to use Patrick Volkerding's personal Linux distro, designed according to PV's personal tastes - for free. Slackware is entirely financed by sales, via the Slackware store or any donations. You can buy merchandise or not and you can use it freely. What you don't really have is a say. You can suggest something, it might be considered, but when all is said and done - the man decides.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.