And the error imparts no meaning on what the error was. You can print it out as a string, but if you have code that actually needs to see the error, the generic error must be cast into the explicit type to get at the value. It's very clumsy.
This was improved as of golang 1.13 with is and as.
by the time the customer realises they've been conned and contacts the bank, the bank can only explain that it's impossible to conduct a charge-back more than thirty days after the payment.
For defective or not as described items you get 120 days, not 30 days
The truth is, except for maybe state level hackers, it's not worth the trouble to scan IPv6 when IPv4 is so rich with weak targets.
The entirety of ipv4 address space (including the reserved space for things like rfc1918) is 1/4294967296th the space a single end user gets with ipv6. It would take over 4 billion times the probe attempts to scan a single end point as it would take to scan the entirety of the ipv4 address space. ipv6 doesnt get scanned because the math to do it just doesnt work out.
MAC addresses are supposed to be hard-coded : first 3 octets are manufacturer ID, last 3 octets are device ID. Programmable MAC addresses have always been a hack - mostly useful to spoof another machine and bypass MAC-based security or get a fixed IP from a DHCP server that's meant to be doled out to another machine.
The problem with that theory is there is such a thing as a locally administered MAC address akin to rfc1918 but for MAC addresses and is a perfectly legitimate use case for alterable MAC addresses.
Just FYI apple just deprecated print drivers in the latest CUPS and will remove support at some unannounced point in the future. The only printers that will be able to print from apple computers are ones that implement Bonjour/IPPE
The claim was that Uber is an app company because you cant pay them without the app... that means mcdonalds is a cash register company since i cant pay them unless they have a cash register.
Is mcdonalds a cash register company?
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.
Enzymes are things invented by biologists that explain things which otherwise require harder thinking. -- Jerome Lettvin
