Announcement

Collapse
No announcement yet.

KDrive, Xnest, Xvfb Called For Removal From X.Org

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • johnc
    replied
    Originally posted by Alex Sarmiento View Post
    Sounds good to me, X have a lot of bloated functionality
    But if it never hits, it doesn't matter right?

    Only to those who want to use it, of course.

    Leave a comment:


  • Alex Sarmiento
    replied
    Sounds good to me, X have a lot of bloated functionality

    Leave a comment:


  • rafirafi
    replied
    Again...

    I imagine it will be better to just keep the support for X by I/O Kit on macosx, preferably only for the latest version. It should seriously reduce the number of lines.
    "
    - Please, can someone can explains me where is Xnest ?
    - I don't know I don't work on deprecated code, you can use an older version. You can search the git repository yourself, compile the code, reimplement it... do whatever you want, it's free software.
    - Thanks.
    "

    Leave a comment:


  • johnc
    replied
    So wait, what's the better solution that supersedes Xephyr?

    Leave a comment:


  • Sadako
    replied
    Originally posted by [Knuckles] View Post
    From my experience using Xephyr and Xnest, most of them have little things broken everywhere.
    If they are not maintained and are untested, it's better to remove them than to leave users frustrated with crashes and other problems.
    So it's better that users have no software than buggy software?

    I've used Xnest, Xvfb and Xephyr for various things in the past, and would hate to see them go.

    At the least, I really think they should wait 'till all the functionality of these servers which aren't currently available in the DDX drivers are implemented first before removing the servers, it'd provide motivation for whoever wants the servers removed to actually get the work done, whereas if the servers are removed first then we will likely never see some of the functionality re-implemented, and will effectively be removing functionality for no good reason.

    And before someone mentions "removing 30,000 lines of code" as a good enough reason, I wonder how much of that code actually affects the Xorg server itself?
    Pretty sure they're all separate code trees within the source tarballs...

    Anyways, from reading through the mailing list messages looks like it's gonna happen regardless of what I or other end users think.

    Leave a comment:


  • bug77
    replied
    Originally posted by johnc View Post
    There has to be a better reason than "it removes 30,000 lines of code".
    There is: this seems to be unused code/duplicated functionality.

    Leave a comment:


  • [Knuckles]
    replied
    From my experience using Xephyr and Xnest, most of them have little things broken everywhere.
    If they are not maintained and are untested, it's better to remove them than to leave users frustrated with crashes and other problems.

    Leave a comment:


  • curaga
    replied
    Well, Xfbdev hasn't been usable in several releases (they broke both keyboard and mouse in 1.3, IIRC). While I personally use many of the would-be-kicked and already-kicked servers, it's quite understandable when the people who use them (mainly embedded folks, with little to none X dev experience) aren't the people who maintain X.

    Leave a comment:


  • johnc
    replied
    There has to be a better reason than "it removes 30,000 lines of code".

    Leave a comment:

Working...
X