I know that not all Mac users are this fanatical, but 95% of the encounters I've had have been.
That's odd, because I use Macs and I know dozens of other Mac users. I've never experienced anything like you mentioned, even when in the company of Mac and PC users.
I do have a solution for you, though. If you do become a Mac user, and least the rabid fanatics will stop annoying you.
Have you ever seen what kinda of traffic that the Mac network browser generates?
AppleTalk is known for that. Ironically, the chattiness of the protocol also makes it easier to use, because it's more likely to find other computers without any help.
The money is already gone. It was spent on the equipment and labor to upgrade the infrastructure. Plus, $250K - $100K is still $150K, which is much less than the combined salaries of all the employees.
I never said BIOS should be written in C++. I said that BIOS developers should understand OO concepts and more design principles so that they can be applied when appropriate.
And FYI, a typical BIOS is 90% Assembly language and 10% C.
You must have a reading comprehension problem or something, because I agree with you 100%. The BIOS developers I know don't understand OO concepts, so they can't apply them to their programming. The end result is poorly designed code.
I'll take the former, all other things being equal.
But that's my point - all other things were not equal with this bunch. All they knew was how to program hardware in assembly language.
And I think it's inconsistent of you to say that expose to Assembly makes you a better programmer, but exposure to OO languages makes you a worse programmer. A good programmer learns from all the languages he's exposed to. If you're exposed to a language, and it makes you a worse programmer, then you were never a good programer to begin with.
I wasn't talking about adding extra features beyond the spec, I was talking about designing the code so that it can be easily maintained and enhanced, without necessarily being any larger or slower.. Any experienced programmers knows what I'm talking about. It's the difference between a good programmer who can think ahead, and one who can't.
Then those checkmarks were not all created by a single Season Pass. Either you have multiple season passes, a Wishlist, or you checked the epsiodes on the other channels manually. I am 100% positive about this, because it is one of my biggest gripes about the TiVo software.
Check out the TiVo online forums and you'll see what I mean. You can search the archives or just ask about it. Everyone will tell you what I'm telling you: Season Passes are locked to a particular channel.
I used to work as a BIOS developer for one of the major OEMs. I quit after about two years because I couldn't take it any more. The developers just were awful programmers.
The reason why is that they've been working with assembly language for most of their careers, while everyone else was learning advanced techniques like object-oriented design and development, and working on multiple languages (C++, Java, C#, etc). There were a dozen BIOS developers in my department, and I was the only one who lnew object-oriented programming. The only one!
Now, you might be saying, what does OO have to do with BIOS? True, you're not supposed to write OO assembly code, but you are at least supposed to understand the concept, so that you can apply them in some way. The Linux kernel is written like this - the kernel developers know OO concepts, but they use them only where necessary, and the code is still written in C.
I firmly believe that the only reason why these people worked there was because no one could write this code. Writing BIOS is hard, and it's almost impossible to find someone who knows BIOS and modern programming techniques. I remember this one guy who consumed caffeine all day long and was completely wired. He wrote code really fast, but it was all very poorly designed, and none of it was documented. Every time a new feature was added, the guy had to hack it in somehow, because the original code was always written to just what it was supposed to do, no more.
Another reason why they were so bad is that BIOS developers are highly resistant to change. Most of them spend all their time updating the code to support new motherboards, but they would never rewrite anything to improve its design. The majority of code was written back in the 80's, and no one wants to touch it. So this code just sits there, from one version to the next.
What made it more pathetic was that these people were actually better than most BIOS programmers. We would have conference calls with some of these other developers (the company doesn't write the BIOS for all motherboards they sell), and we would ask them technical questions, and they couldn't answer half of them!
The real solution is to rewrite the entire BIOS from scratch, using proper OO techniques, and writing as much code as possible in C. But today's BIOS programmers aren't qualified for that job.
That doesn't mean anything. "View Upcoming Epsidoes" shows episodes on all channels, but the SP itself will only record from one channel. Take a second look, and you'll see what I mean.
As to Palmer's bitch wife? She got what she deserved.
True, but it will cost Palmer the Presidency, which is just stupid. Just like killing off Jack's wife is also stupid.
Of course, there are plenty of plot holes. Like why was Mrs. Bauer allowed to roam CTU unescorted? And why wasn't the surveillance video of Jamie's "suicide" examined earlier? And why are CTU employees allowed to make unmonitored cell phone calls inside the building? Cell phones shouldn't even be working inside that building! These are obvious security holes.
Unless you had a Wishlist for Stargate or created a Season Pass for it on the Sci-Fi channel, it won't be recorded. SPs don't migrate from one channel to the next.
The last 10 minutes of the season finale ruined the whole show for me. I have a hard time believing that a future First Lady could be so stupid, and I don't like the fact that Jack's wife is dead. If they don't resolve these two "issues" in the next episode, I think I'm just going to tune out completely.
There's this thing called Google, maybe you heard of it? There are plenty of free tools for making PDFs on Windows. The most common technique is to use a printer driver - you effectively "print to PDF". I think the Adobe PS drivers can do this.
A) Mozilla is free, so it doesn't generate any revenue for anyone. B) Mozilla doesn't create files, it just displays them, so it's primary purpose is to display other people's documents, not its own.
Can one tell the difference between two binaries compiled at different times / locations if they come from the same source code?
Often, yes. I challenge you to take the kernel source code for your current distribution (e.g. the kernel source RPM for RedHat 7.3), compile it, and generate a binary that exactly matches, byte for byte, the kernel binary that's installed on your system.
You can set a manual record with a TiVo also, that's always been a feature. However, unless you have up-to-date guide data, TiVo "nags" you with "warning" messages every time you try to do something.
Slashdot Mirror
Why don't you get a license plate with some other graphic, and then put a sticker of a mushroom cloud over it?
20% marketshare in a previously untapped market is damn good, I think.
Yes, he does. I thought that was obvious. Anything else, and you get the oxymoron "live recording".
That's odd, because I use Macs and I know dozens of other Mac users. I've never experienced anything like you mentioned, even when in the company of Mac and PC users.
I do have a solution for you, though. If you do become a Mac user, and least the rabid fanatics will stop annoying you.
AppleTalk is known for that. Ironically, the chattiness of the protocol also makes it easier to use, because it's more likely to find other computers without any help.
Does anyone know if it's compatible with the Mac? That would be the only thing stopping me from getting one.
The money is already gone. It was spent on the equipment and labor to upgrade the infrastructure. Plus, $250K - $100K is still $150K, which is much less than the combined salaries of all the employees.
And FYI, a typical BIOS is 90% Assembly language and 10% C.
Because it's distracting, and you have to pay for it.
You must have a reading comprehension problem or something, because I agree with you 100%. The BIOS developers I know don't understand OO concepts, so they can't apply them to their programming. The end result is poorly designed code.
But that's my point - all other things were not equal with this bunch. All they knew was how to program hardware in assembly language.
And I think it's inconsistent of you to say that expose to Assembly makes you a better programmer, but exposure to OO languages makes you a worse programmer. A good programmer learns from all the languages he's exposed to. If you're exposed to a language, and it makes you a worse programmer, then you were never a good programer to begin with.
I wasn't talking about adding extra features beyond the spec, I was talking about designing the code so that it can be easily maintained and enhanced, without necessarily being any larger or slower.. Any experienced programmers knows what I'm talking about. It's the difference between a good programmer who can think ahead, and one who can't.
Check out the TiVo online forums and you'll see what I mean. You can search the archives or just ask about it. Everyone will tell you what I'm telling you: Season Passes are locked to a particular channel.
The reason why is that they've been working with assembly language for most of their careers, while everyone else was learning advanced techniques like object-oriented design and development, and working on multiple languages (C++, Java, C#, etc). There were a dozen BIOS developers in my department, and I was the only one who lnew object-oriented programming. The only one!
Now, you might be saying, what does OO have to do with BIOS? True, you're not supposed to write OO assembly code, but you are at least supposed to understand the concept, so that you can apply them in some way. The Linux kernel is written like this - the kernel developers know OO concepts, but they use them only where necessary, and the code is still written in C.
I firmly believe that the only reason why these people worked there was because no one could write this code. Writing BIOS is hard, and it's almost impossible to find someone who knows BIOS and modern programming techniques. I remember this one guy who consumed caffeine all day long and was completely wired. He wrote code really fast, but it was all very poorly designed, and none of it was documented. Every time a new feature was added, the guy had to hack it in somehow, because the original code was always written to just what it was supposed to do, no more.
Another reason why they were so bad is that BIOS developers are highly resistant to change. Most of them spend all their time updating the code to support new motherboards, but they would never rewrite anything to improve its design. The majority of code was written back in the 80's, and no one wants to touch it. So this code just sits there, from one version to the next.
What made it more pathetic was that these people were actually better than most BIOS programmers. We would have conference calls with some of these other developers (the company doesn't write the BIOS for all motherboards they sell), and we would ask them technical questions, and they couldn't answer half of them!
The real solution is to rewrite the entire BIOS from scratch, using proper OO techniques, and writing as much code as possible in C. But today's BIOS programmers aren't qualified for that job.
That doesn't mean anything. "View Upcoming Epsidoes" shows episodes on all channels, but the SP itself will only record from one channel. Take a second look, and you'll see what I mean.
I don't think that's correct. SPs are definitely tied to a single channel, no matter how or when they were made.
True, but it will cost Palmer the Presidency, which is just stupid. Just like killing off Jack's wife is also stupid.
Of course, there are plenty of plot holes. Like why was Mrs. Bauer allowed to roam CTU unescorted? And why wasn't the surveillance video of Jamie's "suicide" examined earlier? And why are CTU employees allowed to make unmonitored cell phone calls inside the building? Cell phones shouldn't even be working inside that building! These are obvious security holes.
Unless you had a Wishlist for Stargate or created a Season Pass for it on the Sci-Fi channel, it won't be recorded. SPs don't migrate from one channel to the next.
The last 10 minutes of the season finale ruined the whole show for me. I have a hard time believing that a future First Lady could be so stupid, and I don't like the fact that Jack's wife is dead. If they don't resolve these two "issues" in the next episode, I think I'm just going to tune out completely.
I could have sworn that Gopher was around before 1990.
There's this thing called Google, maybe you heard of it? There are plenty of free tools for making PDFs on Windows. The most common technique is to use a printer driver - you effectively "print to PDF". I think the Adobe PS drivers can do this.
A) Mozilla is free, so it doesn't generate any revenue for anyone. B) Mozilla doesn't create files, it just displays them, so it's primary purpose is to display other people's documents, not its own.
I heard that wasn't true any more.
Often, yes. I challenge you to take the kernel source code for your current distribution (e.g. the kernel source RPM for RedHat 7.3), compile it, and generate a binary that exactly matches, byte for byte, the kernel binary that's installed on your system.
You can set a manual record with a TiVo also, that's always been a feature. However, unless you have up-to-date guide data, TiVo "nags" you with "warning" messages every time you try to do something.