"There is one rule for the industrialist and that is: Make the best quality of goods possible at the lowest cost possible, paying the highest wages possible." -- Henry Ford
Libertarians will kindly note that Henry Ford died in 1947.
Yes, I'm aware it's standardized in the ANSI spec. Nevertheless, I still don't consider it true C code. Preprocessor code is metacoding. Similarly, I don't consider !doctype to be true HTML, and so on. Metacode is extremely useful, and in the case of C it was decided that it is so useful that standardizing it was required. But metadata and metacoding is a secondary language used to facilitate the requirements of the primary language.
If you want to stomp your feet and pout, go ahead.
It's not really part of C, though. It's a common program that parses C code for errors and also listens to instructions means specifically for it. It's run as part of the compiler, but the compiler is not C either. C is a language, not a program.
Yes, well, the Maya were also known for human sacrifice. You have a lot of encouragement for getting your days and nights right when the last guy who got it wrong has his chest cut open with a stone blade and his heart removed right in front of you.
You think to yourself "Hey, I *need* my heart. I should figure out when the equinoxes are so I don't end up as the next scapegoat for a bad harvest."
The Gregorian calendar has leap years as follows: Every year divisible by 4 is a leap year. Except when that year is also divisible by 100, in which case it is *not* a leap year. Except when that year is also divisible by 400, in which case it *is* a leap year.
Hence 2000 was a leap year. 2100 will not be.
The fun hokeyness is due to the Western assumption that everything is linear, in spite of the fact that we repeat months, days of months, and days of weeks constantly. We don't find it odd that there are thousands of Wednesdays or March 21sts, but somehow we can't understand there ever being more than one 2007.
Only in the case where service users are also service providers. If websites out there all use Google's API and Google finds that they are losing money by losing direct traffic, they will truncate their API or drop the service.
No for-profit business is in the business of providing services for free. What they will do is give you a free lunch in exchange for picking up the dinner bill.
Yeah, a few of the better techs found that out searching the chipset numbers. You try and convince Windows of that. It wouldn't accept them automatically, and if you forced it to then the device showed up as having an error. And sound either didn't play, or played with the wrong tone and tempo (both really high).
I don't know what HP (Compaq?) did to 'em, but nothing worked with them. One of the techs even tried every device driver Creative Labs had for download as well as every driver that might work from Windows. Not even legacy drivers for SB 16-bit or 8-bit cards would work. He got *one* driver to work perfectly, but every time you rebooted it would have to be reinstalled.
That happened with some hardware we had lying around. We had two dozen PCI SB Live 512 cards someone got off eBay for $5, but no longer had this discs. There were no drivers available for download from creative or HP because some 3rd party software packaged with the drivers prohibited it. They weren't even on driver download sites. We used to use it as a hazing ritual to send someone out to find drivers for them because we knew nobody could ever do it no matter where they went or who they called. One day one of the guys took them and used 'em for target practice. Literally.
You clearly have not been on Steam in a long time.
Current library includes: Call of Duty 1 & 2 Civilization III & IV Flatout 1 & 2 Psychonauts Prey Dark Messiah of Might & Magic Midevil II: Total War Dreamfall: The Longest Journey *And* PopCap games like Bejeweled.
Yes, you can use pseudo-random nonces and pseudo-random session tokens to prevent replay attacks, too, but they have their own caveats. Encryption makes is unreasonable to access data, but authentication makes it unusable.
The point is, in order for two systems to authenticate they must agree on reality. Why would you trust a system that doesn't agree on what time [meaning UTC or unixtime] it is? Agreeing on UTC time is a trivial request for a system to make of another for authentication.
It's like complaining that you can't set your resolution to 2,000,000 x 1. The complaint is not reasonable.
UTC timestamps don't have time zones. Rather, they all implicitly use GMT as the time zone. UTC is "the number of seconds since 00:00 Jan 1 1970 GMT" (this is why UTC doesn't technically account for leap seconds). That's an absolute number of seconds no matter where you are in the world. UTC is independent of Earth-based times such as GMT and Universal Time, and, again, this is why UTC doesn't know about leap seconds.
To fix the "future" problem, all Outlook needs to do is: 1. Store UTC on the Exchange server. 2. Allow meeting times to be set with time zone info. So if I'm in Tokyo and I need to set a meeting at 9 am next week New York time, I should get three drop-down boxes: 1: Date, 2: Time, 3: Time zone (with a default of the current locale).
Alternately, they can force UTC time for meeting creation, but that's just as absurd as the current "what's a timezone?" problem.
Are you changing the clock or are you changing the time zone? If you change the clock, you're changing the internal UTC-type clock. If you're changing time zone, you're just affecting how time is displayed. Don't tell the computer that the time has changed. Tell it that you're in a different time zone.
The problem, of course, is that Exchange is not very time-zone aware, particularly with calendar entries.
Yes, but UTC systems will still display the correct time. They're 100% accurate, they just have the wrong time zone. They will work perfectly well with and agree with patched systems. This is one reason you can login to a server in Cairo from New York: the systems agree that the time is the same. Windows doesn't much care about time zone changes. You'll be able to log in on March 12th whether you're patched or not.
The only problem MS made here is by not using UTC for Exchange calendar entries in the first place. Rather, for using timestamp without time zone, which, frankly, is absurd. Did they not expect email to be a global system?
I've not seen any *nix distro use anything but/home for years, with the exception of the superuser wich always uses/root. The last time I did was about the time Microsoft changed from %windir%\profiles (the Windows NT 4 directory) to Documents and Settings.
Additionally, you can use the '~' shortcut. '~' is current user's home directory. It's equivalent to %userprofile% in Windows. '~fred' is user fred's home directory. Also, 'cd' with no directory always changes you back to your home directory (it's the same as 'cd ~').
Linux's unified directory structure is very confusing especially compared to the Windows system (everything is a file, logical to physical mapping is not obvious), but home directories are one of the easiest things possible. The most complicated thing for me was figuring out the difference between/bin,/usr/bin, and/usr/local/bin (and then/sbin and it's contemporaries). It boils down to needing to learn the FHS (http://en.wikipedia.org/wiki/Filesystem_Hierarchy _Standard), and then learning the history of the directories. For example,/opt and/srv are still rather new, so a lot of systems still use/var.
If you think about it though, Windows's directories are also rather complex. Windows doesn't install in C:\Windows. It's really in C:\Windows\System32. Program Files is supposed to be read only, and it's one of the reasons so many apps only work when you're an admin. Documents and Settings, while an accurate name, is filled with hidden directories where the OS is trying to keep the user from breaking it, but you still need to get into them from time to time. pagefile.sys is the system pagefile, hiberfil.sys is for hibernation. NTLDR is the bootstrap, and the bootloader is kept in the volume MBR and is completely hidden since all it does is find NTLDR and run it. Most systems have an \i386 directory copied from the CD since Windows wants it from time to time. There's also \RECYCLER which is the recycle bin, and \System Volume Information which contains information Windows itself uses as well as where it store the Restore Points. %userprofile%\NTUSER.DAT is the user's registry hive, while the other registry hives all live in C:\WINDOWS\system32\config. %windir%\system32\config\systemprofile and %documentsandsettings%\.Default user also exists on most systems, containing information on the default profiles. %windir%\system32\drivers is filled with kernel-mode code (real mode, mostly drivers) and %windir%\system32\dllcache contains protected-mode code (user-mode apps). Then there's 5 or 6 different temp directories, and storage locations for Group Policy, security objects, system logs, etc.
IMX, none of that is half as well documented as the Linux stuff.
Probably because it was fun. You'll note that the criticisms he levels can be equally used against nearly every NES cart ever produced, and many people still find those much more enjoyable than the triple-A title shit coming from today's superstudios. Doom didn't do anything that hadn't been done before. It just looked good and was lots of fun.
Nobody is going to buy Vista as boxed retail except bleeding edgers who need DirectX 10. The vast majority will buy a PC within the next few years and it will ship with Vista pre-installed. Microsoft learned how this worked back with Windows 9x.
To most people, a computer is indistinguishable from a microwave or a VCR. The OS might as well be embedded.
Slashdot Mirror
"There is one rule for the industrialist and that is: Make the best quality of goods possible at the lowest cost possible, paying the highest wages possible." -- Henry Ford
Libertarians will kindly note that Henry Ford died in 1947.
Yes, I'm aware it's standardized in the ANSI spec. Nevertheless, I still don't consider it true C code. Preprocessor code is metacoding. Similarly, I don't consider !doctype to be true HTML, and so on. Metacode is extremely useful, and in the case of C it was decided that it is so useful that standardizing it was required. But metadata and metacoding is a secondary language used to facilitate the requirements of the primary language.
If you want to stomp your feet and pout, go ahead.
Still. Not. C.
It's not really part of C, though. It's a common program that parses C code for errors and also listens to instructions means specifically for it. It's run as part of the compiler, but the compiler is not C either. C is a language, not a program.
It's like saying that PHP *is* HTML.
#ifdef is a pre-processor instruction. It's not C code at all.
Yet PS3 portability was *absolutely vital*.
Yes, well, the Maya were also known for human sacrifice. You have a lot of encouragement for getting your days and nights right when the last guy who got it wrong has his chest cut open with a stone blade and his heart removed right in front of you.
You think to yourself "Hey, I *need* my heart. I should figure out when the equinoxes are so I don't end up as the next scapegoat for a bad harvest."
The Gregorian calendar has leap years as follows:
Every year divisible by 4 is a leap year.
Except when that year is also divisible by 100, in which case it is *not* a leap year.
Except when that year is also divisible by 400, in which case it *is* a leap year.
Hence 2000 was a leap year. 2100 will not be.
The fun hokeyness is due to the Western assumption that everything is linear, in spite of the fact that we repeat months, days of months, and days of weeks constantly. We don't find it odd that there are thousands of Wednesdays or March 21sts, but somehow we can't understand there ever being more than one 2007.
Only in the case where service users are also service providers. If websites out there all use Google's API and Google finds that they are losing money by losing direct traffic, they will truncate their API or drop the service.
No for-profit business is in the business of providing services for free. What they will do is give you a free lunch in exchange for picking up the dinner bill.
Here's a test for you. Get a DVD-R or CD-R. Burn your favorite Linux iso on it, and make sure it works.
Now get a flathead screwdriver and scrape of some of the label, and try again.
Yeah, a few of the better techs found that out searching the chipset numbers. You try and convince Windows of that. It wouldn't accept them automatically, and if you forced it to then the device showed up as having an error. And sound either didn't play, or played with the wrong tone and tempo (both really high).
I don't know what HP (Compaq?) did to 'em, but nothing worked with them. One of the techs even tried every device driver Creative Labs had for download as well as every driver that might work from Windows. Not even legacy drivers for SB 16-bit or 8-bit cards would work. He got *one* driver to work perfectly, but every time you rebooted it would have to be reinstalled.
I dunno, it was a few years ago. Now that I think about it, maybe they were just SB PCI 512's.
That happened with some hardware we had lying around. We had two dozen PCI SB Live 512 cards someone got off eBay for $5, but no longer had this discs. There were no drivers available for download from creative or HP because some 3rd party software packaged with the drivers prohibited it. They weren't even on driver download sites. We used to use it as a hazing ritual to send someone out to find drivers for them because we knew nobody could ever do it no matter where they went or who they called. One day one of the guys took them and used 'em for target practice. Literally.
Hey, at least they're smart enough to see the dollar sign.
RIAA isn't. MPAA isn't.
Congratulations. Over *all* of Slashdot, *you* are the lone member of their target audience.
You clearly have not been on Steam in a long time.
Current library includes:
Call of Duty 1 & 2
Civilization III & IV
Flatout 1 & 2
Psychonauts
Prey
Dark Messiah of Might & Magic
Midevil II: Total War
Dreamfall: The Longest Journey
*And* PopCap games like Bejeweled.
Yes, you can use pseudo-random nonces and pseudo-random session tokens to prevent replay attacks, too, but they have their own caveats. Encryption makes is unreasonable to access data, but authentication makes it unusable.
The point is, in order for two systems to authenticate they must agree on reality. Why would you trust a system that doesn't agree on what time [meaning UTC or unixtime] it is? Agreeing on UTC time is a trivial request for a system to make of another for authentication.
It's like complaining that you can't set your resolution to 2,000,000 x 1. The complaint is not reasonable.
Replay attacks. I capture the data you use to authenticate, and then send it to the server.
This is all I used. Copy-paste-save-copy-paste-save-copy-paste-save, set as startup script for Win2k systems.
It took me all of 20 minutes. Total cost: $0.
UTC timestamps don't have time zones. Rather, they all implicitly use GMT as the time zone. UTC is "the number of seconds since 00:00 Jan 1 1970 GMT" (this is why UTC doesn't technically account for leap seconds). That's an absolute number of seconds no matter where you are in the world. UTC is independent of Earth-based times such as GMT and Universal Time, and, again, this is why UTC doesn't know about leap seconds.
To fix the "future" problem, all Outlook needs to do is:
1. Store UTC on the Exchange server.
2. Allow meeting times to be set with time zone info. So if I'm in Tokyo and I need to set a meeting at 9 am next week New York time, I should get three drop-down boxes: 1: Date, 2: Time, 3: Time zone (with a default of the current locale).
Alternately, they can force UTC time for meeting creation, but that's just as absurd as the current "what's a timezone?" problem.
Are you changing the clock or are you changing the time zone? If you change the clock, you're changing the internal UTC-type clock. If you're changing time zone, you're just affecting how time is displayed. Don't tell the computer that the time has changed. Tell it that you're in a different time zone.
The problem, of course, is that Exchange is not very time-zone aware, particularly with calendar entries.
MS did it right just fine with Active Directory and Windows authentication. The only problem is that *Exchange* doesn't.
Yes, but UTC systems will still display the correct time. They're 100% accurate, they just have the wrong time zone. They will work perfectly well with and agree with patched systems. This is one reason you can login to a server in Cairo from New York: the systems agree that the time is the same. Windows doesn't much care about time zone changes. You'll be able to log in on March 12th whether you're patched or not.
The only problem MS made here is by not using UTC for Exchange calendar entries in the first place. Rather, for using timestamp without time zone, which, frankly, is absurd. Did they not expect email to be a global system?
I've not seen any *nix distro use anything but /home for years, with the exception of the superuser wich always uses /root. The last time I did was about the time Microsoft changed from %windir%\profiles (the Windows NT 4 directory) to Documents and Settings.
/bin, /usr/bin, and /usr/local/bin (and then /sbin and it's contemporaries). It boils down to needing to learn the FHS (http://en.wikipedia.org/wiki/Filesystem_Hierarchy _Standard), and then learning the history of the directories. For example, /opt and /srv are still rather new, so a lot of systems still use /var.
Additionally, you can use the '~' shortcut. '~' is current user's home directory. It's equivalent to %userprofile% in Windows. '~fred' is user fred's home directory. Also, 'cd' with no directory always changes you back to your home directory (it's the same as 'cd ~').
Linux's unified directory structure is very confusing especially compared to the Windows system (everything is a file, logical to physical mapping is not obvious), but home directories are one of the easiest things possible. The most complicated thing for me was figuring out the difference between
If you think about it though, Windows's directories are also rather complex. Windows doesn't install in C:\Windows. It's really in C:\Windows\System32. Program Files is supposed to be read only, and it's one of the reasons so many apps only work when you're an admin. Documents and Settings, while an accurate name, is filled with hidden directories where the OS is trying to keep the user from breaking it, but you still need to get into them from time to time. pagefile.sys is the system pagefile, hiberfil.sys is for hibernation. NTLDR is the bootstrap, and the bootloader is kept in the volume MBR and is completely hidden since all it does is find NTLDR and run it. Most systems have an \i386 directory copied from the CD since Windows wants it from time to time. There's also \RECYCLER which is the recycle bin, and \System Volume Information which contains information Windows itself uses as well as where it store the Restore Points. %userprofile%\NTUSER.DAT is the user's registry hive, while the other registry hives all live in C:\WINDOWS\system32\config. %windir%\system32\config\systemprofile and %documentsandsettings%\.Default user also exists on most systems, containing information on the default profiles. %windir%\system32\drivers is filled with kernel-mode code (real mode, mostly drivers) and %windir%\system32\dllcache contains protected-mode code (user-mode apps). Then there's 5 or 6 different temp directories, and storage locations for Group Policy, security objects, system logs, etc.
IMX, none of that is half as well documented as the Linux stuff.
Probably because it was fun. You'll note that the criticisms he levels can be equally used against nearly every NES cart ever produced, and many people still find those much more enjoyable than the triple-A title shit coming from today's superstudios. Doom didn't do anything that hadn't been done before. It just looked good and was lots of fun.
Nobody is going to buy Vista as boxed retail except bleeding edgers who need DirectX 10. The vast majority will buy a PC within the next few years and it will ship with Vista pre-installed. Microsoft learned how this worked back with Windows 9x.
To most people, a computer is indistinguishable from a microwave or a VCR. The OS might as well be embedded.