Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › echo "The `uname` Club" (NEW POLL)
New Posts  All Forums:Forum Nav:

echo "The `uname` Club" (NEW POLL) - Page 117

Poll Results: How long have you been using your current, main installation?

 
  • 24% (50)
    less then a month
  • 23% (47)
    less then six months
  • 14% (30)
    less then a year
  • 24% (49)
    less then three years
  • 13% (27)
    three years+
203 Total Votes  
post #1161 of 4043
Quote:
Originally Posted by Xaero252 View Post

The problem is that Xorg is too convoluted now. It's had thousands of hands with different creative direction stirring a giant bucket of code with little or no regard to previous standards or implied or required functionality. Couple that with the massive lack of organized documentation that is still relevant and you have a mess. I love Xorg to death, and I appreciate what the project has done for us. But I think its gotten quite archaic and its probably time to put the puppy down. That said however, I don't see why a revolutionary display system couldn't be legacy compatible with Xorg applications. The API isn't whats screwed up with Xorg, its the rest of it. You could leave Xorg API compatibility in place, and add/build around it to create something great. I doubt that's the direction Canonical went with it, and I doubt Wayland will ever get the support it needs anyway (sad, it looks like a great project)

To answer your first question - eventually. The second, maybe. By that I mean that sometimes there are really great things brought by change and new environments with new applications. And sometimes there are huge losses. For example, a game I helped develop relied heavily on FFMPEG's old API. This leads to a massive breakage when the API changed. The compiled program still works with new FFMPEG; however you can't build it with the new FFMPEG source, leading to a halt in development advancement since some of what we accomplished is no longer possible with the new API due to changes in how it works with other applications. Granted we will eventually work around this hurdle, but with a development staff of only 3, its kind of hard to make progress.

Oh the last part was a bit sarcastic. =P I should have been more clear. Though the Xorg info is nice! =) I don't get into the dev muck of stuff, I can fix things but I stay away from the dev crowd (though now would be a good time to know one for my DSDT idea). I didn't know people really say it's that bad, shame too.

I agree with the API part, keep the (thinking of word, hold on).... I'm too tired, we'll just stick with they should keep the API. lol
Current Rig
(14 items)
 
  
CPUMotherboardGraphicsRAM
FX-8350 4.6GHz@1.44v GA-990FXA-UD3 R4.0 HD 7950 (1100/1450) 8G Muskin DDR3 1866@8CLS 
Hard DriveOptical DriveOSMonitor
1TB WD LiteOn DVD-RW DL Linux/Windows 19" Phillips TV 1080p 
PowerCaseMouseMouse Pad
OCZ 600W Generic Junk Logitech MX400 Generic Junk 
Audio
SBL 5.1 
  hide details  
Reply
Current Rig
(14 items)
 
  
CPUMotherboardGraphicsRAM
FX-8350 4.6GHz@1.44v GA-990FXA-UD3 R4.0 HD 7950 (1100/1450) 8G Muskin DDR3 1866@8CLS 
Hard DriveOptical DriveOSMonitor
1TB WD LiteOn DVD-RW DL Linux/Windows 19" Phillips TV 1080p 
PowerCaseMouseMouse Pad
OCZ 600W Generic Junk Logitech MX400 Generic Junk 
Audio
SBL 5.1 
  hide details  
Reply
post #1162 of 4043
I'll quite happily see the back of xorg. I just don't want Canonical in charge of the new server either
post #1163 of 4043
I'll quite happily see the back of xorg. I just don't want Canonical in charge of the new server either
post #1164 of 4043
I'll quite happily see the back of xorg. I just don't want Canonical in charge of the new server either
post #1165 of 4043
OMG A triple! Nice. wink.gif I kid I kid! hehe
Current Rig
(14 items)
 
  
CPUMotherboardGraphicsRAM
FX-8350 4.6GHz@1.44v GA-990FXA-UD3 R4.0 HD 7950 (1100/1450) 8G Muskin DDR3 1866@8CLS 
Hard DriveOptical DriveOSMonitor
1TB WD LiteOn DVD-RW DL Linux/Windows 19" Phillips TV 1080p 
PowerCaseMouseMouse Pad
OCZ 600W Generic Junk Logitech MX400 Generic Junk 
Audio
SBL 5.1 
  hide details  
