"Jobwashing" - Similar to "greenwashing" but updated for the present era.
"Jobwashing" - Similar to "greenwashing" but updated for the present era.
Sorry, no. They broke strings entirely in Python 3.0 and that is why people cannot port to them.
Here is how to do strings correctly: use UTF-8 and DO NOT BARF ON ENCODING ERRORS!
It is absolutely 100% a requirement that a program be able to read a random byte stream into a "string", then write it out again, and get the same byte stream.
In Python 2.0 this only barfed if you tried to convert that string to "Unicode" (it would have been nice if it did not barf, but at least you could store, read, and write strings).
In Python 3.0 it will BARF ON READ. This makes it impossible to write reliable software.
Yes you can use "bytes" in Python 3.0. But that really sucks if in fact you expect your bytes to be readable text, with only RARE (but not magically non-existent) errors.
SevenEves would have been better if it was half as long. Stephenson is a great writer, though, and I understand if he can't help himself on that!
I agree than Anathem was incredibly good. A long book that you should really read twice to get everything.
It's satire, stupid
I work for Dolby Laboratories, and am deeply involved with high-dynamic-range content creation and hardware.
We created the SMPTE 2084 standard HDR EOTF (electro-optical transfer function.) It turns out that human perception is such that by choosing the luminance for code values to be just barely indistinguishable from the adjacent ones, you can get 0 to 10,000 nits (10x as bright as this Panasonic display) with only 12 bits. SMPTE 2084 is what all HDR TVs are using today.
Actually this won't fix X11 applications running on Wayland, as they are just using X11 api which lacks any "I understood the resolution" call.
Wayland does in fact have support for resolution independence. By this I mean that if a program does nothing about the resolution of the screen, Wayland assumes it is drawing for approximately 100 dpi, and scales the image by 2 if the screen is 200dpi. I think it only does integer scaling but it may be up to the compositor implementation.
If a program actually claims it's drawing for the high-resolution display, then Wayland does not scale. The problem with X (and I think with Windows) was that there was no api so a program could tell the system that it is handling the high resolution, so the compositor had to assume it was.
So some Uber rides will cost 50 cents more because the driver is doing this? I don't think so. This will come out of the drivers income. Don't be naive.
Honestly the changes in Python 3 should not be any obstacle to porting code. Most of it winds up being a find and replace. The major difference is the use of unicode, and if your package really depends heavily on strings not being unicode, you probably did it wrong. The problem is that if one package that lots of people depend on has devs that just say, "I don't wanna," everything breaks down. And more than one package has devs like that.
At this point, if the Python community could make "porting" as simple as adding a header to a
The problem with Python 3 "unicode" is not that text is not Unicode. The problem is that *random binary data* is not Unicode, but when you read data from an unknown source, you MUST assume it is "random binary data". Trusting it to follow some pattern is by far the stupidest thing you can do.
In Python 2 you could put random binary data into a "string" and then write it to disk without any change, and no errors would be produced. Only if you tried to *display* the string would you get an exception. In Python 3 it will immediately throw an exception, at a completely useless point in your program (ie when you are reading data in, not when you are processing it). Changing every "string" to a "bytes" will "fix" it, but then you have to change the type of every single function that is called from "string" to "bytes", and so on, eventually replacing every single "string" in your program with "bytes". And you are out of luck if one of those api's is from a library that you don't control.
Python 3 will NEVER get accepted unless you can put totally arbitrary patterns of 8-bit data into a "string" and get them back out unchanged. All exceptions must be deferred until something actually tries to split the data into Unicode code points. Even then they should be providing a more useful iterator based api that returns an object that says "the code point is this" or "there is a UTF-8 parsing error here and the first byte is this".
An annual cost of $230 is about $20/month. I am paying that for one HD DVR from Frontier. So I think this average certainly is from single boxes.
I don't know if you are trying to make a joke, but global warming is not going to do too much to the earthquakes. Greenland is already rising steadily due to the loss of the glaciers from the last ice age. It is really slow and will still happen for tens of thousands of years. Even if all the current ice cap disappeared tomorrow it would, at best, speed this up a tiny amount (the current ice cap is a fraction of the ice age ice cap so the amount of lost mass is only a small change). The weight of the new ice added to the ocean is insignificant (if it raised the ocean 30 feet that would still only be a tiny fraction of mass increase, think about how deep the ocean is).
When I was shooting Fast and Furious: Tokyo Drift in Tokyo, in winter of 2005, I saw a rig a lot like this. I was walking down a street, and saw a van with four cameras, four LIDARs, and two GPS sensors on the top. I asked a man working on it what it was, and he said "Oh! Are you engineer?" and I confessed that I was just a movie-maker. But, nevertheless, they showed me everything in the van, and said that the point was developing 3D models of all the streets in Tokyo. At the time, it wasn't for self-driving cars though -- they wanted to build 3D in-car maps for navigation. The team of engineers was from a university in Tokyo; although I don't recall which one.
While in the past, I agree that people were correct to hold the government accountable for this kind of surveillance, it isn't the biggest issue today. Huge amounts of information are gathered by companies about everybody on the 'net, and shared between them without any limitations. You don't want the government to see your email? Ok, fine -- but Google's incredibly powerful AI team doesn't just see your email -- it *understands* your email. Google can, and does, use that knowledge in any number of ways; and ways that will get more diverse (and perverse?) in the future.
In the not too distant future, I believe that companies like Google and Facebook will become more politically powerful than 99% of the governments in the world. Facebook was going to launch a satellite today to allow everybody in Africa to use Facebook; although somehow the rocket that was going to launch that satellite blew up. My belief is that Facebook wants to get information about everybody on the planet, and will do whatever it takes to do that.
Governments? Come on, that's not the threat.
My believe is that they intend to fly hundreds of these. If you have 100 tethers from 0 to 60,000 ft or so, I believe that you would have many aircraft accidents. Recall that the British used tethered balloons to protect themselves from German air raids. There is no way that you could see those tethers while flying, until you were very close to them -- then it would be too late to avoid.
There are a dozen or so tethered balloons around the border of the US now, so far there have been no incidents that I know of -- but the border is a place where pilots are very observant. Also, the balloons are only at about 10,000 ft or so, so most planes are far higher.
You can't change the angle at which the scene is rendered by interpolating between frames.
It's not the raw framerate. It's that the scene your viewing has to match where you're looking that quickly or you get motion sick.
While the parent is Anonymous coward, please rate him up, as that is correct.
"There... I've run rings 'round you logically" -- Monty Python's Flying Circus