An old growth forest tree is a tree growing in an old growth forest (which apparently largely refers to the forest having recovered from any human disturbance).
Seedlings in a box don't seem to be old growth trees.
Biometrics are terrible. You leave fingerprint everywhere, most fingerprint readers seem to be incredibly easy to bamboozle, it gives incentives to detach fingers, it is hard to get new fingerprints if you find out the ones you have are compromised, and on and on.
Now, for certain types of authentication they probably make a lot of sense, but not for medium value authentication across miscellaneous un-managed hardware.
If a bit of information exists in some database somewhere, it isn't private.
You could call it personally identifiable information though. If you are going to advocate for the children here, you might as well pick a framing that has the advantage of being accurate.
Of course, they aren't using it as a unique identifier, they are using it to reduce the number of collisions they have when considering just names and other info.
I'm trying to decide if you are just being snarky, or if you are being snarky to point the GP in this direction.
(I was going to make a snarky comment about how he must have used emphasis, because italics are broken, but no, it appears that he actually used i tags)
I'm sure I would hate it (and I usually do have quite some days of this or that dry food, it is easy to put the new stuff on the back of the shelf), but I'm also quite sure I would survive it, with basically zero issues.
More fun to be at least a little obtuse and explain that "no, I do not have a Facebook".
Re:Is the GIL removed from the interpreter
on
Python 3.2 Released
·
· Score: 1
Generators have been in the language since 2.3 or 2.4 (they were first supported in 2.2 but required activation there). Changing the standard library to return generators instead of lists basically guarantees that a user will trip over the problem outlined by GP, but naive use of a function like that is just as much a problem in the later 2.x releases.
It runs as a separate process from the windows shell there poindexter, so when you close it, the session really does go away.
Anyway, the way this technique works, once the session is successfully hijacked, even turning the computer off isn't going to help any.
Re:Another great Python 3.x series release
on
Python 3.2 Released
·
· Score: 1
Go Daddy? And you say this choice was based on some sort of investigation?
FWIW, I have no idea about Slicehost, but you were making claims about bargain hosting, so I didn't have any qualms about tossing out a name that may or may not be shitty.
The windows file extension thing is a little bit irritating, but I can't say I care that much about it. It is mostly a limitation of Windows that the Python developers chose not to work around (and it is easy to deal with for a few scripts running on one interpreter or the other, just creates shortcuts that explicitly launch the correct interpreter).
As far as the hosting thing, I doubt a new name would help on your search to find a host supporting a new language, outside of PHP, they don't work very hard at keeping stuff current, especially bargain hosts.
Re:Another great Python 3.x series release
on
Python 3.2 Released
·
· Score: 1
Order of magnitude? What's your price point for managed hosting? A cheap VM on something like Slicehost is $20 a month, and the situations where a managed server works and that doesn't are pretty limited.
Nevermind that lots of hosts won't pay much attention if you want to roll your own binaries.
The HDFury 2, mentioned in a recent Slashdot story, may solve your problem (it outputs on component and can downscale, you would have to convert the component output to composite).
Removing backtick support actually makes the language simpler.
(I realize that it does make simple shell access more complicated, by requiring that it be done with a library function (but removing syntax still simplifies the language))
Re:Another great Python 3.x series release
on
Python 3.2 Released
·
· Score: 1
If they had named it Bathiola, would you be complaining that the made it too similar to Python?
If Python 3 is a success in 2015 and Python 2 is largely dead, it will provide some amount of evidence that backwards compatibility does not need to be inviolate.
You should want it in the source material, even a cheap amp should be able to do high quality compression, letting you choose how much you get.
An old growth forest tree is a tree growing in an old growth forest (which apparently largely refers to the forest having recovered from any human disturbance).
Seedlings in a box don't seem to be old growth trees.
Biometrics are terrible. You leave fingerprint everywhere, most fingerprint readers seem to be incredibly easy to bamboozle, it gives incentives to detach fingers, it is hard to get new fingerprints if you find out the ones you have are compromised, and on and on.
Now, for certain types of authentication they probably make a lot of sense, but not for medium value authentication across miscellaneous un-managed hardware.
The people doing this were bureaucrats in a department of a small state. If they are the ruling class, so is half of everybody else.
If it is stored in some database somewhere, it isn't private information.
Names and SSNs are personally identifiable information, if you want to advocate about it, you should choose a framing that is accurate.
Names and SSNs are not private information.
If a bit of information exists in some database somewhere, it isn't private.
You could call it personally identifiable information though. If you are going to advocate for the children here, you might as well pick a framing that has the advantage of being accurate.
Of course, they aren't using it as a unique identifier, they are using it to reduce the number of collisions they have when considering just names and other info.
I'm trying to decide if you are just being snarky, or if you are being snarky to point the GP in this direction.
Your conspiracy makes no sense. The SSA already has a database matching SSNs to names and birth locations.
Hey, they fixed the italics bug.
(I was going to make a snarky comment about how he must have used emphasis, because italics are broken, but no, it appears that he actually used i tags)
I'm sure I would hate it (and I usually do have quite some days of this or that dry food, it is easy to put the new stuff on the back of the shelf), but I'm also quite sure I would survive it, with basically zero issues.
Why is 2 weeks the magic number?
Hell, if you are mostly healthy and have access to water, 5 or 6 days without food is barely dangerous, probably mostly uncomfortable.
More fun to be at least a little obtuse and explain that "no, I do not have a Facebook".
Generators have been in the language since 2.3 or 2.4 (they were first supported in 2.2 but required activation there). Changing the standard library to return generators instead of lists basically guarantees that a user will trip over the problem outlined by GP, but naive use of a function like that is just as much a problem in the later 2.x releases.
It is transmitting the session information to a server.
It runs as a separate process from the windows shell there poindexter, so when you close it, the session really does go away.
Anyway, the way this technique works, once the session is successfully hijacked, even turning the computer off isn't going to help any.
Go Daddy? And you say this choice was based on some sort of investigation?
FWIW, I have no idea about Slicehost, but you were making claims about bargain hosting, so I didn't have any qualms about tossing out a name that may or may not be shitty.
Yeah, I got it, I move mine around/use it as a laptop too, I was just pointing out that at least 1 manufacturer does whine about it.
It seems like being reluctant to reboot is just another type of broken.
The manual for mine says not to move it around while powered up (Lenovo).
The windows file extension thing is a little bit irritating, but I can't say I care that much about it. It is mostly a limitation of Windows that the Python developers chose not to work around (and it is easy to deal with for a few scripts running on one interpreter or the other, just creates shortcuts that explicitly launch the correct interpreter).
As far as the hosting thing, I doubt a new name would help on your search to find a host supporting a new language, outside of PHP, they don't work very hard at keeping stuff current, especially bargain hosts.
Order of magnitude? What's your price point for managed hosting? A cheap VM on something like Slicehost is $20 a month, and the situations where a managed server works and that doesn't are pretty limited.
Nevermind that lots of hosts won't pay much attention if you want to roll your own binaries.
Stable across point releases. So C libraries compiled against the stable ABI should work with Python 3.2 or 3.3 or 3.4.
At the moment, libraries need to be compiled for each point release of Python (so 2.4, 2.5, 2.6, 2.7, etc).
The HDFury 2, mentioned in a recent Slashdot story, may solve your problem (it outputs on component and can downscale, you would have to convert the component output to composite).
Removing backtick support actually makes the language simpler.
(I realize that it does make simple shell access more complicated, by requiring that it be done with a library function (but removing syntax still simplifies the language))
If they had named it Bathiola, would you be complaining that the made it too similar to Python?
If Python 3 is a success in 2015 and Python 2 is largely dead, it will provide some amount of evidence that backwards compatibility does not need to be inviolate.