The same tired argument comes up every time the government adds a new safety standard because X number of preventable deaths occurred. Free market advocates say, "Well the market should sort out whether a safety feature is added!" And sometimes they even rehash the tired, "But people will drive safer if they know they could die at any moment!" argument. The former never happens, it just never does. You can wait until the end of time, the only people who choose to pay for safety, even if ends up reducing costs for everyone, are a small informed minority. The rest of everyone will buy what happens to be on the lot, or whatever the salesman can make the best pitch for.
IMO, this should be considered a form of market failure and be acted on. If you buy a game in which the feature could be disabled by a third party at any time, don't you have at least some right to use that feature regardless of what they do? What would it cost them to release the server component source code and let the internet figure out how to use it?
Ogginfo's source includes information on how to process the metadata for various codecs.
So, the grandparent's complaint is still valid. Ogginfo appears to require recompilation for every stream that they want to support inside an ogg container.
The majority of the Senate voted to block funds necessary to transfer detainees. The Republicans then made a huge deal about it and turned into a political nightmare. Obama has pressed forward with preparing facilities in the US and on trials, regardless.
Given how quickly almost all of the Senate blocked the transfer of prisoners, I think he's doing quite well. Unfortunately, the President can scoff at Congress' decisions only to a certain degree, and it takes a lot of legal wrangling to get around Congress denying funding for transferring inmates.
If your code is internal use only, then you're not violating the GPL. If your code is leaving your company, you're selling it to someone else, etc, then you are violating the GPL.
Apparently if HTC simply "frees their code" for their thousands of phones, maintainers will come out of the woodwork to keep them up to date for HTC. And HTC will never have to worry about it again...
For now, at least. VMWare doesn't support combining pages >= 2MB because the overhead (hit rate on finding duplicates versus the cost of searching for duplicates) and I suspect other hypervisors will do the same. Additionally, Intel and AMD are both moving to support 1GB page tables. What are the odds that you'll start up two VMs and their first 1GB of memory will remain identical for very long?
The only way I see page sharing working in the future is if the hypervisor inspects the nested pages down to the VM level, which will typically be the 4KB pages we know and love. Either that, or paravirtualization support needs to exist for loading common code and objects into a shared pool.
Even so, there's a lot of overhead from inspecting (hashing and then comparing) pages which will only grow as memory sizes grow. If we increase page sizes, the hit rate decreases and the overhead of copy-on-write increases. It's not a good situation.
In ESX Server 3.5 and ESX Server 3i v3.5, large pages cannot be shared as copyonwrite pages. This means, the ESX Server page sharing technique might share less memory when large pages are used instead of small pages. In order to recover from nonsharable large pages, ESX Server uses a “sharebeforeswap” technique. When free machine memory is low and before swapping happens, the ESX Server kernel attempts to share identical small pages even if they are parts of large pages. As a result, the candidate large pages on the host machine are broken into small pages. In rare cases, you might experience performance issues with large pages. If this happens, you can disable large page support for the entire ESX Server host or for the individual virtual machine.
That is, page sharing involves breaking up large pages, negating their performance benefit and is only used as a last ditch when you've overcommited memory and you're nearly to the point of having to hit the disk. And VMWare overcommit is great until you hit the disk, then it's a nightmare.
Not set in stone, but less volatile than "every other release needs some minor fixup." That's all.
For example, we're currently on 2.6.33.2. Why not standardize on an ABI for the minor version number? 2.6 versus 2.8 for example. (Or since they switched development pattern, will 2.7 be a legit release? I don't know.)
The problem is that the volatility is so high that kernel drivers need 24/7 maintenance, or else they're dropped and then it becomes even harder to re-integrate them. Ask Microsoft about their paravirtualization drivers. They've submitted two or three versions to the kernel, and each time you had to use the specific version of the kernel that they compiled them on, or it didn't work. That's the problem. Linux. Isn't. Free. Microsoft is however eventually going to have to come to a sad realization: it may cost them a salaried employee and benefits just to maintain these drivers. That's ridiculous. If it's difficult for Microsoft to justify targeting Linux, how is a small business going to justify putting 1/10 of its development staff on it? 1/20?
It's insane. Linux is such a "me me me" culture where everything revolves around the sanctity of the kernel and how free and open it is, and no one appears to consider the ramifications of the actions.
The fact is, the Linux kernel will fix these problems or Android will fork, or HTC, Nokia, et al. will do it for them. And then Android will be fragmented, and we'll be back to considering iPhones and BlackBerry phones the best in the world, each with their horrendous lock-in. With one, I have to code in The One True Language, and with the other, I have to make sure my clients are using The One True Message Server. As soon as Android isn't viable, they're the best options. That's sad.
Those proprietary drivers still have to be maintained against the rest of the kernel, and that costs time, and consequently money.
Furthermore, many of these devices are protected by patents, and I'm sure you don't want code for a special model of capacitive multi-touch screen that only one phone uses to be added to the general Linux kernel. There's no point in it.
So that's the problem. All these phones have highly specialized devices that may be protected by patents that in Europe have no weight, but in the US do, and could cause problems for the linux kernel potentially even if they were introduced. Add to that the fact that for many of these devices a generic, unifying framework doesn't exist that they can attach themselves too, and you could end up seeing the kernel with ten thousand different phone drivers, each of them so specific that all it does is bloat the kernel.
So what's the answer? Well, the answer is that if Linux doesn't start building a good ABI, they're going to shoot themselves in the foot, or more literally, they'll end up sawing off their own leg because it decided to fork itself. And for all the babbling the kernel devs do about the difficulty of maintaining an ABI and how it constrains them, it also makes it very difficult for the generic, current Linux kernel to gain widespread adoption in markets that resemble embedded ones in all but name. What is HTC supposed to do, keep people on payroll perpetually to maintain their thousand plus phones and their potentially tens of thousands of drivers?
Suddenly, Linux is starting to look a lot more expensive than free.
I appreciate the attempt at ad hominem, but it's not merely "pragmatic" to accept that we have a precarious economy that would not take well the loss of a significant number of jobs. Do I think the insurance companies should eventually go the way of the dodo? Yes. Do I think health care reform was needed now? Yes. Do I think that if we implemented single payer and made the insurance companies go away in one fell swoop, it'd deal an enormous blow to a large part of our economy? Yes.
So how do you recommend we reconcile those, or would you answer differently to any of those questions?
So why don't you actually read the bill? It's posted online. It's complex, it deals within the existing framework of other bills delineating medicare, medicaid, veteran's health care, etc. Because it operates within that context, many parts of the bill are long, complex amendments to previous bills.
I hope my generation is the first one to introduce the idea of "version control" into the legal system, don't get me wrong. I think the laws are too complex as it is and could be more simply described. But health care is a complex issue, and frankly, I read the Canada Health Act, and it doesn't specify a whole lot. If we were to enact something like that, we'd be throwing out the existing system entirely and it'd cost a lot of jobs too, at a time when we can't afford to hemorrhage those jobs. I think that's part of why Congress wanted to act in the current framework of health care insurers. And yes, I'm fully aware of the broken window fallacy. I realize that these jobs may ultimately not be necessary, but now is not a good time to get rid of them.
Exactly the same, ignoring all the surrounding politics. I'm sure our bill would be simpler too if we simply did single payer as well. But Congress chose to maintain the existing system as much as possible and transition to a new system by 2014.
Everyone says these drives get 300-400IOPS peak. An Intel SSD will get you 8,000-12,000 easy, and the X25-E model will get you 15,000-20,000 easy. To compare:
That's the top two SSDs in the market, using Intel's controller and Sandforce's controller. For reads and a large request size the limitation is the SATA bus, you'll notice that each SSD maxes out the bus at 260MB/s. For small reads, it gets increasingly more ridiculous.
Four 600GB velociraptors in RAID0: $1120 and approximately 1200 IOPS. For 1.07IOPS/$. One X25-M or Sandforce SSD in the 80-120GB range: $300 and approximately 8000 IOPS. For 26.67IOPS/$. IOPS actually grows as block size decreases, and both the X25-M and Sandforce SSDs see more than double the performance for 512B requests.
That's not the definition of a monopoly, or even what's wrong with being one.
There's nothing illegal with being a monopoly, but using your enormous market share to affect other markets, hurt potential competitors, etc, those things are illegal.
Health care is complex and there are dozens of other bills that make up the health care regulation we have now. Not only that, but legislators use ridiculous margins, double or triple spaced text and large fonts.
So not only is it shorter than you think it is, but it deals with issues more complex than you're willing to admit.
Shouldn't be 24/7. Modern S3 sleep is very efficient and works well with timers. Using Windows as an HTPC with sleep enabled will let the PC go to sleep, wake up to record, and then sleep again.
Powershell support with proper verb-noun command structure and piping support?
I'm disappointed that I even have to add the last bit, but Powershell stuff from Microsoft differs greatly on supporting the implicit standards. There are some modules and snapins that are really good, there are some that are... not so much.
Slashdot Mirror
The same tired argument comes up every time the government adds a new safety standard because X number of preventable deaths occurred. Free market advocates say, "Well the market should sort out whether a safety feature is added!" And sometimes they even rehash the tired, "But people will drive safer if they know they could die at any moment!" argument. The former never happens, it just never does. You can wait until the end of time, the only people who choose to pay for safety, even if ends up reducing costs for everyone, are a small informed minority. The rest of everyone will buy what happens to be on the lot, or whatever the salesman can make the best pitch for.
IMO, this should be considered a form of market failure and be acted on. If you buy a game in which the feature could be disabled by a third party at any time, don't you have at least some right to use that feature regardless of what they do? What would it cost them to release the server component source code and let the internet figure out how to use it?
Ah, the gotcha is in the source:
http://svn.xiph.org/trunk/vorbis-tools/ogginfo/ogginfo2.c
Ogginfo's source includes information on how to process the metadata for various codecs.
So, the grandparent's complaint is still valid. Ogginfo appears to require recompilation for every stream that they want to support inside an ogg container.
It looks like it's depending on the information from each codec though. What happens if you don't have one of the codecs installed?
Some overseas news sources, such as the BBC, use a style guide that does make it "Nasa" not "NASA".
The word you're looking for, when trying to describe what happens when you unload a live DLL, is "interesting".
Here, like this:
No, because of politics. I think that's plain to see, when 96 Senators voted against funding the transfer of Gitmo detainees.
Ok, so he puts them on a plane, where does he send them? That's what the funding was for.
Don't. Do. Nothing.
The majority of the Senate voted to block funds necessary to transfer detainees. The Republicans then made a huge deal about it and turned into a political nightmare. Obama has pressed forward with preparing facilities in the US and on trials, regardless.
Also, do I need to post sources or are we just ignoring those now? Here's the senate block, here's Obama pressing forward with a memorandum.
Given how quickly almost all of the Senate blocked the transfer of prisoners, I think he's doing quite well. Unfortunately, the President can scoff at Congress' decisions only to a certain degree, and it takes a lot of legal wrangling to get around Congress denying funding for transferring inmates.
You're right, he did surround himself with a lot of former intellectual property "advocates". It's disappointing.
On the other hand, he's had an amazing first year.
If your code is internal use only, then you're not violating the GPL. If your code is leaving your company, you're selling it to someone else, etc, then you are violating the GPL.
Apparently if HTC simply "frees their code" for their thousands of phones, maintainers will come out of the woodwork to keep them up to date for HTC. And HTC will never have to worry about it again...
That's a good fairytale, do you have any more?
For now, at least. VMWare doesn't support combining pages >= 2MB because the overhead (hit rate on finding duplicates versus the cost of searching for duplicates) and I suspect other hypervisors will do the same. Additionally, Intel and AMD are both moving to support 1GB page tables. What are the odds that you'll start up two VMs and their first 1GB of memory will remain identical for very long?
The only way I see page sharing working in the future is if the hypervisor inspects the nested pages down to the VM level, which will typically be the 4KB pages we know and love. Either that, or paravirtualization support needs to exist for loading common code and objects into a shared pool.
Even so, there's a lot of overhead from inspecting (hashing and then comparing) pages which will only grow as memory sizes grow. If we increase page sizes, the hit rate decreases and the overhead of copy-on-write increases. It's not a good situation.
Sources: Performance Best Practices for vSphere 4 which references Large Page Performance which states:
That is, page sharing involves breaking up large pages, negating their performance benefit and is only used as a last ditch when you've overcommited memory and you're nearly to the point of having to hit the disk. And VMWare overcommit is great until you hit the disk, then it's a nightmare.
Not set in stone, but less volatile than "every other release needs some minor fixup." That's all.
For example, we're currently on 2.6.33.2. Why not standardize on an ABI for the minor version number? 2.6 versus 2.8 for example. (Or since they switched development pattern, will 2.7 be a legit release? I don't know.)
The problem is that the volatility is so high that kernel drivers need 24/7 maintenance, or else they're dropped and then it becomes even harder to re-integrate them. Ask Microsoft about their paravirtualization drivers. They've submitted two or three versions to the kernel, and each time you had to use the specific version of the kernel that they compiled them on, or it didn't work. That's the problem. Linux. Isn't. Free. Microsoft is however eventually going to have to come to a sad realization: it may cost them a salaried employee and benefits just to maintain these drivers. That's ridiculous. If it's difficult for Microsoft to justify targeting Linux, how is a small business going to justify putting 1/10 of its development staff on it? 1/20?
It's insane. Linux is such a "me me me" culture where everything revolves around the sanctity of the kernel and how free and open it is, and no one appears to consider the ramifications of the actions.
The fact is, the Linux kernel will fix these problems or Android will fork, or HTC, Nokia, et al. will do it for them. And then Android will be fragmented, and we'll be back to considering iPhones and BlackBerry phones the best in the world, each with their horrendous lock-in. With one, I have to code in The One True Language, and with the other, I have to make sure my clients are using The One True Message Server. As soon as Android isn't viable, they're the best options. That's sad.
I will. My emails are important, I make sure each of them has the red exclamation mark and flag.
Those proprietary drivers still have to be maintained against the rest of the kernel, and that costs time, and consequently money.
Furthermore, many of these devices are protected by patents, and I'm sure you don't want code for a special model of capacitive multi-touch screen that only one phone uses to be added to the general Linux kernel. There's no point in it.
So that's the problem. All these phones have highly specialized devices that may be protected by patents that in Europe have no weight, but in the US do, and could cause problems for the linux kernel potentially even if they were introduced. Add to that the fact that for many of these devices a generic, unifying framework doesn't exist that they can attach themselves too, and you could end up seeing the kernel with ten thousand different phone drivers, each of them so specific that all it does is bloat the kernel.
So what's the answer? Well, the answer is that if Linux doesn't start building a good ABI, they're going to shoot themselves in the foot, or more literally, they'll end up sawing off their own leg because it decided to fork itself. And for all the babbling the kernel devs do about the difficulty of maintaining an ABI and how it constrains them, it also makes it very difficult for the generic, current Linux kernel to gain widespread adoption in markets that resemble embedded ones in all but name. What is HTC supposed to do, keep people on payroll perpetually to maintain their thousand plus phones and their potentially tens of thousands of drivers?
Suddenly, Linux is starting to look a lot more expensive than free.
I appreciate the attempt at ad hominem, but it's not merely "pragmatic" to accept that we have a precarious economy that would not take well the loss of a significant number of jobs. Do I think the insurance companies should eventually go the way of the dodo? Yes. Do I think health care reform was needed now? Yes. Do I think that if we implemented single payer and made the insurance companies go away in one fell swoop, it'd deal an enormous blow to a large part of our economy? Yes.
So how do you recommend we reconcile those, or would you answer differently to any of those questions?
So why don't you actually read the bill? It's posted online. It's complex, it deals within the existing framework of other bills delineating medicare, medicaid, veteran's health care, etc. Because it operates within that context, many parts of the bill are long, complex amendments to previous bills.
I hope my generation is the first one to introduce the idea of "version control" into the legal system, don't get me wrong. I think the laws are too complex as it is and could be more simply described. But health care is a complex issue, and frankly, I read the Canada Health Act, and it doesn't specify a whole lot. If we were to enact something like that, we'd be throwing out the existing system entirely and it'd cost a lot of jobs too, at a time when we can't afford to hemorrhage those jobs. I think that's part of why Congress wanted to act in the current framework of health care insurers. And yes, I'm fully aware of the broken window fallacy. I realize that these jobs may ultimately not be necessary, but now is not a good time to get rid of them.
Exactly the same, ignoring all the surrounding politics. I'm sure our bill would be simpler too if we simply did single payer as well. But Congress chose to maintain the existing system as much as possible and transition to a new system by 2014.
He doesn't care about that, he wants random access performance.
And yes, your RAID0 of four Velociraptor drives will have pitiful performance.
Here's a performance review that included IOPS:
http://www.pcper.com/article.php?aid=892&type=expert&pid=7
Everyone says these drives get 300-400IOPS peak. An Intel SSD will get you 8,000-12,000 easy, and the X25-E model will get you 15,000-20,000 easy. To compare:
http://www.legitreviews.com/article/1208/13/
That's the top two SSDs in the market, using Intel's controller and Sandforce's controller. For reads and a large request size the limitation is the SATA bus, you'll notice that each SSD maxes out the bus at 260MB/s. For small reads, it gets increasingly more ridiculous.
Four 600GB velociraptors in RAID0: $1120 and approximately 1200 IOPS. For 1.07IOPS/$.
One X25-M or Sandforce SSD in the 80-120GB range: $300 and approximately 8000 IOPS. For 26.67IOPS/$. IOPS actually grows as block size decreases, and both the X25-M and Sandforce SSDs see more than double the performance for 512B requests.
That's not the definition of a monopoly, or even what's wrong with being one.
There's nothing illegal with being a monopoly, but using your enormous market share to affect other markets, hurt potential competitors, etc, those things are illegal.
Health care is complex and there are dozens of other bills that make up the health care regulation we have now. Not only that, but legislators use ridiculous margins, double or triple spaced text and large fonts.
So not only is it shorter than you think it is, but it deals with issues more complex than you're willing to admit.
Shouldn't be 24/7. Modern S3 sleep is very efficient and works well with timers. Using Windows as an HTPC with sleep enabled will let the PC go to sleep, wake up to record, and then sleep again.
Did you see how it carved a logo into it that had a different appearance but looked flush?
That's it carving only a tiny, tiny bit in, probably in some crosshatch pattern to get the logo to stand out.
SharePoint 2010 will support Safari (Webkit) and Firefox (Gecko) browsers explicitly, and by extension work on derivatives using those engines.
Powershell support with proper verb-noun command structure and piping support?
I'm disappointed that I even have to add the last bit, but Powershell stuff from Microsoft differs greatly on supporting the implicit standards. There are some modules and snapins that are really good, there are some that are... not so much.