You do know that OpenGL debuted as a feature of X11, right, you know waaay back in 1993? And you don't even know what you mean when you say "the X stack gets out of the way".
I'm well aware of that. Why do you think everyone uses DRI which bypasses X and not indirect rendering for gl which goes through X.
I quote the parent I was replying to... oh wait that's you
Applications are expected to render to their own buffers using something like DRI, which is PRECISELY the same as they use under X11 too if running locally.
Ivanka, President Trump's eldest daughter, was born in the United States (in New York)
I know damn good and well who she is. I also remember the big hoopla when he and Ivana (her mother) came back from their trip to eastern europe and announced she was born overseas. Ergo Ivanka was not born on US soil and is not eligible to be president.
And by "work properly" you mean back track an architectural choice that has been pushed for security reasons for the past 3 years.
It's a work around for shitty apps from people stuck in the old ways or that just haven't been updated yet.
Man if you people were around when sudo was adopted you'd still be suggesting everyone log in as root.
It's pretty funny you say that since the whole thread got started by a guy with just that attitude. The people pushing wayland are saying "hey, check it out polkit is better than sudo"
I know of that workaround, but it is all it is, a workaround.
Typically for legacy apps one uses workarounds.
And it won't work for native apps,only for X apps.
You're absolutely right, it only works for poorly designed apps. Properly designed apps use polkit and the workaround isn't needed. So whats your complaint?
No it isn't: X has supported hardware acceleration from the earliest days and continues to do so. See, for example GlamourGL, in which Xorg uses OpenGL shaders to do all the 2D drawing operations.
There's a reason that any serious graphics rendering under Xorg uses DRI. It's because DRI bypasses most of the X stack.
No, that's utter crap. Wayland doesn't do that AT ALL. Wayland is basically a system for sending bitmapts to a compositor and have the compositor send back input. Wayland provides very little else and certainly no rendering.
So what you're saying is wayland gets the cpu out of the way so applications can render on the graphics card more efficiently? wow why didn't I think to say that?
Applications are expected to render to their own buffers using something like DRI, which is PRECISELY the same as they use under X11 too if running locally.
So what you're saying is all that Xorg nonsense just bogs it down and anything rendering 3d any serious graphics is just going to do direct rendering like wayland prefers anyway? holy shit I wish I had thought to say that... oh wait I did.
Really screwed up installing 17.10. Should have stuck to LTS.
Absolutely. If you aren't willing to reinstall on a regular basis then always stick with LTS releases. Upgrading every time theres a new Ubuntu release gives you the latest and greatest, but lots of stuff will be broken.
The X Server stack was fast enough back in the days of the FOUR-EIGHTY-SIX.
Because back in the days of the "FOUR-EIGHTY-SIX" your cpu was generally faster than your graphics card. Nowadays your graphics card is so much faster than your cpu the X stack leaves your graphics rendering waiting on the CPU. So Wayland is an attempt (successful or not is an entirely different discussion) to get the cpu out of the way for your graphics card to work more efficiently.
No, this was a regulatory decision by the FCC, not an executive order.
No legal basis for them to challenge
Weirdly enough the courts have decided otherwise in previous court cases.
All Trump did was revert back to the pre-2015 "bad days" of no net neutrality. Oh, it was so much worse back then, just a couple of years ago!
Actually before 2014 or so there was net neutrality. The courts killed the existing rules in verizon v fcc and explicitly told the fcc that they had to regulate internet providers under title II. So no, before 2015 we had net neutrality and after 2015 we had net neutrality. We're now back to that one year where we didn't have it
nope, google home, and chromecast use multicastDNS like apple bojour to locate devices on the same access point.
Nope, as long as they're on the same layer 2 network they communicate fine.
a quiet side effect is chromecasts, don't work well in multi wireless access point networks. (ie a computer connecting to you AP can't reach devices connected to another AP)
What? I have 4 access points and it doesn't matter which one I'm on I can connect to the chromecasts fine, I even have multiple ssids (to manage bandwidth restrictions for guests), Doesn't matter which AP or SSID, all chromecasts work.
The hub is a bit more novel than just a software repository. It handles building your software as well as the layer bits to where you only download what is changed from the parent images.
In dockers case the docker hub (and registry) are pretty novel. I personally don't think its novel enough for a patent but dumber shit has been patented in the past.
Properly implemented they have no way of telling if its a bunch of real devices, a bunch of phantom devices, or a single device. Everyones network looks the same, constantly changing suffices
The repeal only restored previous legislation, you know where communications providers were common carriers and couldnâ(TM)t screw with connections at all or couldnâ(TM)t reform into a monopoly.
Uh the 2015 ruling that they repealed was to apply Title II regulation to the isps for the first time, for those who aren't particularily well versed in fcc regulations, Title II is common carrier status. The FCC repealed Common carrier status, so ISPS are no longer common carriers.
No, the scandal is that the FCC under Obama put an executive policy into place that was directly at odds with the specific wishes of congress.
What? Why did they pass the telecommunications act of 1996 that explicitly empowers the FCC to enact network neutrality then?
Undoing that Obama admin fiat is putting things back into line with the law. I suppose you were also complaining when NN was put into place, for the same reasons? No? Gotcha.
But the law explicitly empowers the fcc to enact network neutrality, undoing the ruling doesn't put things back in line with the law, in fact the courts are saying that title ii regulation is the only way forward while the FCC is claiming its the FTCs job. This is an attempt by the FCC to get out of following the law as congress specifically enacted it.
> Except that congress stated explicitly that the internet not be regulated, and ditching NN brings the FCC in line with what congress wanted.
When did they? and if so why don't they repeal the telecom act empowering the FCC to enact title II common carrier status? and why is the DMCA still in place if they want the internet to not be regulated? and why is the FCC claiming congress wants the internet regulated by the FTC?
Many don't even read the title of the post, they just sort of get a feel for what the article is about and then kneejerk from there. I'm looking at a front page post on reddit right now where the top rated comment is just that, he even uses a quote from the article but he clearly didn't comprehend the article at all.
The "I" circle vs the green lock indicates it is not an EV cert, and is typically how an HTTPS site looks when accepting your own certificate signed by another key you made your browser trust.
Slashdot Mirror
By serious graphics, you mean OpenGL?
You do know that OpenGL debuted as a feature of X11, right, you know waaay back in 1993? And you don't even know what you mean when you say "the X stack gets out of the way".
I'm well aware of that. Why do you think everyone uses DRI which bypasses X and not indirect rendering for gl which goes through X.
No, look, put up or shut up.
I quote the parent I was replying to... oh wait that's you
Applications are expected to render to their own buffers using something like DRI, which is PRECISELY the same as they use under X11 too if running locally.
DRI Bypasses X.org. Why do you think that is?
Ivanka, President Trump's eldest daughter, was born in the United States (in New York)
I know damn good and well who she is. I also remember the big hoopla when he and Ivana (her mother) came back from their trip to eastern europe and announced she was born overseas. Ergo Ivanka was not born on US soil and is not eligible to be president.
And by "work properly" you mean back track an architectural choice that has been pushed for security reasons for the past 3 years.
It's a work around for shitty apps from people stuck in the old ways or that just haven't been updated yet.
Man if you people were around when sudo was adopted you'd still be suggesting everyone log in as root.
It's pretty funny you say that since the whole thread got started by a guy with just that attitude. The people pushing wayland are saying "hey, check it out polkit is better than sudo"
I know of that workaround, but it is all it is, a workaround.
Typically for legacy apps one uses workarounds.
And it won't work for native apps,only for X apps.
You're absolutely right, it only works for poorly designed apps. Properly designed apps use polkit and the workaround isn't needed. So whats your complaint?
So all you needed to get Wayland to work properly was... X.
I mean at this point pretty much all of the wayland apps are already using X
No it isn't: X has supported hardware acceleration from the earliest days and continues to do so. See, for example GlamourGL, in which Xorg uses OpenGL shaders to do all the 2D drawing operations.
There's a reason that any serious graphics rendering under Xorg uses DRI. It's because DRI bypasses most of the X stack.
No, that's utter crap. Wayland doesn't do that AT ALL. Wayland is basically a system for sending bitmapts to a compositor and have the compositor send back input. Wayland provides very little else and certainly no rendering.
So what you're saying is wayland gets the cpu out of the way so applications can render on the graphics card more efficiently? wow why didn't I think to say that?
Applications are expected to render to their own buffers using something like DRI, which is PRECISELY the same as they use under X11 too if running locally.
So what you're saying is all that Xorg nonsense just bogs it down and anything rendering 3d any serious graphics is just going to do direct rendering like wayland prefers anyway? holy shit I wish I had thought to say that... oh wait I did.
Really screwed up installing 17.10. Should have stuck to LTS.
Absolutely. If you aren't willing to reinstall on a regular basis then always stick with LTS releases. Upgrading every time theres a new Ubuntu release gives you the latest and greatest, but lots of stuff will be broken.
The X Server stack was fast enough back in the days of the FOUR-EIGHTY-SIX.
Because back in the days of the "FOUR-EIGHTY-SIX" your cpu was generally faster than your graphics card. Nowadays your graphics card is so much faster than your cpu the X stack leaves your graphics rendering waiting on the CPU. So Wayland is an attempt (successful or not is an entirely different discussion) to get the cpu out of the way for your graphics card to work more efficiently.
Or like being incapable of running GUI apps as root - which breaks among others gparted,
I literally ran gparted a few days ago under wayland. It was a minor pita but it is very doable.
http://ubuntuhandbook.org/index.php/2017/10/ubuntu-17-10-tip-graphical-apps-doesnt-launch-via-root-sudo-gksu//
xhost si:localuser:root
was all I meeded
This was an executive order, rules change only.
No, this was a regulatory decision by the FCC, not an executive order.
No legal basis for them to challenge
Weirdly enough the courts have decided otherwise in previous court cases.
All Trump did was revert back to the pre-2015 "bad days" of no net neutrality. Oh, it was so much worse back then, just a couple of years ago!
Actually before 2014 or so there was net neutrality. The courts killed the existing rules in verizon v fcc and explicitly told the fcc that they had to regulate internet providers under title II. So no, before 2015 we had net neutrality and after 2015 we had net neutrality. We're now back to that one year where we didn't have it
I wasn't calling you a troll, i was saying the guy you were replying to was a troll.
Two things, A) he's obviously a troll B) out of all 4 of those only vlc is desktop software
nope, google home, and chromecast use multicastDNS like apple bojour to locate devices on the same access point.
Nope, as long as they're on the same layer 2 network they communicate fine.
a quiet side effect is chromecasts, don't work well in multi wireless access point networks. (ie a computer connecting to you AP can't reach devices connected to another AP)
What? I have 4 access points and it doesn't matter which one I'm on I can connect to the chromecasts fine, I even have multiple ssids (to manage bandwidth restrictions for guests), Doesn't matter which AP or SSID, all chromecasts work.
The hub is a bit more novel than just a software repository. It handles building your software as well as the layer bits to where you only download what is changed from the parent images.
What invention?
In dockers case the docker hub (and registry) are pretty novel. I personally don't think its novel enough for a patent but dumber shit has been patented in the past.
Properly implemented they have no way of telling if its a bunch of real devices, a bunch of phantom devices, or a single device. Everyones network looks the same, constantly changing suffices
The repeal only restored previous legislation, you know where communications providers were common carriers and couldnâ(TM)t screw with connections at all or couldnâ(TM)t reform into a monopoly.
Uh the 2015 ruling that they repealed was to apply Title II regulation to the isps for the first time, for those who aren't particularily well versed in fcc regulations, Title II is common carrier status. The FCC repealed Common carrier status, so ISPS are no longer common carriers.
No, the scandal is that the FCC under Obama put an executive policy into place that was directly at odds with the specific wishes of congress.
What? Why did they pass the telecommunications act of 1996 that explicitly empowers the FCC to enact network neutrality then?
Undoing that Obama admin fiat is putting things back into line with the law. I suppose you were also complaining when NN was put into place, for the same reasons? No? Gotcha.
But the law explicitly empowers the fcc to enact network neutrality, undoing the ruling doesn't put things back in line with the law, in fact the courts are saying that title ii regulation is the only way forward while the FCC is claiming its the FTCs job. This is an attempt by the FCC to get out of following the law as congress specifically enacted it.
> Except that congress stated explicitly that the internet not be regulated, and ditching NN brings the FCC in line with what congress wanted.
When did they? and if so why don't they repeal the telecom act empowering the FCC to enact title II common carrier status? and why is the DMCA still in place if they want the internet to not be regulated? and why is the FCC claiming congress wants the internet regulated by the FTC?
Many don't even read the title of the post, they just sort of get a feel for what the article is about and then kneejerk from there. I'm looking at a front page post on reddit right now where the top rated comment is just that, he even uses a quote from the article but he clearly didn't comprehend the article at all.
Hey meant web browser usage is supposed to be fragmented, not standards usage.
Android doesn't run it's apps on a java interpreter.
Hell for that matter apple compiles its apps on llvm, guess what android compiles its apps on nowadays... llvm
The problem with that theory is they will unlock the extra capacity if you pay them.
The "I" circle vs the green lock indicates it is not an EV cert, and is typically how an HTTPS site looks when accepting your own certificate signed by another key you made your browser trust.
Google says you're wrong.
https://support.google.com/chrome/answer/95617?hl=en/