First, you're assuming that greenhouse gases are a significant contributer to global warming. This is not proved, beyond the obvious fact that without any greenhouse effect at all the average temperature of Earth would be around freezing. There is nothing to prove a causal relationship between elevated CO2 levels and warming.
The laws of thermodynamics aren't proved either. Evidence is examined, and tentative theories are formulated. Nothing is proved. Welcome to science.
Alternate Data Streams are good place for file managers to cache their metadata about a file, since if the file is moved, the metadata moves with it, and if the file is deleted, so is the metadata. Does Explorer actually use ADS this way? I don't know.
Yes. If you're a Slashdot reader, and you haven't figured out why people complain about Windows so much, then there's really nothing more that can be said to you.
Your entire rant seems to hinge on the notions that UTF-8 can't represent every possible Unicode character, and that every bit of code that ever processes text will should know about the Unicode spec. The first notion is wrong, and the second notion is bad for both security and speed.
As for storage efficiency of UTF-8 for non-Western character sets, ever heard of RFC 1951? I suggest you read it. As for internal representation of characters inside programs, you're free to use whatever you want.
Linux doesn't have any notion of a "file type" built-in, with the exception of the "execute permission" bits; The filesystem simply maps names to inodes to byte streams. This means that all of the bugs that are associated with file type mapping simply disappear, in most cases.
You don't want to change that. You may think you do, but you don't. Trust me on this (or go do some more research).
If i search for TPSreports.txt will tpsreports.txt evern come up? People have a hard enough time remembering what they named something and you would ad another level of complexity above that? I always thought this was a very big linux flaw.
locate -i TPSreports.txt
or
find / -iname TPSreports.txt
Trying to write non-buggy, consistently-behaving programs with a case-insensitive filesystem is harder than you think. Case sensitivity in the filesystem is one of Linux's strengths, and is one of the easiest things to get used to.
What annoys the hell out of me, though, is scp. You have to double-escape stuff because it apparently uses the cp utility on the remote machine as an unescaped shell command, rather than setting up the argument vector and starting cp directly.
I usually use rsync over SSH, which tends to be a little saner. But yeah, scp is seriously brain-damaged.
This is somewhat offtopic, but if we want universal wireless Internet access (which we do... well I do), then eventually AUPs are going to have to go away, and network protocols that take this into account will have to be used (email and universal IPSEC come to mind)...
There you are coding the bulk importing tool for SQL server. You have written all this code to try and determine data types, matching the columns to commas, etc. You wrote the loop that iterates through the file. And then the manager came along and told you not to add any eception handling to the code inside the loop?
The manager would have said, "good enough, now drop everything and do this super-urgent project before the deadline next month".
Whether or not you are willing to accept it, I suspect there are as many bad managers out there as there are lazy programmers.
I get that linux is more secure then windows. ESPECIALLY if you're just a Joe-User: It's so difficult to install and configure that he'd eventually just forget-it and leave the PC half-baked and useless.
No, it isn't difficult to install and configure. Heck, I use Debian, which is arguably one of the more expert-oriented distributions, and it's still far easier to set up than any recent version of Windows. I don't just mean the install CD; I mean the install CD, upgrading everything using Microsoft Update, and getting a basic set of third-party software installed. It takes even longer if I want to install, for example, Visual Studio. Any time I do a Windows install, I know I'm going to waste a full day at the computer doing it. And that's assuming I don't have any trouble with the drivers.
Getting a fully-loaded Debian system working doesn't take nearly as much of my time (of course, this also depends on the drivers working).
Installing operating systems requires specialized knowledge. So does driving a car, or piloting an airplane. That doesn't mean it's difficult.
Of course, installing Debian doesn't have to be done very often, so it can be left to professionals. I really can't say the same thing for Windows.
Yeah, the kernel is monolithic, that's because research over the past 10-15 years shows that microkernels are slooooow.
That's a often-debunked myth. Research over the past 10-15 years shows that Mach is slow because it's bloated. Newer microkernels are much smaller (for example, L4 can apparently fit entirely inside your CPU cache), and don't incur anywhere near as much of a performance hit.
Instead of drawing conclusions based on an old flamewar, go read some of what Andrew S. Tanenbaum and others have written on the subject.
we shouldn't dismiss the guy... when we, admittedly, know so very little about him, and are drawing wild conclusions about his character and ability from essentially nothing.
Congratulations then, you're wholly incapable of recognizing or interpreting entendre. How does being that dense make you enlightened?
Apparently you didn't read the part where the poster wrote, "before I read the context of it being brought up".
People ignore unimportant details all the time. If you're a geek, you know this (how often do you actually read the entire content of a dialog box or a log file?). To some people, racial differences just aren't important enough to merit attention most of the time. What would you prefer?
Slashdot Mirror
The laws of thermodynamics aren't proved either. Evidence is examined, and tentative theories are formulated. Nothing is proved. Welcome to science.
I think we're all hoping that they'll just leave us the hell alone.
Alternate Data Streams are good place for file managers to cache their metadata about a file, since if the file is moved, the metadata moves with it, and if the file is deleted, so is the metadata. Does Explorer actually use ADS this way? I don't know.
Yes. If you're a Slashdot reader, and you haven't figured out why people complain about Windows so much, then there's really nothing more that can be said to you.
Your entire rant seems to hinge on the notions that UTF-8 can't represent every possible Unicode character, and that every bit of code that ever processes text will should know about the Unicode spec. The first notion is wrong, and the second notion is bad for both security and speed.
As for storage efficiency of UTF-8 for non-Western character sets, ever heard of RFC 1951? I suggest you read it. As for internal representation of characters inside programs, you're free to use whatever you want.
Linux doesn't have any notion of a "file type" built-in, with the exception of the "execute permission" bits; The filesystem simply maps names to inodes to byte streams. This means that all of the bugs that are associated with file type mapping simply disappear, in most cases.
You don't want to change that. You may think you do, but you don't. Trust me on this (or go do some more research).
I think this works in bash:
I think that was true until Windows ME. WinNT/2K/XP/2K3 all use an NT-based installer, as far as I'm aware.
locate -i TPSreports.txt
or
find / -iname TPSreports.txt
Trying to write non-buggy, consistently-behaving programs with a case-insensitive filesystem is harder than you think. Case sensitivity in the filesystem is one of Linux's strengths, and is one of the easiest things to get used to.
How would you know? It's not like Microsoft has released the specification for it...
[Insert rant about proprietary data formats here]
I usually use rsync over SSH, which tends to be a little saner. But yeah, scp is seriously brain-damaged.
That character was stripped to make room for the kilobytes of extra data that you could fit on an Amiga floppy. :-P
I think you're getting libtool confused with the runtime dynamic linker (ld.so). libtool is a script used during compilation.
HTML entities are probably © The SCO Group, like everything else.
That part seems to be correct.
This is somewhat offtopic, but if we want universal wireless Internet access (which we do... well I do), then eventually AUPs are going to have to go away, and network protocols that take this into account will have to be used (email and universal IPSEC come to mind)...
How do they avoid getting air bubbles into the patient's bloodstream?
The manager would have said, "good enough, now drop everything and do this super-urgent project before the deadline next month".
Whether or not you are willing to accept it, I suspect there are as many bad managers out there as there are lazy programmers.
No, it isn't difficult to install and configure. Heck, I use Debian, which is arguably one of the more expert-oriented distributions, and it's still far easier to set up than any recent version of Windows. I don't just mean the install CD; I mean the install CD, upgrading everything using Microsoft Update, and getting a basic set of third-party software installed. It takes even longer if I want to install, for example, Visual Studio. Any time I do a Windows install, I know I'm going to waste a full day at the computer doing it. And that's assuming I don't have any trouble with the drivers.
Getting a fully-loaded Debian system working doesn't take nearly as much of my time (of course, this also depends on the drivers working).
Installing operating systems requires specialized knowledge. So does driving a car, or piloting an airplane. That doesn't mean it's difficult.
Of course, installing Debian doesn't have to be done very often, so it can be left to professionals. I really can't say the same thing for Windows.
This is only a problem for software that doesn't come with source code.
That's a often-debunked myth. Research over the past 10-15 years shows that Mach is slow because it's bloated. Newer microkernels are much smaller (for example, L4 can apparently fit entirely inside your CPU cache), and don't incur anywhere near as much of a performance hit.
Instead of drawing conclusions based on an old flamewar, go read some of what Andrew S. Tanenbaum and others have written on the subject.
Or management, who de-prioritized it as a "nobody will ever do that" feature.
On the other hand, considering Microsoft's idea of what constitutes an "engineer", it wouldn't surprise me that it's the "engineers'" fault.
You must be new here.
People have to want to mirror it.
I think you missed the point. Read the post again. The grandparent is probably talking about Microsoft's anti-trust obligations.
Apparently you didn't read the part where the poster wrote, "before I read the context of it being brought up".
People ignore unimportant details all the time. If you're a geek, you know this (how often do you actually read the entire content of a dialog box or a log file?). To some people, racial differences just aren't important enough to merit attention most of the time. What would you prefer?