Reply
Current Rig
(14 items)
 
  
CPUMotherboardGraphicsRAM
FX-8350 4.6GHz@1.44v GA-990FXA-UD3 R4.0 HD 7950 (1100/1450) 8G Muskin DDR3 1866@8CLS 
Hard DriveOptical DriveOSMonitor
1TB WD LiteOn DVD-RW DL Linux/Windows 19" Phillips TV 1080p 
PowerCaseMouseMouse Pad
OCZ 600W Generic Junk Logitech MX400 Generic Junk 
Audio
SBL 5.1 
  hide details  
Reply
post #1166 of 4043
Thread Starter 
I agree with xaero- x11 is fine, xorg is unmaintainable. What they need is a new xserver, not a whole new uncompatible display system. (I understand wayland and mir plan on 'x plugins' or whatever, but since that's basiclly nested xorg... Not a real backwards compatible solutation.) At the same time, two projects is enough. We should, if we must write a new display system, all be working on wayland. Get gtk/qt working (I believe qt5 does but I'm not sure) port kwin/mutter or even just get gnome/kde working with weston. As long as weston isn't the only WM, for sake of compatibility with other POSIX OSes (pretty sure weston is Linux only for some reason)
post #1167 of 4043
Quote:
Originally Posted by mushroomboy View Post

OMG A triple! Nice. wink.gif I kid I kid! hehe

lol yeah. The battery died on my laptop right in the middle of a system update so I was forced to browser OCN on my tablet while I waited for an Arch ISO to download (couldn't even get past the boot menu, the crash was that badly timed!), and we all know how crappy Hudler's mobile site is mad.gif

It's all back up again now (I spent more time wrestling with a Windows laptop trying to get the ISO to burn than i did fixing Linux lol). Which reminds me, I really need to convert my / to Btrfs to make use of snapshotting....
Edited by Plan9 - 3/7/13 at 2:21pm
post #1168 of 4043
Quote:
Originally Posted by jrl1357 View Post

I agree with xaero- x11 is fine, xorg is unmaintainable. What they need is a new xserver, not a whole new uncompatible display system. (I understand wayland and mir plan on 'x plugins' or whatever, but since that's basiclly nested xorg... Not a real backwards compatible solutation.) At the same time, two projects is enough. We should, if we must write a new display system, all be working on wayland. Get gtk/qt working (I believe qt5 does but I'm not sure) port kwin/mutter or even just get gnome/kde working with weston. As long as weston isn't the only WM, for sake of compatibility with other POSIX OSes (pretty sure weston is Linux only for some reason)

The Wayland founder, Kristian Høgsberg, said that he first thought about upgrading X to do these new things, but apparently it's impossible to do in an elegant way. So he started from scratch, in order to make everything clean and correct. There's certainly no technical reason for Mir's existence though, it's just NIH syndrome.
post #1169 of 4043
Thread Starter 
^exactly. Well I don't agree with x not beig good enough (mainly because his main reason is better compositing at the cost of long time, functonal standard) at the very least if x needs to be replaced it should be by one thing, not two completely different things. Makes me wonder if ubuntu would still be working on wayland if the compiz dev hadn't stopped his porting effort. I think the android/gnu hybrid core (imcompatible with both gnu and android) will end up being in the desktop ubuntu (windows 8 syndrome of one half baked OS to rule them all) it might work for them, but I only see it going one of two ways: complete success or horrible failure. I'm rooting/expecting for the latter.
post #1170 of 4043
I hope Wayland wins. I hope Ubuntu fades away. For advanced distros, I choose Arch. For newbie-friendly distros, I choose OpenSUSE. For servers, we'll see when I finally get around to them. tongue.gif
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Linux, Unix
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Linux, Unix › echo "The `uname` Club" (NEW POLL)