Maybe you should have removed your ram-leaking extensions. Once I did that with 2.0 and on, most of the RAM issues went away. Pretty sure mozilla had a blog titled something like "stop blaming us for your crappy, bug-ridden extensions" around 3.0.
"Translate these numbers, which are written in base seven, to base five." Translating from one base to another is an utterly useless thing. If you can do it, maybe it's entertaining; if you can't do it, forget it. There's no point to it.
Being able to translate from decimal to hex and binary is quite useful, and at times necessary. Imagine trying to subnet with no conception as to how bases work? Imagine being introduced to this thing called "binary" in intro to IT without actually understanding how an alternate base works?
It also helps teach you how to think, in a more general sense; numbers arent these absolute things, but representations of value in an arbitrary system that can be represented differently (base 10, base 2, as a fraction, as a decimal, etc etc).
But question, assuming you are doing something like "exec(pdfparse($input))", and you dont sanitize your data, whats to stop someone from specifying the pdf file "somefile.pdf);rm -rf" as the file?
The hashes should be salted, but Im not sure what to make of the accusation that the network protocols send hashes for authentication. What would you rather have them send? The plaintext password?
Regardless, AD login uses Kerberos AFAIK.
Again, no excuse for not using a salt, Im not really clear why they dont do that.
32/64 issues - on linux you can choose between a 32, hybrid 32/64 or pure 64bit system as your needs dictate, with windows its necessary to have the 32bit libraries present wether you intend to use them or not, which makes it cruft.
I believe you can remove WindowsOnWindows if you dont need 32-bit compatibility on the server. That may only be for the upcoming version, I cannot find the reference at the moment.
"File and Registry Virtualization" is a lot more than symlinks, it is more of an overlay filesystem more similar to unionfs if you're familiar with that.
Ive heard that language used, but it depends what youre talking about. If I go into my home directory and issue "dir/a:hs", i get back a number of those "virtualized" folders, which are actually reported as junction points (aka, directory links). Thats for compatibility with the older locations used on prior versions of windows. Ditto with Documents and Settings: it is junctioned to the Users folder.
For 32/64 compatibility, yes, I think you are correct, as a 32-bit process cannot (IIRC) access the 64-bit nodes.
On the other hand it is extremely rare that links would be used for this kind of compatibility kludge.
I cannot give examples offhand, but I have run into it before where a new version doesnt stick a file in the old location, and so it is necessary to link the file to its old location so that things "just work".
Linking a file to multiple locations is a different use case, and is also done for efficiency rather than having multiple copies of the same file.
If you dont use links, you can end up with multiple different versions, causing inconsistent behavior or worse. Links make sure that doesnt happen.
Any ways, presumably at some point, like Rosetta, the FS / registry virtualization will be dropped;
I dont totally disagree with you, and you make some good points; I DO disagree that the handling of the changed folder locations and the 64/32 interoperability fixes qualifies as a bad thing. I have been burned enough by 'apt-get update' disasters to be impressed by the relative scarcity of actual issues caused by a windows update. Thats not to say that there arent bad updates that cause BSODs; but that sort of thing happens on Linux too, and it isnt really what Im talking about. I have gripes that the WinSXS folder gets gigantic, but it gets some love for the fact that running windows update is very often a safe bet (barring major changes like IE upgrades which tend to break stuff like Quickbooks).
A lot of what you complain about could be removed, but a lot of old software would break; Microsoft has decided (of which I am glad) that it is worth having that compatibility in place so that old software will still run. There is a lot of software I remember using on Ubuntu 7.10 that I have had a lot of issues getting to run on versions several years newer, and it is kind of a pity. There are ways to get them working, but it generally involves hacks to install multiple versions of libraries outside of the "blessing" of the package manager, which just seems like a poor solution to me (one apt-get update away from a broken system).
Excessively complex network services, want to enable file sharing? You've now opened up a service port which does a lot more than file sharing...
SSH can be used for a heck of a lot more than secure shell (tunneling, file transfer, etc), but that doesnt mean its "hard to quantify the risks".
sure there is much less of this in the 64bit libs, but you also have all the 32bit compatibility libs present on your system and i'm not aware of any way to uninstall them - hence more cruft since you cant have a pure 64bit system.
API and x86 vs x64 issues dont magically go away because you use Linux instead of Windows. Different systems have different levels of "difficulty" when dealing with mismatches between installed libraries and expected libraries.
Fair enough if you want to call it "legacy cruft", it just occurs to me that its not a terribly helpful term: being able to deal with multiple expected versions of a file is not necessarily a bad thing, and many people would consider the ability to do security updates without having to worry about broken 3rd party programs a good thing.
Dirty workarounds, how about the various hacks implemented in vista/7 which provide for a shadow registry and even shadow filesystem (known as "File and Registry Virtualization") in an attempt to retain compatibility with applications which were designed to run as a privileged admin user? If that's not a dirty workaround i don't know what is...
They basically amount to symlinks. Im pretty sure that Linux and Macs make use of hard / soft links to deal with incompatibilities at times (linking a file to multiple locations to deal with 3rd party expectations). Do hardlinks now count as "dirty hacks"?
Do tell, what are these "huge insecurities due to bad design" in Windows NT 6.x? What are these dirty workarounds in Win7? What legacy cruft is there in Win7 x64?
I do this as well, and have since I started driving, but blind spots remain. Unless you get wide-angel mirrors, you will either have a gap back and to your rear between your rear view vision and your side view, or else you will have a small window where the car has disappeared from your side view as it approaches your shoulder.
Additionally, as you move out from that blindspot, it widens, so if you have your rear-view and side view FoV meeting, you will have a wide blind spot 2 lanes over in a spot you would need to watch in order to shift lanes.
It isnt large, and you can view most of it by turning over your shoulder, but its still a spot your mirrors wont get.
what an absurd statement. Not sure where you live but along the east coast I cannot recall having seen a single railroad crossing gate. Certainly they have flashing lights, but I hardly think you would say that it costs "billions" to replace a long-life lightbulb every 10 years or so.
I didnt say I approved of Assange's hypothethical extradition.
Just pointing out that people hollering "PENTAGON PAPERS!" should probably find another poster child, since this ISNT the SCOTUS case you're looking for.
But of course when its implented in Linux as sudo / su / gksudo, and in Mac (whatever its called), its not "removing the wheels", its called "principle of least privilege".
Times v. United States is generally considered a victory for an extensive reading of the First Amendment, but as the Supreme Court ruled on whether the government had made a successful case for prior restraint, its decision did not void the Espionage Act or give the press unlimited freedom to publish classified documents.
Times v. United States is generally considered a victory for an extensive reading of the First Amendment, but as the Supreme Court ruled on whether the government had made a successful case for prior restraint, its decision did not void the Espionage Act or give the press unlimited freedom to publish classified documents.
You may want to re-read that article. Espionage is still illegal.
Slashdot Mirror
Maybe you should have removed your ram-leaking extensions. Once I did that with 2.0 and on, most of the RAM issues went away. Pretty sure mozilla had a blog titled something like "stop blaming us for your crappy, bug-ridden extensions" around 3.0.
Feinman isnt totally correct:
"Translate these numbers, which are written in base seven, to base five." Translating from one base to another is an utterly useless thing. If you can do it, maybe it's entertaining; if you can't do it, forget it. There's no point to it.
Being able to translate from decimal to hex and binary is quite useful, and at times necessary. Imagine trying to subnet with no conception as to how bases work? Imagine being introduced to this thing called "binary" in intro to IT without actually understanding how an alternate base works?
It also helps teach you how to think, in a more general sense; numbers arent these absolute things, but representations of value in an arbitrary system that can be represented differently (base 10, base 2, as a fraction, as a decimal, etc etc).
Such videos are worthless with no context. What exactly is going on there?
Instead they go with a slogan they don't know what means, don't know how to pronounce, but is short and goes well with beer.
Apparently you can be bigoted (as long as it is against soldiers), and still get a +5 here on slashdot. Well done.
Blaming Mozilla / Asa for flash is one heck of a stretch.
I could have sworn back in the 3.6 days that everyone was complaining about its RAM usage, and that some pined for the 2.0 days of better RAM usage.
Isnt there a saying about the grass being greener?
If you have properly protected your electronics, you should be fine.
I am neither a Ruby nor C developer.
But question, assuming you are doing something like "exec(pdfparse($input))", and you dont sanitize your data, whats to stop someone from specifying the pdf file "somefile.pdf);rm -rf" as the file?
The hashes should be salted, but Im not sure what to make of the accusation that the network protocols send hashes for authentication. What would you rather have them send? The plaintext password?
Regardless, AD login uses Kerberos AFAIK.
Again, no excuse for not using a salt, Im not really clear why they dont do that.
32/64 issues - on linux you can choose between a 32, hybrid 32/64 or pure 64bit system as your needs dictate, with windows its necessary to have the 32bit libraries present wether you intend to use them or not, which makes it cruft.
I believe you can remove WindowsOnWindows if you dont need 32-bit compatibility on the server. That may only be for the upcoming version, I cannot find the reference at the moment.
"File and Registry Virtualization" is a lot more than symlinks, it is more of an overlay filesystem more similar to unionfs if you're familiar with that.
Ive heard that language used, but it depends what youre talking about. If I go into my home directory and issue "dir /a:hs", i get back a number of those "virtualized" folders, which are actually reported as junction points (aka, directory links). Thats for compatibility with the older locations used on prior versions of windows. Ditto with Documents and Settings: it is junctioned to the Users folder.
For 32/64 compatibility, yes, I think you are correct, as a 32-bit process cannot (IIRC) access the 64-bit nodes.
On the other hand it is extremely rare that links would be used for this kind of compatibility kludge.
I cannot give examples offhand, but I have run into it before where a new version doesnt stick a file in the old location, and so it is necessary to link the file to its old location so that things "just work".
Linking a file to multiple locations is a different use case, and is also done for efficiency rather than having multiple copies of the same file.
If you dont use links, you can end up with multiple different versions, causing inconsistent behavior or worse. Links make sure that doesnt happen.
Any ways, presumably at some point, like Rosetta, the FS / registry virtualization will be dropped;
I dont totally disagree with you, and you make some good points; I DO disagree that the handling of the changed folder locations and the 64/32 interoperability fixes qualifies as a bad thing. I have been burned enough by 'apt-get update' disasters to be impressed by the relative scarcity of actual issues caused by a windows update. Thats not to say that there arent bad updates that cause BSODs; but that sort of thing happens on Linux too, and it isnt really what Im talking about. I have gripes that the WinSXS folder gets gigantic, but it gets some love for the fact that running windows update is very often a safe bet (barring major changes like IE upgrades which tend to break stuff like Quickbooks).
A lot of what you complain about could be removed, but a lot of old software would break; Microsoft has decided (of which I am glad) that it is worth having that compatibility in place so that old software will still run. There is a lot of software I remember using on Ubuntu 7.10 that I have had a lot of issues getting to run on versions several years newer, and it is kind of a pity. There are ways to get them working, but it generally involves hacks to install multiple versions of libraries outside of the "blessing" of the package manager, which just seems like a poor solution to me (one apt-get update away from a broken system).
Excessively complex network services, want to enable file sharing? You've now opened up a service port which does a lot more than file sharing...
SSH can be used for a heck of a lot more than secure shell (tunneling, file transfer, etc), but that doesnt mean its "hard to quantify the risks".
sure there is much less of this in the 64bit libs, but you also have all the 32bit compatibility libs present on your system and i'm not aware of any way to uninstall them - hence more cruft since you cant have a pure 64bit system.
API and x86 vs x64 issues dont magically go away because you use Linux instead of Windows. Different systems have different levels of "difficulty" when dealing with mismatches between installed libraries and expected libraries.
Fair enough if you want to call it "legacy cruft", it just occurs to me that its not a terribly helpful term: being able to deal with multiple expected versions of a file is not necessarily a bad thing, and many people would consider the ability to do security updates without having to worry about broken 3rd party programs a good thing.
Dirty workarounds, how about the various hacks implemented in vista/7 which provide for a shadow registry and even shadow filesystem (known as "File and Registry Virtualization") in an attempt to retain compatibility with applications which were designed to run as a privileged admin user? If that's not a dirty workaround i don't know what is...
They basically amount to symlinks. Im pretty sure that Linux and Macs make use of hard / soft links to deal with incompatibilities at times (linking a file to multiple locations to deal with 3rd party expectations). Do hardlinks now count as "dirty hacks"?
Apparently, among other things, you regard the following as being disqualifiers for being president:
Maybe you should find criticisms that are actually grounded in some kind of substance, rather than in your own bias.
Apparently you moonlight as an OS architect.
Do tell, what are these "huge insecurities due to bad design" in Windows NT 6.x? What are these dirty workarounds in Win7? What legacy cruft is there in Win7 x64?
I would love to hear this.
I do this as well, and have since I started driving, but blind spots remain. Unless you get wide-angel mirrors, you will either have a gap back and to your rear between your rear view vision and your side view, or else you will have a small window where the car has disappeared from your side view as it approaches your shoulder.
Additionally, as you move out from that blindspot, it widens, so if you have your rear-view and side view FoV meeting, you will have a wide blind spot 2 lanes over in a spot you would need to watch in order to shift lanes.
It isnt large, and you can view most of it by turning over your shoulder, but its still a spot your mirrors wont get.
what an absurd statement. Not sure where you live but along the east coast I cannot recall having seen a single railroad crossing gate. Certainly they have flashing lights, but I hardly think you would say that it costs "billions" to replace a long-life lightbulb every 10 years or so.
...in all operating systems, yes, there are.
I didnt say I approved of Assange's hypothethical extradition.
Just pointing out that people hollering "PENTAGON PAPERS!" should probably find another poster child, since this ISNT the SCOTUS case you're looking for.
But of course when its implented in Linux as sudo / su / gksudo, and in Mac (whatever its called), its not "removing the wheels", its called "principle of least privilege".
I see, that seems terribly fair and balanced.
I dont recall endorsing any particular candidate for president in my post.
A democrat mocking democracy. Not sure if you'd call that irony or what.
Has anyone in this thread claimed that FLAC was magic?
Never could fathom the approach they took tho,
They released Vista, plugging years worth of holes, and were promptly tar and feathered for it.
(Yes, Vista did have honest to goodness suckage, but most of the complaints centered around the fact that they actually fixed their security)
See above. As indicated by the Wiki article,
Times v. United States is generally considered a victory for an extensive reading of the First Amendment, but as the Supreme Court ruled on whether the government had made a successful case for prior restraint, its decision did not void the Espionage Act or give the press unlimited freedom to publish classified documents.
So yes, it can be criminalized.
Times v. United States is generally considered a victory for an extensive reading of the First Amendment, but as the Supreme Court ruled on whether the government had made a successful case for prior restraint, its decision did not void the Espionage Act or give the press unlimited freedom to publish classified documents.
You may want to re-read that article. Espionage is still illegal.
Espionage is and always has been, IIRC, a crime.
Unlikely, since last time I checked Holocaust denial was a criminal offense in Germany.