Even Microsoft took less than 10 years to become less shitty. What the hell is taking so long, open source people?
The same reason it's taking Microsoft so long. Too much programming, not enough design work, and not enough attention paid to quality and efficiency.
<rant>
You can tell which programmers is contributing to the problem: anyone who says "but with today's 2GHz computers, that's not really a problem" is too lazy or too unskilled to actually FIX the problem, so they simply justify it. It's the same problem as Microsoft has had, unfortunately.
This is known as a one-time pad (where the key is the same length as the message), and it's unbreakable (not just hard to break). Of course, it's also difficult to exchange these keys.
Perl is practical language for extracting and reporting. For anything else, it tends to suck. (But it also tends to be easy for beginners, so people cling to it like they cling to VB, instead of learning how to program.)
Yep, you are. First of all, depending on the case, it's quite possible that it will not "exhibit itself as odd subtle bugs next time you link to the library". This is especially true when using macros to declare types . . . like when you use autoconf.
For instance, time(2) has returned a long int pretty much forever. So, it would have been safe to name a variable storing time(2)'s return value as lCurrentTime. Let's say you also have another long int somewhere else called lFoo
When the 64-bit platforms roll in, and even possibly replace 32-bit platforms, you use autoconf to compile your program perfectly on those platforms (since you used a macro to declare type). Now, you have the wonderful situation where lCurrentTime is a long long int, yet lFoo is a long int.
What happens? New developers are confused and frustrated, and experienced ones are still confused, but they soon make a habit of relying on variable declarations, rather than the notation (and will curse your name every time they screw up because of the notation).
In the long run, Hungarian notation can't be trusted, and if you need it to remember your types, your code is probably already too complex, and needs re-thinking (eg. modularization) anyway.
Maybe, but on Debian, it's actually possible to do apt-get -y install ash && ln -sf ash/bin/sh without too much harm coming. Also, the Debian maintainers appear to listen when you report bugs about bashisms.
Hungarian notation is fine...until you change around your datatypes (think of promoting char -> int -> long -> long long, or float -> double). Then, it's just confusing.
Slashdot Mirror
Even Microsoft took less than 10 years to become less shitty. What the hell is taking so long, open source people?
The same reason it's taking Microsoft so long. Too much programming, not enough design work, and not enough attention paid to quality and efficiency.
<rant>
You can tell which programmers is contributing to the problem: anyone who says "but with today's 2GHz computers, that's not really a problem" is too lazy or too unskilled to actually FIX the problem, so they simply justify it. It's the same problem as Microsoft has had, unfortunately.
</rant>
I am contacting you to ask your advice.
It probably suffers from the same problems.
or even Xoring with a big chunk of random data?
This is known as a one-time pad (where the key is the same length as the message), and it's unbreakable (not just hard to break). Of course, it's also difficult to exchange these keys.
The only thing that's secure against quantum computers is one-time pads, which are impractical over the internet.
Perl is practical language for extracting and reporting. For anything else, it tends to suck. (But it also tends to be easy for beginners, so people cling to it like they cling to VB, instead of learning how to program.)
IPv6. Bug your ISP for it today.
*Sigh* They do in Canada. OTOH, at least we don't have a DMCA...
That's correct. Another neat thing is that you can index your tar files, and seek wherever you want to extract the appropriate files.
Having a published API lets you re-implement Windows, extend Windows, and extinguish Windows.
Please tell me they're not running IPv4 on it.
Well, at least with ACPI, you'll soon be able to use the power button.
Pick a new window manager?
Negative numbers are easier here, due to the weather. Everybody knows that -40 is colder than +30.
For instance, time(2) has returned a long int pretty much forever. So, it would have been safe to name a variable storing time(2)'s return value as lCurrentTime. Let's say you also have another long int somewhere else called lFoo
When the 64-bit platforms roll in, and even possibly replace 32-bit platforms, you use autoconf to compile your program perfectly on those platforms (since you used a macro to declare type). Now, you have the wonderful situation where lCurrentTime is a long long int, yet lFoo is a long int.
What happens? New developers are confused and frustrated, and experienced ones are still confused, but they soon make a habit of relying on variable declarations, rather than the notation (and will curse your name every time they screw up because of the notation).
In the long run, Hungarian notation can't be trusted, and if you need it to remember your types, your code is probably already too complex, and needs re-thinking (eg. modularization) anyway.
Why does an accounting firm have to be clueful about web design?
First part: often. Second part: grow up.
Maybe, but on Debian, it's actually possible to do apt-get -y install ash && ln -sf ash /bin/sh without too much harm coming. Also, the Debian maintainers appear to listen when you report bugs about bashisms.
Search and replace kills source-compatibility.
And 30 years later, I'm getting more spam than ever!
On Debian, it returns Bash's builtins(1) manpage.
Trademark law?
No, but it can crap all over it if you're not careful!
It's been said 1000 times: non-free is NOT part of Debian. So, in effect, it IS being dropped.
Hungarian notation is fine...until you change around your datatypes (think of promoting char -> int -> long -> long long, or float -> double). Then, it's just confusing.
OpenQuartz , needs GPL-compatible sounds!