Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×
Software Open Source

Wayland 1.5 Released 179

An anonymous reader writes "Wayland 1.5 has been released, along with Weston Compositor 1.5. Wayland/Weston 1.5 carry many new user features, with a new libinput back-end, XWayland support, a full-screen shell, and many other changes. This release is particularly important as Fedora 21 will run on GNOME Wayland and X.Org Server 1.16 will be released this summer with integrated XWayland support."
This discussion has been archived. No new comments can be posted.

Wayland 1.5 Released

Comments Filter:
  • by bluegutang ( 2814641 ) on Wednesday May 21, 2014 @03:18AM (#47054217)

    Anyhow. Now you know. If I'm wrong get a refund.

    While I think Wayland remote display will end up working just fine, "get a refund" is exactly the wrong attitude, and one that is doing a great deal to hold back open source. Don't like your Firefox buttons switching places every two weeks? Get a refund. Unity's window management for retards driving you up a wall? Get a refund. Newest GNOME version missing half the features you depend on? Get a refund. Guess what? Nobody is going to ask for a refund. They are going to switch to a different piece of software. And if every open source application has been trashed by developers, they'll switch to closed source.

  • by dbIII ( 701233 ) on Wednesday May 21, 2014 @05:46AM (#47054605)

    Basically all that. Even over GigE simple things like gvim are a dog.

    To me that sounds like complete and utter bullshit unless gvim is now seriously broken. In my workplace complex interactive geophysical packages with a lot of graphical information are used remotely over X by dozens of people at once to (in some cases) substandard MS Windows implementations of X without running like a dog - even over wireless to laptops, so how is your gvim over GigE example even possible unless somethign else is going on? It appears to fail the reality test. Did you make it up or was the machine you were running it on under very heavy load at the time so it would be slow in all cases? If you made it up - why - what is motivating you to make such things up about what you see as opposition instead of praising what you see as good in Wayland? This X sux rubbish that fails the reality test is annoying and doesn't do Wayland any good while Wayland is still making progress.

  • by Beck_Neard ( 3612467 ) on Wednesday May 21, 2014 @05:48AM (#47054611)

    I've built a few open source projects and been heavily criticized for my design choices but you know what? I agree with this. A lot of developers are too stubborn to make changes and it drives people away then they wonder why no one is using their project anymore.

    But the flipside is true too. A lot of the time 'flaws' are actually sober and sane design choices which you have to get into the internals of the system to understand. People often don't get this and then bitch and moan about why something hasn't been done the way they like.

    The Wayland devs seem pretty sober and sane so far, and I think they've made a lot of nice design choices. The problem of displaying graphics on a PC is an inherently ugly problem (and X is an ugly piece of software which visibly reflects that). If they can make it just a little bit better, it will be worth the wait, in my opinion.

  • No GTK2 (Score:4, Interesting)

    by Blaskowicz ( 634489 ) on Wednesday May 21, 2014 @07:02AM (#47054833)

    That's nice but what you describe is for GTK3, and not GTK2. Seems like the latter is still used a lot, and frankly GTK3 has gone rogue, deleting features, adding ones only Gnome developers will use etc.
    Developers of applications run away from it and migrations from GTK2 to GTK3 seldom made (though there are dual mode GTK2/GTK3 applications where you can select the UI).

    Recently with GTK 3.10 they removed icons in menus and the highlighting of letters to help you with keyboard navigation (e.g. Alt-F opens File menu). It's the Slashdot Beta of the toolkit world.

Any circuit design must contain at least one part which is obsolete, two parts which are unobtainable, and three parts which are still under development.

Working...