How about you list the other definitions of deprecate:
http://dictionary.reference.com/browse/deprecate
The word has clearly undergone a change in the last century, as words generally like to do.
Additionally, technical fields, or any fields in general, tend to have their own vocabulary apart from that of the standard language. It's obviously not kosher to use these vocabulary items (jargon) outside the context of that field, but it is not uncommon for them to "cross over" and become part of the standard language.
You can't throw a list of podunk Debian-based distros that three people use and expect me to take that seriously. Ubuntu is the ONLY commercially-supported, widely-used distro that uses APT. Every other distro in that category uses RPM: SuSE, RedHat/Fedora/CentOS (see, I'm even being fair and lumping them together as one distro), Mandriva. It's also the format specified by the LSB. For better or worse, a standard will emerge and I can assure you that DEB won't be it. Eventually Ubuntu will switch to RPM like it should and then Linux can finally make sense when it comes to package management.
I just love it when people get angry at/about RedHat without realizing that without RedHat, Linux would not be where it is today. It has been the foremost corporate contributor to Linux and Linux on the desktop by far. It has also proven to the market that there is a viable business model selling Linux and Linux services. Without that, it'd be doubtful that as many corps and organizations would not have adopted Linux.
Some people seem to think that if there were no evil Linux corps, Linux would be better. Well, this isn't 1992 anymore. Weekend coders can't produce a fully-functional OS and software stack with QA and performance factored in. Linux would be NOWHERE without the corporations that have hired many people to work full time on Linux projects. RedHat is the chief among these.
BTW, I'm agreeing with you, but just adding some more points.
I'm sorry, but RPM is the standard, not APT/DEB. It may have come along earlier, but that's water under the bridge now.
And yes, I am aware of the distinction between package manager and package format. I should have said YUM/RPM instead of just RPM. Both are light-years ahead of APT/DEB. Looking at the man-page for APT scared me as I found that a number of searching and installation options I had grown accustomed to with YUM were not possible at all.
X.org IS XFree86. All the developers left the latter and became the former, along with the codebase. So, in a sense, you are right, but it was hardly normal competition.
Quite true, since so many people falsely believe RPM is inferior, when it is, in fact, superior to deb in almost every way. Having worked with both, including making my own RPMs and specfiles, I can safely say, that using RPM is a dream compared to trying to do anything interesting with apt.
How is this ANY different from your standard Ubuntu fare? Yes, Ubuntu has the LTS releases, but honestly, who doesn't upgrade when the next Ubuntu comes out, especially since they refuse to backport newer versions of software to older versions of Ubuntu.
It doesn't matter what we know, it only matters what he is talking about. And he implied in the second part of the sentence that he did not believe it was a scam. But if it were, he says, then he agrees about some point. It may certainly be true that it is a scam, and if agreed that it was, then you would be right. But that is not the case, so you are wrong.
It's funny because I basically use Python indenting rules for all of my programming, and everyone should anyways. I've had no problem with copy and paste (any good editor will take care of fixing the indentation for you, like Eclipse's editor), or adding in one off lines, or any of the other stuff you've complained about.
Uh....how is that actually different than month/day/year or day/month/year? It's just a different ordering. The only winning point is that year-first is easier for comparison.
Actually, the ability to use the force was also genetic in the first Star Wars trilogy. It just wasn't played up as much.
Re:Python is part of the answer
on
Open Source Math
·
· Score: 1
No, that's not true. If the program produced with an unoptimized compiler relies on undefined behavior, then there is no way an optimizing compiler can guarantee that the optimized code will produce EXACTLY the same undefined behavior, because, well, the behavior is undefined. The only time it should produce the same behavior is if all of the behavior is well-defined by the standard.
What's to stop people from taking pictures of you and posting them on the streetcorner, or giving them to a newspaper, or putting them on a blog or personal website...
There's really no way to stop that except for suing for libel, if you actually have a case.
Actually, Windows 3.x basically used MS-DOS as a bootloader and occasionally for drivers. It already had a preemptive multitasking kernel using 386 virtual memory and paging. Unfortunately, all Windows programs ran in a single task, but each DOS program ran in a separate kernel task since that was the only way to multitask DOS applications.
I hope by "readily feasible", you mean "hard, but not impossible". Obviously (and necessarily) anything that can be done in a higher-level language can be done in assembly.
Why is he wrong to say the NOT gate is the easiest? The NAND gate is only the simplest for solid state transistor-based circuitry. But quantum computers are not made of anything like that, so why should NAND necessarily be the easiest for quantum computers as well?
Hmm, this is very insightful. I hope somebody figures this out. Oh wait...Linux distros have been doing this for years. How long have you been using Gentoo or LFS? If you had touched a modern Linux distro, you'd find that this is exactly what they do and have done for a number of years.
No...voltage is just potential to do work, like the height a boulder falls off a cliff. Amps is actual current ("the size of the electrical flow" in actuality) in coulombs per second -- like the mass of the boulder. In fact, if you'd bothered to look at the units, you'd see that what you say doesn't make much sense.
120V with a current of 0.0001 amps is nothing. 5V with a current of 1 amp will probably kill you, or at least hurt you pretty bad. It's all about the amps. But all people know is volts, so that's what they care about.
But he never said that they would have to with RPM either. All he said is that they could use --define on the rpmbuild command line to pass in information to the specfile, which is free to interpret that information however it wishes, including, but not limited to, modifying configure flags.
Yes, they don't. The problems are either that they don't use autotools, or they use some ass-backwards build/install system that doesn't allow for relocatable builds and configuring options. I found one package that required you to manually copy files and modify the system JRE to work! That's just ridiculous. If they used normal source packaging conventions, making an RPM would be a breeze. I made an RPM for a nicely autotooled package in a matter of minutes. And I'm not THAT experienced in RPM.
I think it's part of a larger problem that software developers often don't want to, or care to, do things the right way. And so they end up spending more time fighting with the system they are using than just taking 5 minutes to do some research. At my place of work, we have had a lot of hackery to force Java components to be of a certain size. This involved overriding setSize(), setBounds() and making hacks into layout managers. All of that could have been avoided by just using Java's layout management system as it is intended. We're in the process of undoing that mess now, fortunately.
But maybe I just care too much about the technology as a thing unto itself, instead of something I have to fight with for 8 hours a day so I can get a paycheck.
Slashdot Mirror
How about you list the other definitions of deprecate: http://dictionary.reference.com/browse/deprecate The word has clearly undergone a change in the last century, as words generally like to do. Additionally, technical fields, or any fields in general, tend to have their own vocabulary apart from that of the standard language. It's obviously not kosher to use these vocabulary items (jargon) outside the context of that field, but it is not uncommon for them to "cross over" and become part of the standard language.
You can't throw a list of podunk Debian-based distros that three people use and expect me to take that seriously. Ubuntu is the ONLY commercially-supported, widely-used distro that uses APT. Every other distro in that category uses RPM: SuSE, RedHat/Fedora/CentOS (see, I'm even being fair and lumping them together as one distro), Mandriva. It's also the format specified by the LSB. For better or worse, a standard will emerge and I can assure you that DEB won't be it. Eventually Ubuntu will switch to RPM like it should and then Linux can finally make sense when it comes to package management.
I just love it when people get angry at/about RedHat without realizing that without RedHat, Linux would not be where it is today. It has been the foremost corporate contributor to Linux and Linux on the desktop by far. It has also proven to the market that there is a viable business model selling Linux and Linux services. Without that, it'd be doubtful that as many corps and organizations would not have adopted Linux. Some people seem to think that if there were no evil Linux corps, Linux would be better. Well, this isn't 1992 anymore. Weekend coders can't produce a fully-functional OS and software stack with QA and performance factored in. Linux would be NOWHERE without the corporations that have hired many people to work full time on Linux projects. RedHat is the chief among these. BTW, I'm agreeing with you, but just adding some more points.
I'm sorry, but RPM is the standard, not APT/DEB. It may have come along earlier, but that's water under the bridge now. And yes, I am aware of the distinction between package manager and package format. I should have said YUM/RPM instead of just RPM. Both are light-years ahead of APT/DEB. Looking at the man-page for APT scared me as I found that a number of searching and installation options I had grown accustomed to with YUM were not possible at all.
X.org IS XFree86. All the developers left the latter and became the former, along with the codebase. So, in a sense, you are right, but it was hardly normal competition.
Quite true, since so many people falsely believe RPM is inferior, when it is, in fact, superior to deb in almost every way. Having worked with both, including making my own RPMs and specfiles, I can safely say, that using RPM is a dream compared to trying to do anything interesting with apt.
How is this ANY different from your standard Ubuntu fare? Yes, Ubuntu has the LTS releases, but honestly, who doesn't upgrade when the next Ubuntu comes out, especially since they refuse to backport newer versions of software to older versions of Ubuntu.
It doesn't matter what we know, it only matters what he is talking about. And he implied in the second part of the sentence that he did not believe it was a scam. But if it were, he says, then he agrees about some point. It may certainly be true that it is a scam, and if agreed that it was, then you would be right. But that is not the case, so you are wrong.
It's funny because I basically use Python indenting rules for all of my programming, and everyone should anyways. I've had no problem with copy and paste (any good editor will take care of fixing the indentation for you, like Eclipse's editor), or adding in one off lines, or any of the other stuff you've complained about.
Uh....how is that actually different than month/day/year or day/month/year? It's just a different ordering. The only winning point is that year-first is easier for comparison.
How is it any less ambiguous? It could just as easily be year-day-month. The numbers don't actually tell you.
Actually, the ability to use the force was also genetic in the first Star Wars trilogy. It just wasn't played up as much.
No, that's not true. If the program produced with an unoptimized compiler relies on undefined behavior, then there is no way an optimizing compiler can guarantee that the optimized code will produce EXACTLY the same undefined behavior, because, well, the behavior is undefined. The only time it should produce the same behavior is if all of the behavior is well-defined by the standard.
The first book or two are pretty lame. The later books are much better (although some parts of 5 and 6 are pretty boring).
What's to stop people from taking pictures of you and posting them on the streetcorner, or giving them to a newspaper, or putting them on a blog or personal website... There's really no way to stop that except for suing for libel, if you actually have a case.
Actually, Windows 3.x basically used MS-DOS as a bootloader and occasionally for drivers. It already had a preemptive multitasking kernel using 386 virtual memory and paging. Unfortunately, all Windows programs ran in a single task, but each DOS program ran in a separate kernel task since that was the only way to multitask DOS applications.
I hope by "readily feasible", you mean "hard, but not impossible". Obviously (and necessarily) anything that can be done in a higher-level language can be done in assembly.
Why is he wrong to say the NOT gate is the easiest? The NAND gate is only the simplest for solid state transistor-based circuitry. But quantum computers are not made of anything like that, so why should NAND necessarily be the easiest for quantum computers as well?
You mean like this? http://www.shodor.org/interactivate/activities/Fun ctionFlyer/
Hmm, this is very insightful. I hope somebody figures this out. Oh wait...Linux distros have been doing this for years. How long have you been using Gentoo or LFS? If you had touched a modern Linux distro, you'd find that this is exactly what they do and have done for a number of years.
No...voltage is just potential to do work, like the height a boulder falls off a cliff. Amps is actual current ("the size of the electrical flow" in actuality) in coulombs per second -- like the mass of the boulder. In fact, if you'd bothered to look at the units, you'd see that what you say doesn't make much sense. 120V with a current of 0.0001 amps is nothing. 5V with a current of 1 amp will probably kill you, or at least hurt you pretty bad. It's all about the amps. But all people know is volts, so that's what they care about.
I tried it myself it it works fine. Perhaps a version issue?
You could use a bind mount on the mail directory with atime enabled.
/path/to/maildir /path/to/maildir
mount -o atime --bind
But he never said that they would have to with RPM either. All he said is that they could use --define on the rpmbuild command line to pass in information to the specfile, which is free to interpret that information however it wishes, including, but not limited to, modifying configure flags.
Yes, they don't. The problems are either that they don't use autotools, or they use some ass-backwards build/install system that doesn't allow for relocatable builds and configuring options. I found one package that required you to manually copy files and modify the system JRE to work! That's just ridiculous. If they used normal source packaging conventions, making an RPM would be a breeze. I made an RPM for a nicely autotooled package in a matter of minutes. And I'm not THAT experienced in RPM.
I think it's part of a larger problem that software developers often don't want to, or care to, do things the right way. And so they end up spending more time fighting with the system they are using than just taking 5 minutes to do some research. At my place of work, we have had a lot of hackery to force Java components to be of a certain size. This involved overriding setSize(), setBounds() and making hacks into layout managers. All of that could have been avoided by just using Java's layout management system as it is intended. We're in the process of undoing that mess now, fortunately.
But maybe I just care too much about the technology as a thing unto itself, instead of something I have to fight with for 8 hours a day so I can get a paycheck.