And how many years before 9/11 did we go without a terrorist act? And how many years before that were we hit by a terrorist act enacted by people who are not American citizens?
So how do you come to the conclusion that the Patriot Act works?
What, you want them to make a huge potentially destabilizing change to a mostly stable os to fix an RPC bug on a port you shouldn't make available to the outside world anyway?
From a risk analasys perspective, as an NT4 admin I wouldn't want to apply the fix even if they did have one.
The gamut (range of colors capable of being displayed; kind of like the difference between 16 and 24 bit color) of an LCD monitor is also smaller than that of a CRT, which certainly doesn't help things either...
I'm not quite sure how the lawsuit turned out, but the result is that contract workers are only allowed to work for MS for 9-10 months at a time. After which they are required to work at a different company for a certain period of time before becoming elidgable to work at MS again...
Tivo has "unofficial" ethernet support built in -- you basically enter in a dialing code that the Tivo interprets as "use a network interface instead". There are several USB ethernet devices that work on the Series 2 units. There are also a few different devices that plug into the edge connector on the series 1 units, including one with 802.11b support.
If connectivity is the only thing holding you back from getting a Tivo, and you don't mind spending a few extra bucks to set it up to use your LAN, it isn't a problem.
Say you have 10 applications. And say you have 3 DLLs. In the GAC, you'll have
Dll version 1 Dll version 1.1 Dll version 2
You'll have 3 copies of the DLL. Not one copy for each application.
Additionally, which dll you use will depend on how your app is written. IE: You can still write your app to use the "newest" version of the DLL. Or you could write it to use newer versions only. Or you could write it so that it will use any version it finds. Or you could write it to use only a specific version.
This stuff only works with.NET applications. All of the "legacy" DLLs that this effects today will still have problems. In fact, I'm not quite sure what they changed in.NET 1.1, because what the article describes is pretty much how it works with.NET assemblies today...
The second reason is the damn heat-sink and fan is on the bottom of the card. I'll never figure this one out, but why did the hardware enginers do this? The heat from the heatsink rises back into the card and makes the ambient temp even hotter. Most people leave PCI 1 open to help dissapate this heat.
Hot air rises. Heat radiates outward.
Ie: The efficiency of a heatsink is not altered by it's orientation.
"But the hot air gets stuck under the card!"
Unless the temperature of the air contained within your case varies significantly (which it doesn't with a normal case with a couple of fans sucking air through it), orientation of the heatsink/fan does not matter. Your case doesn't have a mini atmosphere inside of it with updrafts and downdrafts.
The reason why the.NET platform is very important for Microsoft (and for that matter, those who write software which words in a Windows enviornment) will become very apparent when 64bit CPUs from both AMD and Intel hit the market.
While AMD's 64bit chip will be backwards compatible with 32bit x86 CPUs on an instruciton level, the 64bit instructions will not be compatible with Intels version. And Intel's 64bit CPU is deathly slow emulating 32bit code. So a developer "needs" to write at least 2 versions (an Intel 64bit version, and an x86 32bit version) and probably a 64bit AMD version if their stuff ever catches on.
That sucks. Sure, you might be able to just flip a few switches on the compiler and make a second binary, but that sucks. Or have the compiler run different bits of code depending on what CPU it's running with (similar to how SSE/3dnow stuff is done) but that sucks too. And when the NEXT platform comes out, you've got to recompile code again. And that really sucks..NET is "Java the Microsoft way". It isn't meant to be platform and OS independant the way Java is. It's meant to be platform independant and OS dependant. And while this kind of utility isn't very apparent right now, nor do I know if this is the reason why MS decided to compile binaries in a manner similar to java, I have a feeling that it will be very significant in Microsoft's future.
TiVo is very open about what kind of data they collect (data which is not linked to specific users), and provide an easy way to opt out of that collection process.
The fact that you can record video on a pc means nothing to me -- a Tivo is nothing but a really low end computer running linux -- but you don't get a Tivo just to record tv. Saying "my computer with a video capture card does the same thing" is like saying that "my ford escort is just as good for a 2000 mile treck across the country as luxury sedan". They both get the job done. One is just a hell of a lot nicer than the other.
Even after starting with a very small sample of messages to define each bucket, the accuracy of determinations was suprising. Over the last week or so I've been correcting it on the emails it gets wrong. It's accuracy has been increasing dramatically. I havn't had to correct any assessments for the last 2 days.
What has probably happened is that you've got a lot of stuff thumbed down, but very few things thumbed up. You may want to examine the guide listing for shows that you like (but generally don't watch).
Unfortunately, "good writing" is a subjective thing.
The Tivo does use a collaborative suggestion engine though, which is probably about as close to that concept we'll ever see in our lifetime...
By collaborative, I mean that the unit will gather profiles from other users of the Tivo service and make suggestions based on what other people who like the same stuff you like prefer. This isn't the only input in the suggestion engine, but it is one of them...
You don't have to go out of your way. The people described in the article are idiots. If you don't like a suggestion, you give it a thumbs down. This tells the tivo that you didn't like it. Imagine that.
You don't go searching through the guide listing finding programs that seem like the opposite of the suggestion you didn't like. Why? Because the Tivo doesn't know that you didn't like the suggestion it recorded.
When you first get a tivo the suggestions are pretty bad. This is reasonable; the unit doesn't have much data to go off of. Use it for a month or two using the thumbs up/down ratings properly, and the suggestions are pretty good. When I run out of "normal" tv to watch, I can scroll down to the recorded suggestions and 9 times out of 10 there will be something down there that I want to watch. The other 1/10th of the time there is something down there that I would normally watch but am not in the mood for...
If you want the quality of suggestions to improve, give your TiVo some feedback. If it records a suggestion you don't like, give it a thumbs down. If it records one you do like, give it a thumbs up.
It's a piece of hardware with software written by human beings. It isn't empathic. All it knows at this point is that you like the simpsons, soprano's, and iron chef. So obviously with what little it knows the unit is hypothesizing that you like cartoons, cooking shows, and mob based tv shows. Shouldn't be terribly surprising when you get random cartoon and cooking shows recorded as suggestions.
If you don't want suggestions at all, it's incredibly easy to turn them off.
Unless you've got your router setup to allow you to configure it remotely (ie: on the cablemodem side of the network; aka, while you're at your friends house). If you've done this, odds are this problem is the least of your concerns.
And there's already a firmware fix for it, should you be concerned that any script kiddies living in your house will want to hose their connection to the outside world...
There is the "ideal" case, which is what you describe, and what the rest of the world actually does.
You may not care about controlling the placement of every pixel on the screen, but you do want to have some vague control over the layout of the screen. When your widgets are different for each platform, your layout suddenly becomes different for each platform.
When you develop a web page, you don't go "ok, this is 100% complaint code, all browsers will render this and my client will be happy." Instead, you develop a web page, then load it on every known browser in existance (or, at least the ones you think your customers will use). Then you tweak the code until it renders the way your client wants it to look on every browser in existance.
This really really sucks. And no amount of standing on a soapbox insisting that "it'll be ok because it's only supposed to be a guide, and the way every browser handles it will be ok" will change that fact that people want it to look good on all browsers, not just the one that supports features a, b, and c.
The way Mozilla handles it, they just axed about 3 different platforms you'd have to do tweaking and testing on to make the pointy haired boss type people happy. And when you get right down it, the decision was a choice between two evils, and they took the lesser of the two IMO.
They did it so that a web page that is rendered in Linux looks the same as page rendered in OS X or Windoze... Ie: if you use native widgets you have no guarantees that the web form you made will look consistant across platforms.
Thats the general idea at any rate...
An added benefit is that you greatly reduce platform specific browser bugs.
That's funny, because every single AMD chip I've ever seen is still running without problems.
"pre overclocked" my ass; overclocking is making the CPU run faster than it came from the factory; by definition a chip cannot be overclocked from the factory. Gotta love the FUD spread by Intel zeleots. Of course, the poster will probably reply that AMD raised the voltage used by the chip at some point, to which I'd respond "so does Intel"...but of course, since intel does it, it doesn't count...
Slashdot Mirror
And how many years before 9/11 did we go without a terrorist act? And how many years before that were we hit by a terrorist act enacted by people who are not American citizens?
So how do you come to the conclusion that the Patriot Act works?
What, you want them to make a huge potentially destabilizing change to a mostly stable os to fix an RPC bug on a port you shouldn't make available to the outside world anyway?
From a risk analasys perspective, as an NT4 admin I wouldn't want to apply the fix even if they did have one.
My Polk Audio PSW550 subwoofer has a volume dial which goes to 11... :)
The gamut (range of colors capable of being displayed; kind of like the difference between 16 and 24 bit color) of an LCD monitor is also smaller than that of a CRT, which certainly doesn't help things either...
I think cost would be more related to die size and yields more than anything else...
I'm not quite sure how the lawsuit turned out, but the result is that contract workers are only allowed to work for MS for 9-10 months at a time. After which they are required to work at a different company for a certain period of time before becoming elidgable to work at MS again ...
Tivo has "unofficial" ethernet support built in -- you basically enter in a dialing code that the Tivo interprets as "use a network interface instead". There are several USB ethernet devices that work on the Series 2 units. There are also a few different devices that plug into the edge connector on the series 1 units, including one with 802.11b support.
If connectivity is the only thing holding you back from getting a Tivo, and you don't mind spending a few extra bucks to set it up to use your LAN, it isn't a problem.
That's not how it works.
.NET applications. All of the "legacy" DLLs that this effects today will still have problems. In fact, I'm not quite sure what they changed in .NET 1.1, because what the article describes is pretty much how it works with .NET assemblies today...
Say you have 10 applications. And say you have 3 DLLs. In the GAC, you'll have
Dll version 1
Dll version 1.1
Dll version 2
You'll have 3 copies of the DLL. Not one copy for each application.
Additionally, which dll you use will depend on how your app is written. IE: You can still write your app to use the "newest" version of the DLL. Or you could write it to use newer versions only. Or you could write it so that it will use any version it finds. Or you could write it to use only a specific version.
This stuff only works with
Essentially, they are. It's called Longhorn.
The second reason is the damn heat-sink and fan is on the bottom of the card. I'll never figure this one out, but why did the hardware enginers do this? The heat from the heatsink rises back into the card and makes the ambient temp even hotter. Most people leave PCI 1 open to help dissapate this heat.
Hot air rises. Heat radiates outward.
Ie: The efficiency of a heatsink is not altered by it's orientation.
"But the hot air gets stuck under the card!"
Unless the temperature of the air contained within your case varies significantly (which it doesn't with a normal case with a couple of fans sucking air through it), orientation of the heatsink/fan does not matter. Your case doesn't have a mini atmosphere inside of it with updrafts and downdrafts.
The reason why the .NET platform is very important for Microsoft (and for that matter, those who write software which words in a Windows enviornment) will become very apparent when 64bit CPUs from both AMD and Intel hit the market.
.NET is "Java the Microsoft way". It isn't meant to be platform and OS independant the way Java is. It's meant to be platform independant and OS dependant. And while this kind of utility isn't very apparent right now, nor do I know if this is the reason why MS decided to compile binaries in a manner similar to java, I have a feeling that it will be very significant in Microsoft's future.
While AMD's 64bit chip will be backwards compatible with 32bit x86 CPUs on an instruciton level, the 64bit instructions will not be compatible with Intels version. And Intel's 64bit CPU is deathly slow emulating 32bit code. So a developer "needs" to write at least 2 versions (an Intel 64bit version, and an x86 32bit version) and probably a 64bit AMD version if their stuff ever catches on.
That sucks. Sure, you might be able to just flip a few switches on the compiler and make a second binary, but that sucks. Or have the compiler run different bits of code depending on what CPU it's running with (similar to how SSE/3dnow stuff is done) but that sucks too. And when the NEXT platform comes out, you've got to recompile code again. And that really sucks.
TiVo is very open about what kind of data they collect (data which is not linked to specific users), and provide an easy way to opt out of that collection process.
The fact that you can record video on a pc means nothing to me -- a Tivo is nothing but a really low end computer running linux -- but you don't get a Tivo just to record tv. Saying "my computer with a video capture card does the same thing" is like saying that "my ford escort is just as good for a 2000 mile treck across the country as luxury sedan". They both get the job done. One is just a hell of a lot nicer than the other.
I just started using it about a week ago.
Even after starting with a very small sample of messages to define each bucket, the accuracy of determinations was suprising. Over the last week or so I've been correcting it on the emails it gets wrong. It's accuracy has been increasing dramatically. I havn't had to correct any assessments for the last 2 days.
I'm not sure how the algorithm works, but if you don't want the engine to think that you like a particular show, don't give it a thumbs up...
What has probably happened is that you've got a lot of stuff thumbed down, but very few things thumbed up. You may want to examine the guide listing for shows that you like (but generally don't watch).
Unfortunately, "good writing" is a subjective thing.
The Tivo does use a collaborative suggestion engine though, which is probably about as close to that concept we'll ever see in our lifetime...
By collaborative, I mean that the unit will gather profiles from other users of the Tivo service and make suggestions based on what other people who like the same stuff you like prefer. This isn't the only input in the suggestion engine, but it is one of them...
You don't have to go out of your way. The people described in the article are idiots. If you don't like a suggestion, you give it a thumbs down. This tells the tivo that you didn't like it. Imagine that.
You don't go searching through the guide listing finding programs that seem like the opposite of the suggestion you didn't like. Why? Because the Tivo doesn't know that you didn't like the suggestion it recorded.
When you first get a tivo the suggestions are pretty bad. This is reasonable; the unit doesn't have much data to go off of. Use it for a month or two using the thumbs up/down ratings properly, and the suggestions are pretty good. When I run out of "normal" tv to watch, I can scroll down to the recorded suggestions and 9 times out of 10 there will be something down there that I want to watch. The other 1/10th of the time there is something down there that I would normally watch but am not in the mood for...
If you want the quality of suggestions to improve, give your TiVo some feedback. If it records a suggestion you don't like, give it a thumbs down. If it records one you do like, give it a thumbs up.
It's a piece of hardware with software written by human beings. It isn't empathic. All it knows at this point is that you like the simpsons, soprano's, and iron chef. So obviously with what little it knows the unit is hypothesizing that you like cartoons, cooking shows, and mob based tv shows. Shouldn't be terribly surprising when you get random cartoon and cooking shows recorded as suggestions.
If you don't want suggestions at all, it's incredibly easy to turn them off.
Unless you've got your router setup to allow you to configure it remotely (ie: on the cablemodem side of the network; aka, while you're at your friends house). If you've done this, odds are this problem is the least of your concerns.
And there's already a firmware fix for it, should you be concerned that any script kiddies living in your house will want to hose their connection to the outside world...
Doesn't effect the ability, but does effect the appearance...
There is the "ideal" case, which is what you describe, and what the rest of the world actually does.
You may not care about controlling the placement of every pixel on the screen, but you do want to have some vague control over the layout of the screen. When your widgets are different for each platform, your layout suddenly becomes different for each platform.
When you develop a web page, you don't go "ok, this is 100% complaint code, all browsers will render this and my client will be happy." Instead, you develop a web page, then load it on every known browser in existance (or, at least the ones you think your customers will use). Then you tweak the code until it renders the way your client wants it to look on every browser in existance.
This really really sucks. And no amount of standing on a soapbox insisting that "it'll be ok because it's only supposed to be a guide, and the way every browser handles it will be ok" will change that fact that people want it to look good on all browsers, not just the one that supports features a, b, and c.
The way Mozilla handles it, they just axed about 3 different platforms you'd have to do tweaking and testing on to make the pointy haired boss type people happy. And when you get right down it, the decision was a choice between two evils, and they took the lesser of the two IMO.
They did it so that a web page that is rendered in Linux looks the same as page rendered in OS X or Windoze... Ie: if you use native widgets you have no guarantees that the web form you made will look consistant across platforms.
Thats the general idea at any rate...
An added benefit is that you greatly reduce platform specific browser bugs.
And battlesphere WAS released (albiet in limited quantities).
So we'll end up having to rocket jump into orbit...destroying a large portion of Florida in the process.
Hmm, might not be such a bad idea afterall...;)
That's funny, because every single AMD chip I've ever seen is still running without problems.
"pre overclocked" my ass; overclocking is making the CPU run faster than it came from the factory; by definition a chip cannot be overclocked from the factory. Gotta love the FUD spread by Intel zeleots. Of course, the poster will probably reply that AMD raised the voltage used by the chip at some point, to which I'd respond "so does Intel"...but of course, since intel does it, it doesn't count...