Slashdot Mirror


XFree86 Core Team Disbands

mumumu was among the many to write with this news: "XFree86's release engineer David Dawes has announced that "a majority of the XFree86 core team has voted in favour of my proposal to disband the core team". XFree86's News Headline has a short message about it. Why, all of a sudden? What is the successor of the XFree86? Xouvert? freedesktop.org?"

8 of 448 comments (clear)

  1. From the link... by BoneFlower · · Score: 4, Interesting

    "core team was no longer
    representative of the active, experienced and skilled XFree86 developers"

    That leads me to suspect it isn't XFree86 that is dying, just the current core team is giving up their posts- and probably to be reorganized with new members from among the referred to "active, experienced... developers"

    I wouldn't panic yet.

  2. So if this is just a political change... by Esekla · · Score: 4, Interesting

    then perhaps it's a good thing as there has clearly been a fair amount of rankling lately.

  3. Re:Why a successor? by zarr · · Score: 5, Interesting
    I can't se anything in the article that would indicate that the core developers have stopped working on it. The message by David Dawes gives me the impression that the "core team" and the core deveolpers aren't necessarily the same people.


    If you ask me, xfree86 doesn't need much "inovation". It works great the way it is! Of course, that shouldn't stop other people from taking the xfree code and do radically new stuff with it. If someone manages to come up with something that is significantly better than xfree I'll be more than happy to switch.

  4. Re:"Core Team" models need to die. by Mr+Smidge · · Score: 4, Interesting

    (NOT framebuffer because fb doesn't work well with some hardware)

    Purely out of interest, what kind of hardware does the framebuffer not work well on?

  5. Re:Jesus.....Thank God. by vadim_t · · Score: 3, Interesting

    No, we need more of those people as well.

    You've got to understand, that whatever your archievements are, that doesn't entitle you to behave as a moron. For example, I have great respect for Alan Cox. But, if I ever see him trolling slashdot while I have points, I'm going to mod him down.

    The thing that the X team did were great of course, but lately all I've been hearing of them is that they got lazy, advertised their CVS privileges as if it was some god-given privilege, while not doing almost anything at all with it, and made it difficut for people who were at that time doing much more useful work the possibility of making it easier. I'm very glad to hear that now they finally recognized that they were only stalling the development.

    Having created something Open Source shouldn't mean that you're free to be dictator of that thing. In Open Source this especially makes little sense, because the point of it is the development of a program, not the exhaltation of its authors. I remember that Linus himself said once that if he believes that Linux will advance better without him, he will resign.

  6. maybe we need a new X server (or two) by penguin7of9 · · Score: 3, Interesting

    I think we really need a new X server, dedicated to desktop use. It looks like the RENDER model is going to be the primary graphics model these days and applications expect both multithreading and lots of bitmap storage from the X server.

    Yet, the existing X server originated out of a code base that highly optimized the traditional X11 graphics model and assumed a completely different mix of clients and applications. That means that a lot of complexity in the existing server is devoted to optimizing things few people still care about.

    A new implementation could replace that code with simple, generic implementations and focus on making the stuff that everybody uses these days efficient.

    It may also be worth using C++ for such a new X server. That's not because C++ is "object oriented", but because C++ standardizes a number of facilities that big software systems need, like exceptions and resource cleanup, but for which C has no single standard.

    Actually, at the same time, it might also be good to create a second, minimal X server from scratch that is aimed at handhelds and machines with very limited resources. Some existing work on such servers is based on XFree86, but I suspect one might be able to cut things down to an X server that gets by with 100-200k of code and data with careful coding and choice of features.

  7. Re:Related to the Cygwin blowup? by JianTian13 · · Score: 5, Interesting

    Jesus Fucking Christ. How many times are people going to trot this shit out?

    /flame on

    You haven't been using Linux or X very long, have you? Or if you have, how have you failed to notice how many times someone says "X is slow/boated/sux for 3d/etc"? If you did, did you ever follow the discussion after that point, or did you just say, "Yep, I agree with them, I can stop reading now"?

    Because if you had, how did you miss the amazingly lucid explanations as to just why X does not suck; just how incredibly extensible it is; or how it does not suck at 3d, but that the real problem lies in the card manufacturers who won't release the necessary specs to allow open driver development? No, really. The fundamental problem with 3D driver development is that the card manufacturers have a limited pool of developers who can only acquire so much knowledge/expertise, and can only spend so much time developing drivers for each platform. How much better would things be if they would allow more experienced X devs to look at their code and suggest or write some improvements? We know the answer to this question; if you don't, what are you doing using Free Software?

    /flame off

    X works. X works well. X, properly equipped with the right drivers, even does 3d well. If you can't configure it yourself (no shame there; I was scared as hell the first time *I* did it), there's all these nice distros from RedHat (oops, Fedora), SuSE, Mandrake, even Debian that have tools to do it for you.

    Allright, I'm done. Back to browsing at +3...

  8. freedesktop.org by be-fan · · Score: 4, Interesting

    The fdo.o X server is most likely going to be the successor to XFree86, even if development of XF86 continues. They fd.o X server project is led by Keith Packard, who did a lot of the work on Render and Xft, basically bringing XFree86 into the 20th century. He is also getting help from people who really know what they are doing, like Jim Gettys. They are working on the following features:

    - A core X server based on the lightweight kdrive codebase (formerly TinyX).
    - Back-buffering of all windows, like OS X. This will enable OS X-style fancy window effects like shadows and whatnot.
    - OpenGL accelerated 2D rendering. This is a big step up from Apple's system, because it will accelerate actual drawing via OpenGL, not just window compositing. As a result of this, there is a lot of talk about seperating OpenGL from the X server, and allowing the X server to be just another OpenGL app running on top of a low-level OpenGL acceleration layer.

    --
    A deep unwavering belief is a sure sign you're missing something...