Page 12 of 12 FirstFirst ... 2101112
Results 111 to 117 of 117

Thread: Upstream X/Wayland Developers Bash Canonical, Mir

  1. #111
    Join Date
    Sep 2010
    Posts
    229

    Default

    Quote Originally Posted by Hamish Wilson View Post
    By the way, Ubuntu officially package Gambas3 yet (sorry, just took a little frustrated jab)
    http://packages.ubuntu.com/gambas3

  2. #112
    Join Date
    Feb 2013
    Posts
    38

    Default

    Quote Originally Posted by TheBlackCat View Post
    <...>If mir devs didn't want to get in a fight with wayland devs, they shouldn't have picked a fight with them in the first place.
    i remember the "Mir Spec" page reading "why didnt we consider wayland? because <....> not meet our requirements" - which hardly sounds like picking a fight to me
    instead it sounds like a perfectly good (at least civil) rationale for explaining their decision (apart from the fact that they weren't even obliged to write such a "disclaimer" - which may even make it a sign of goodwill on their part)
    but those who called developers names for "not having done research", aren't picking up a fight are they?

    the mir spec page may contain inaccuracies (like that wayland's input model is similar to that of X), yes
    but are you seriously blaming them, with wayland's freedesktop.org website (the official and only credited source *) describing wayland's revolutionary approach (that of merging the display server and the compositor while generating surfaces client side, oh wow) and very little else?
    with the need to dwelve in the wayland-devel mailing list for the implementation details and design processes?
    with the need, if you're new, to read 4+ years worth of it to reconstruct its evolution from a simple redraw loop to its current state (which even now has things to settle)?
    with Xinput2 actually mentioned somewhere as a weston dependency IIRC, because "lets reuse what works"?

    * or are you telling one should really dwelve in 4+ years of stuff, scattered among mailing list, phoronix articles, obscure external blogs, to cobble together knowledge about the project named after Aliens' megacorp? seriously?
    that's not how a professional would work, for a professional developer only official reference material (possibly books) counts, the rest is fluff
    You can't go around bashing other development projects then get all offended when they dare to respond to your bashing.
    looks like my definition of bashing and your definition of bashing are quite divergent...
    also, consider that there is a thing called ovverreaction - which sometimes may trigger escalation, but usually leaves the one who overreacts less worthy of respect and consideration afterwards, when things have calmed down again...

  3. #113
    Join Date
    Feb 2013
    Posts
    38

    Default

    Quote Originally Posted by TheBlackCat View Post
    If mir devs didn't want to get in a fight with wayland devs, they shouldn't have picked a fight with them in the first place.
    i remember the "Mir Spec" page reading "why didnt we consider wayland? because <....> not meet our requirements"
    which hardly sounds like picking a fight to me... instead it sounds like a perfectly good (at least civil) rationale for explaining their decision
    disregarding the fact that they weren't even obliged to write such a "disclaimer" in the first place, so it may even be considered a sign of good will on their part
    but those who called developers names for "not having done research", aren't picking up a fight, are they?

    now, the mir spec page may contain inaccuracies (like that wayland's input model is similar to that of X), yes
    but are you seriously blaming them, with wayland's freedesktop.org website (the official and only credited source *) describing wayland's revolutionary (in world encumbered by 30 years of X, for sure) approach (of merging the display server and the compositor while generating surfaces client side, oh wow) and very little else?
    with the need to dwelve in the wayland-devel mailing list for implementation details and design processes (if we call debates about this or that function, as such)?
    with the need, if you're new, to read 4+ years worth of it to reconstruct its evolution from a simple redraw loop to its current state (with things to settle and standardise even now)?
    with Xinput2 IIRC actually mentioned somewhere as a weston dependency, because "lets reuse what works"?

    * or are you telling one should really dwelve in 4+ years of stuff, scattered among mailing list, phoronix articles, obscure external blogs, to cobble together knowledge about the project named after Aliens' megacorp? seriously?
    that's not how a professional would work, for a professional developer only official reference material (possibly books) counts, the rest is fluff

    You can't go around bashing other development projects then get all offended when they dare to respond to your bashing.
    looks like my definition of bashing and your definition of bashing are quite divergent
    also consider that there is a thing called ovverreaction - which sometimes may trigger escalation, but usually leaves the one who overreacts less worthy of respect and consideration afterwards, when things have calmed down again...
    Last edited by silix; 03-09-2013 at 10:30 AM.

  4. #114
    Join Date
    Oct 2011
    Location
    Rural Alberta, Canada
    Posts
    1,017

    Default

    Quote Originally Posted by JanC View Post
    Ancient as hell...

  5. #115
    Join Date
    Oct 2011
    Location
    Rural Alberta, Canada
    Posts
    1,017

    Default

    Quote Originally Posted by silix View Post
    Snip
    I think the idea is they could, as an interested vendor, have asked the Wayland developers for that information (not having to go trawling though old posts). And it was more than just a few inaccuracies, but damn right lies on that page. Whether or they were intentional I do not know, but it is more than enough to justify getting your hackles up.

  6. #116
    Join Date
    Nov 2011
    Posts
    270

    Default

    Quote Originally Posted by pingufunkybeat View Post
    Ryao, what happened to eudev?
    Look at systemd 197 changelog under contributions.

  7. #117
    Join Date
    Jun 2013
    Posts
    1

    Default

    Quote Originally Posted by Pawlerson View Post
    And gnome developers don't suffer from the NIH syndrome? Unity for example, was available before gnome shell.
    Um, no. You have that backwards.

    First commit to gnome-shell repository: 2008-10-31 04:22:44 UTC

    First commit to Unity repository: 2009-10-15 10:40:35 UTC

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •