The repairability is my main reason for not buying or recommending AIO. Laptops are bad enough, but at least with laptops there's a legitimate reason for it. They need to be small and protable. AIO are kind of questionable as they could just as easily go back to CPUs that lie flat on their side and just change the way that ventilation is done. Set the monitor on top of the CPU and attach clips. There you go. A computer that's very similar to an AIO and a ton easier to repair.
Yeah, I agree. But, to be fair, there are more factors now than back in the '90s when megahertz was the main thing they were improving. AMD doesn't do a perfect job with their processor naming, but they do give you a number to help get an idea of where a particular processor fits in their line of products. Interestingly over the last decade the spread between the number and the frequency has gotten to be rather huge.
GPUs OTOH, I don't think any of the major vendors take that seriously. Trying to figure out why a GPU that has a higher number has lower performance is designed to give people a stroke.
I generally build my own desktops because it's the only way of not getting infested with Intel and Microsoft products and still get a decent rig. The selection of desktops that don't use Intel or MS products is pretty limited. But, by building it myself, I can get what I want without having to give money to monopolists.
That's an easy assumption, but it's not correct. The sites that are blocked will just timed out because the DNS won't connect you, but most of the sites that I observed to be effected would load from time to time, they just took forever to load. And once they did load, there was nothing about China and nothing that they're usually blocking. Sites like the NYT do get blocked, but sites that just carry Chinese lessons and other innocuous content don't normally get blocked.
The main reason for the latency is that China controls access to DNS servers and you're only supposed to use those DNS servers. So, they tend to be over crowded and sites can appear to be blocked, that are just located a long distance away.
Unfortunately, no sarcasm. Breakage is taken from the artist for digital sales. So, while there isn't technically such a thing as a case of MP3s, that doesn't stop the labels from taking money to cover the cost of breakage for an item that's indestructible.
Sort of, what you're failing to account for is that the contracts themselves are crooked and the labels don't generally release the sales figures without being sued. For example, the artist pays for the studio time and the record label gets paid for that again on the back end. The label also frequently gets to charge breakages of discs to the artist, and that includes cases where the case of MP3s was dropped when the movers were taking it out of the truck.
When that happens, the pensioners generally get a small portion of what they were promised, and there are few, if any, consequences for not properly funding the pension plan. Now, if there's fraud involved, the people committing it might end up in a minimum security prison, but the people who were supposed to get the pension are out of luck.
Suggesting that the protections in place are sufficient to guarantee that the obligations are met, is disingenuous as the amount the government pays out after taking over the fund is generally substantially less than what the people getting the pensions were promised.
Indeed. But, even in China where they do filter the internet, there isn't any real throttling that goes down, the main thing I saw when I was there was abysmal latency. It would have the effect of killing of websites that weren't blocked, when the website was expecting to load dozens of scripts from various other servers. Each one would have up to 2.5 seconds of latency attached. And yes, that is seconds, not often, but there were a few times when my ping was measurably with a human timer.
More likely, this is some sort of broken link somewhere along the way that's resulting in the traffic being slowed.
It's because it's designed to look cool. Also, ideally you shouldn't have a computer in your bedroom. Obviously, that's ideal, I know that I have mine in my bed room, because I don't have other options. But, ideally computers shouldn't be where you're sleeping.
The annoying computers are the ones like the one I'm using that put that blue light in a place where it's not easily covered up. My battery charger has a huge blue light on it, but I can easily obscure it by putting a pack of cards or similar item over the top of it. The blue light on my computer is the only visible sign that the computer is on, and is right on the power button, making it hard to cover with sufficient tape to make it not light up the whole room.
The ACPI implementation for Windows has always been rather lenient when it comes to errors that are in the DSDT for a motherboard. It works well now because Linux now contains most of the workarounds as well.
Basically the DSDT that shipped with a lot of the computers from years back wouldn't compile using the Intel compiler, and only under the compiler that MS was using at the time. So, in order to get the ACPI to work correctly, you'd have to decompile the DSDT and reprogram it to compile then you'd have to tell the computer to use that rather than the one on the mother board.
And, it was a tremendous PITA in some cases, in other cases you had to wonder why the developer didn't just spend the extra 5 minutes to get it right.
Standby is there for when you want to leave your desktop applications open and have the benefits of using less energy while you eat dinner or take a walk. Hibernation is great if you need that 0 watts of draw, but don't want to have to have all your programs closed down and to have to start from scratch.
Which is easy for MS to achieve as they're willing to implement a non-standard ACPI implementation rather than using the Intel implementation that everybody else uses. And write work arounds for buggy implementations rather than kick it back to the manufacturer to do correctly.
Linux doesn't have that luxury, which means that DSDT changes and such have to be done by the end user rather than the developer that should have implemented the standard correctly in the first place.
Basically, the kernel has an Application Binary Interface which is a bit like a contract. If the application gives the kernel something formatted in a specific way, the kernal promises to give it back something in a specific way and the other way around. Any software that is written to respect the contract should never be broken by a change to the kernel as the application has no knowledge of how the kernel performs its obligation.
Changes to the ABI are not supposed to be common events. They're supposed to be changed only when lesser changes can't work. FreeBSD handles it using compatibility libraries which maintain the ABI for various kernel revisions so that applications can continue to use older ones if need be. AFAIK, Linux doesn't do that, and as a result, the kernel maintainer and the developers writing the code have to be even more careful about changes made not messing up the ABI.
Also, because Linux is just a kernel without a userland, a change to the Linux kernel that was permitted to break the ABI could hose all of the distros all at once requiring the rewrite of hundreds of little bits of software that are cobbled together to make the distros function as complete OSes.
There's more to it, but that's basically why Linus takes the stance that the kernel is to blame and not the developer. But, he undoubtedly doesn't consider it to be the kernel's fault if a developer does things that don't comply with the normal ABI specifications.
Discrepancies definitely are a risk factor. The safest road is one where nobody is driving at all. The second safest road is where everybody is moving at approximately the same speed with adequate spacing in between them.
The main reason for that being is that the relative speed of the vehicles with respect to each other is approximately zero, which makes for safer maneuvering of the vehicles with respect to each other. It also makes it easier for people getting on and off the street to judge the time they'll need to enter the flow of traffic. As well as for pedestrians to figure out if they're going to have the space necessary to cross safely.
AFAIK, this is something that's been reliably known for years. The speed limit laws in most, if not all parts of the US, have tickets for drivers that drive faster than the speed of traffic or slower than the speed of traffic. And the reason for that is because it's safer for the cars to all drive at a similar speed, provided that speed isn't ridiculously fast.
19k people that might well not have committed suicide had they needed to use a less convenient method of suicide? It's what happened when coal stoves were replaced by natural gas and electric ones. The people who had been committing suicide by coal stove by and large didn't move on to another method and the suicide rates dropped by a similar proportion to the ones represented by coal oven deaths.
19,000 people is a large number it's about a quarter the number of US military personnel who were killed in Vietnam ~58k. It's roughly 1/21 the number of US service personnel that were killed in WWII. And about half as many as are killed on the roads in the US in a typical year.
What's more, the only reason that people need firearms is because other people have firearms. Hunting and target shooting are pretty much the only other reasons, and even those aren't exactly worth the human cost that having a lot of firearms easily accessible leads to.
That happens a lot outside of the developed world. In China I would regularly see 3 or more people on motorcycles and scooters. I even once saw a guy pedaling a bike that had him and 3 kids balanced on it.
Around here you have to score a minimum of 80% on the written test in order to pass and that's been like that for years. Just out of curiosity, how many questions are there on the test where you are? The main criticism I have about our written test is that it's only 25 questions and probably should be more like 50 minimum.
I can say that because nobody does those conversions with any frequency in every day living. If you're even claiming that, it means that you aren't paying attention.
I lived under the metric system for an entire year and not one time did it make anything easier for me. Not even a single conversion during that entire period was made more convenient by using SI units. And many things were less convenient because of the base 10 system they use. The most common conversions like distance into time are equally taxing regardless of whether you're using KMPH and KM or MPH and Miles. In either case you just divide the distance by the speed and you wind up with the same unit.
Weather was annoying because most of the year fluctuated within a 10 degree Celsius window giving less meaningful numbers than I would have had with Fahrenheit. And what's more, because the scale was designed with science in mind, the numbers themselves are far less logical for humans than with Fahrenheit.
In other words, despite all the propaganda out there, the metric system is of no additional value for every day living over Imperial measures and it makes certain things less convenient as the real magic of the metric system is the specially chosen units that make science easier, but have absolutely no connection with everyday living. I found most meat and produce to be sold by the half kilo, because that's a more convenient size to buy things in and coincidentally that's just a little bit more than a pound.
Yes, but it's an article on an American site for a general audience. The mistake isn't that they used feet, the mistake is that they used metric for one and imperial for the other when they should have used feet in both instances.
The people doing the engineering aren't doing it based upon an article written after the devices were engineered and built.
I love how the pro-Metric people mod me down, rather than posing a substantive reason for doing it.
I know the metric system, I've used the metric system and it contributes absolutely nothing in daily living. None of the conversions that it's optimized for occur in daily living with any regularity, whereas I regularly need half of something or 2x as much of it.
Not really, you're ignoring changes in technology. These days it's relatively easy to create a sensor where nearly 100% of the light falling on the chip will hit one of your photosites. A typical dSLR sensor will have magnifiers that cover effectively 100% of the area.
I doubt that the original Hubble was as efficient with the light hitting the sensor as a modern dSLR sensor is. Sure, you do lose some photons in the process, but damn near all of them will hit one of the focusing lenses and be directed into a photosite.
Sort of, the original sensors on the Hubble had very little resolution to them. With modern pixel density you could get much larger photos that could be enlarged to a greater extent. Mirror size does play a role, but when you're talking about replacing the 0.64MP sensors with 12MP sensors, you can pull in a lot more detail with any given size of mirror.
From the looks of the article, it's 90x the repaired hubble's capabilities, which is probably 1/200th of what the Hubble would be able to do had it been launched with modern sensors today. The Hubble itself had 8 0.64MP CCDs to work with. Which at the time was quite good, but even if they used the CCD or CMOS from a low end dSLR, they could probably easily get 20x the pixels.
The repairability is my main reason for not buying or recommending AIO. Laptops are bad enough, but at least with laptops there's a legitimate reason for it. They need to be small and protable. AIO are kind of questionable as they could just as easily go back to CPUs that lie flat on their side and just change the way that ventilation is done. Set the monitor on top of the CPU and attach clips. There you go. A computer that's very similar to an AIO and a ton easier to repair.
Yeah, I agree. But, to be fair, there are more factors now than back in the '90s when megahertz was the main thing they were improving. AMD doesn't do a perfect job with their processor naming, but they do give you a number to help get an idea of where a particular processor fits in their line of products. Interestingly over the last decade the spread between the number and the frequency has gotten to be rather huge.
GPUs OTOH, I don't think any of the major vendors take that seriously. Trying to figure out why a GPU that has a higher number has lower performance is designed to give people a stroke.
I generally build my own desktops because it's the only way of not getting infested with Intel and Microsoft products and still get a decent rig. The selection of desktops that don't use Intel or MS products is pretty limited. But, by building it myself, I can get what I want without having to give money to monopolists.
That's an easy assumption, but it's not correct. The sites that are blocked will just timed out because the DNS won't connect you, but most of the sites that I observed to be effected would load from time to time, they just took forever to load. And once they did load, there was nothing about China and nothing that they're usually blocking. Sites like the NYT do get blocked, but sites that just carry Chinese lessons and other innocuous content don't normally get blocked.
The main reason for the latency is that China controls access to DNS servers and you're only supposed to use those DNS servers. So, they tend to be over crowded and sites can appear to be blocked, that are just located a long distance away.
Unfortunately, no sarcasm. Breakage is taken from the artist for digital sales. So, while there isn't technically such a thing as a case of MP3s, that doesn't stop the labels from taking money to cover the cost of breakage for an item that's indestructible.
Sort of, what you're failing to account for is that the contracts themselves are crooked and the labels don't generally release the sales figures without being sued. For example, the artist pays for the studio time and the record label gets paid for that again on the back end. The label also frequently gets to charge breakages of discs to the artist, and that includes cases where the case of MP3s was dropped when the movers were taking it out of the truck.
When that happens, the pensioners generally get a small portion of what they were promised, and there are few, if any, consequences for not properly funding the pension plan. Now, if there's fraud involved, the people committing it might end up in a minimum security prison, but the people who were supposed to get the pension are out of luck.
Suggesting that the protections in place are sufficient to guarantee that the obligations are met, is disingenuous as the amount the government pays out after taking over the fund is generally substantially less than what the people getting the pensions were promised.
Indeed.
But, even in China where they do filter the internet, there isn't any real throttling that goes down, the main thing I saw when I was there was abysmal latency. It would have the effect of killing of websites that weren't blocked, when the website was expecting to load dozens of scripts from various other servers. Each one would have up to 2.5 seconds of latency attached. And yes, that is seconds, not often, but there were a few times when my ping was measurably with a human timer.
More likely, this is some sort of broken link somewhere along the way that's resulting in the traffic being slowed.
It's because it's designed to look cool. Also, ideally you shouldn't have a computer in your bedroom. Obviously, that's ideal, I know that I have mine in my bed room, because I don't have other options. But, ideally computers shouldn't be where you're sleeping.
The annoying computers are the ones like the one I'm using that put that blue light in a place where it's not easily covered up. My battery charger has a huge blue light on it, but I can easily obscure it by putting a pack of cards or similar item over the top of it. The blue light on my computer is the only visible sign that the computer is on, and is right on the power button, making it hard to cover with sufficient tape to make it not light up the whole room.
Those statistics don't address the point at all.
The ACPI implementation for Windows has always been rather lenient when it comes to errors that are in the DSDT for a motherboard. It works well now because Linux now contains most of the workarounds as well.
Basically the DSDT that shipped with a lot of the computers from years back wouldn't compile using the Intel compiler, and only under the compiler that MS was using at the time. So, in order to get the ACPI to work correctly, you'd have to decompile the DSDT and reprogram it to compile then you'd have to tell the computer to use that rather than the one on the mother board.
And, it was a tremendous PITA in some cases, in other cases you had to wonder why the developer didn't just spend the extra 5 minutes to get it right.
Not true.
Standby is there for when you want to leave your desktop applications open and have the benefits of using less energy while you eat dinner or take a walk. Hibernation is great if you need that 0 watts of draw, but don't want to have to have all your programs closed down and to have to start from scratch.
Which is easy for MS to achieve as they're willing to implement a non-standard ACPI implementation rather than using the Intel implementation that everybody else uses. And write work arounds for buggy implementations rather than kick it back to the manufacturer to do correctly.
Linux doesn't have that luxury, which means that DSDT changes and such have to be done by the end user rather than the developer that should have implemented the standard correctly in the first place.
Basically, the kernel has an Application Binary Interface which is a bit like a contract. If the application gives the kernel something formatted in a specific way, the kernal promises to give it back something in a specific way and the other way around. Any software that is written to respect the contract should never be broken by a change to the kernel as the application has no knowledge of how the kernel performs its obligation.
Changes to the ABI are not supposed to be common events. They're supposed to be changed only when lesser changes can't work. FreeBSD handles it using compatibility libraries which maintain the ABI for various kernel revisions so that applications can continue to use older ones if need be. AFAIK, Linux doesn't do that, and as a result, the kernel maintainer and the developers writing the code have to be even more careful about changes made not messing up the ABI.
Also, because Linux is just a kernel without a userland, a change to the Linux kernel that was permitted to break the ABI could hose all of the distros all at once requiring the rewrite of hundreds of little bits of software that are cobbled together to make the distros function as complete OSes.
There's more to it, but that's basically why Linus takes the stance that the kernel is to blame and not the developer. But, he undoubtedly doesn't consider it to be the kernel's fault if a developer does things that don't comply with the normal ABI specifications.
"Delicacy" is better thought of as a code word for "look at the crazy shit we just fed to that tourist."
Discrepancies definitely are a risk factor. The safest road is one where nobody is driving at all. The second safest road is where everybody is moving at approximately the same speed with adequate spacing in between them.
The main reason for that being is that the relative speed of the vehicles with respect to each other is approximately zero, which makes for safer maneuvering of the vehicles with respect to each other. It also makes it easier for people getting on and off the street to judge the time they'll need to enter the flow of traffic. As well as for pedestrians to figure out if they're going to have the space necessary to cross safely.
AFAIK, this is something that's been reliably known for years. The speed limit laws in most, if not all parts of the US, have tickets for drivers that drive faster than the speed of traffic or slower than the speed of traffic. And the reason for that is because it's safer for the cars to all drive at a similar speed, provided that speed isn't ridiculously fast.
So that's how you rationalize it?
19k people that might well not have committed suicide had they needed to use a less convenient method of suicide? It's what happened when coal stoves were replaced by natural gas and electric ones. The people who had been committing suicide by coal stove by and large didn't move on to another method and the suicide rates dropped by a similar proportion to the ones represented by coal oven deaths.
19,000 people is a large number it's about a quarter the number of US military personnel who were killed in Vietnam ~58k. It's roughly 1/21 the number of US service personnel that were killed in WWII. And about half as many as are killed on the roads in the US in a typical year.
What's more, the only reason that people need firearms is because other people have firearms. Hunting and target shooting are pretty much the only other reasons, and even those aren't exactly worth the human cost that having a lot of firearms easily accessible leads to.
That happens a lot outside of the developed world. In China I would regularly see 3 or more people on motorcycles and scooters. I even once saw a guy pedaling a bike that had him and 3 kids balanced on it.
Around here you have to score a minimum of 80% on the written test in order to pass and that's been like that for years. Just out of curiosity, how many questions are there on the test where you are? The main criticism I have about our written test is that it's only 25 questions and probably should be more like 50 minimum.
I can say that because nobody does those conversions with any frequency in every day living. If you're even claiming that, it means that you aren't paying attention.
I lived under the metric system for an entire year and not one time did it make anything easier for me. Not even a single conversion during that entire period was made more convenient by using SI units. And many things were less convenient because of the base 10 system they use. The most common conversions like distance into time are equally taxing regardless of whether you're using KMPH and KM or MPH and Miles. In either case you just divide the distance by the speed and you wind up with the same unit.
Weather was annoying because most of the year fluctuated within a 10 degree Celsius window giving less meaningful numbers than I would have had with Fahrenheit. And what's more, because the scale was designed with science in mind, the numbers themselves are far less logical for humans than with Fahrenheit.
In other words, despite all the propaganda out there, the metric system is of no additional value for every day living over Imperial measures and it makes certain things less convenient as the real magic of the metric system is the specially chosen units that make science easier, but have absolutely no connection with everyday living. I found most meat and produce to be sold by the half kilo, because that's a more convenient size to buy things in and coincidentally that's just a little bit more than a pound.
Yes, but it's an article on an American site for a general audience. The mistake isn't that they used feet, the mistake is that they used metric for one and imperial for the other when they should have used feet in both instances.
The people doing the engineering aren't doing it based upon an article written after the devices were engineered and built.
I love how the pro-Metric people mod me down, rather than posing a substantive reason for doing it.
I know the metric system, I've used the metric system and it contributes absolutely nothing in daily living. None of the conversions that it's optimized for occur in daily living with any regularity, whereas I regularly need half of something or 2x as much of it.
Not really, you're ignoring changes in technology. These days it's relatively easy to create a sensor where nearly 100% of the light falling on the chip will hit one of your photosites. A typical dSLR sensor will have magnifiers that cover effectively 100% of the area.
I doubt that the original Hubble was as efficient with the light hitting the sensor as a modern dSLR sensor is. Sure, you do lose some photons in the process, but damn near all of them will hit one of the focusing lenses and be directed into a photosite.
Sort of, the original sensors on the Hubble had very little resolution to them. With modern pixel density you could get much larger photos that could be enlarged to a greater extent. Mirror size does play a role, but when you're talking about replacing the 0.64MP sensors with 12MP sensors, you can pull in a lot more detail with any given size of mirror.
From the looks of the article, it's 90x the repaired hubble's capabilities, which is probably 1/200th of what the Hubble would be able to do had it been launched with modern sensors today. The Hubble itself had 8 0.64MP CCDs to work with. Which at the time was quite good, but even if they used the CCD or CMOS from a low end dSLR, they could probably easily get 20x the pixels.