> The attacks crippled the economy, not the president.
The attacks were a blip on the economy. A giant tax refund and 2 wars put the nation into a massive deficit, and the global banking crisis devastated the economy.
Uh... If anything, Bush showed all the terrorists of the world that one successfully attack is sufficient to cripple the US economy and bleed us through involvement in several foreign wars. Those wars demonstrated that invading and occupying a couple of small middle-eastern nation was sufficient to over-extend and tax our huge military, while simultaneously draining our budget. They also sapped US will to get involved in other theaters.
"You go the war with the army you have, not the army you want." Anyone remember that? What about sending the reserves into battle? Multiple tours of duty with PTSD soldiers? Inability to provide proper veterans care? Lowered recruitment standards?
Devil's advocate: an individual sets a fire in a sub. A company designs a defective product that kills consumers. If it's company policy that causes the harm, the company is at fault, and the C_O is not held responsible.
Is that the way it should be?
Maybe. I think a bigger problem is tort reform. Punative damages were never designed to be a get-rich-quick scheme; they were a tool designed to punish companies that knowingly cause harm in such a way that they will be reluctant to do so in the first place. When a company can gain more from the harm then they will ever pay as punishment, there's no incentive to be honest.
Imagine if we punished bank robbers by fining him $100, and only punished robbers if they were successful in their crimes?
As the Baby Boomers slowly are forced to give up their passion / hobbies due to age, sickness, etc the rate of exit is significantly >>> the rate of entering.:-/ Liability (getting sued) and Risks (crashing) are seen as "not worth it" by the younger crowd. Like any community, you need enough "new blood" to sustain it and that isn't happening. Is that a bad thing? I don't know, but we can see trends and it looks like our world is changing. I guess that is the million dollar question: Is it changing for the better ?
I'm guessing you're in you're 30s.
I'm actually a member of the motorcycling community, and both my wife and myself have looked into the cost of obtaining pilot training and buying a share of an airplane. Risk and liability has very little to do with it. Major changes have been significantly increased costs, combined with lowering discressionary income, and reduced willingness to purchase on credit.
The motorcycling community is trending older; mostly mid 20s to late 40 year olds who have successful careers and disposable incomes. This is a group of people who have been responsible in their lives, and have enough money to pay the cost of entry. As a result, a lot of the industry growth has been at the high end. In the motorcycling community, top-of the line Japanese, German, and Italian imports are selling well. Mid-range is suffering somewhat. Low end has been trending towards more premium offerings.
10 years ago, the community was mostly early 20-somethings that would buy new bikes on fairly insane loans. That market is drying up; more and more folks are either buying used, paying cash, or leveraging their good credit for favorable rates.
That's a terrible comparison. Changing the oil according to the manufacturers recommended specifications *is* preventative care. Reactionary care would be ignoring the oil until the engine starts making clanking noises. At that point, you're performing a full rebuild, replacing all the components that were damaged by the oil system failure.
The preventative option costs $50 a few times a year. The reactionary option costs thousands of dollars.
Obama care isn't going to mandate that you go to the doctor every time you stub your toe.
The libertarian ideal assumes that the nautral state of business is competition, when in reality the natural state of business is collusion and consolidation. In a libertarian paradise, one of two things happens:
1. The major insurance companies collude, offering customers no choice in plans. All plans offered have loopholes where the company can easily dump the sick. Customers are given no choice, and insurance companies more or less write a death clause* into their policy,
2. The major insurance companies consolidate to the point where you only have one or two options, neither offering any real choice or competitive reason to chose one over the other. You accept whatever plan is offered.
In either case, start-ups are quickly squelched.
You more or less see this in the drug trade. In mexico, the drug market is more or less deregulated, since the government has no power to control the cartels. While the major cartels do squabble, they prefer not to compete against each other directly, as doing so tends to weaken both, allowing a 3rd cartel to grab for power. Regardless, upstart operations are quickly squashed.
You may argue that this situation is the result of government regulation. I'd agree, but point out that the only thing government regulation has done is artificially raised the value of the commodity. A commodity that is 'necessary' and sufficiently rare or expensive will tend towards the same result if left unregulated (see various oil and communication companies. See also diamonds, where the DeBeers conglomerate created the same artificial scarcity as seen in the drug trade.)
* Prior to the ACA, insurance companies did not have 'death panels' but they did have a 'death clause' in the form of a $3.5 million dollar lifetime cap on coverage. If you hit this cap, your 'pre-existing' condition would disqualify you from purchasing insurance from a competitive provider, and unless you were extremely rich, you clearly would not be able to insure yourself. At this point, you would be stabilized and sent home by the hospital as soon as your medical costs had left your family destitute.
As a side note, the lack of insurance has a tendency of making medical problems worse. Patients won't tend to pay out of pocket for preventative medicine, instead waiting until a medical issue requires emergency care. The ACA can certainly help correct this issue.
Apt platitude: An ounce of prevention is worth a pound of cure.
I can't speak to Doctors, but right now the education industry has pumped out way more nurses than we can employ. If the ACA forces hospitals to expand, the nursing jobs will fill quickly.
A courteous, polite response on Slashdot. Was not expecting that.:)
$800 is definitely doable. With components, there's often a sweat spot on the price/performance curve where you can build a powerful system without spending more than $1200 or so. A high-end gaming computer tends to be expensive. With that said, the main benefit of building a machine from components is that some of those components will be re-usable down the road.
Games typically don't benefit from horizontal scaling. Although many games have gone multi-threaded, there are only so many tasks you can hand off to additional cores.
Would have been nice if you'd put a TL;DR at the top that this is an apple propaganda piece.
The specs you listed above are for a gaming computer. Your Mac is a nice machine and it can certainly play some games, but it wouldn't be ideal for that purpose.
The first lesson I learned from the book 'High Performance MySQL' is that one should never use an ORM. Optimizing for ORM queries is virtually impossible.
I'm genuinely interested in hearing what the benefits of this are. It seems like mSATA drives are more or less on parity with this in terms of size and capacity, but have the benefit of increased longevity, reduced noise, and lower power consumption.
I honestly think spinning hard disks are going to go the way of CRTs within the next 5 to 10 years. And there's a high probability Segate will go with it.
You can MITM a SSL connection if you have access to a valid CA key. However, the attack would not be undetected; you need the sites private key in order to create a duplicate certificate. To create a duplicate certificate, you'd need the site's private key. And if you have that, you don't need a CA cert.
Someone who's paying attention could easily see that the MITM certificate doesn't match the original cert. For example, SSH doesn't use CA key signing. However, clients can still detect a MITM attack because the MITM public key does not match the cached key maintained by the client. (This presumes of course that you aren't performing a MITM attack using the compromised private key.)
I strongly disagree. I'd happily deploy configuration management tools or an inventory service in environments with 2 hosts. Configuration management isn't just automation; it's also build documentation and a handy gateway between your RCS and your systems.
Cloud computing is a strong abstraction layer between the physical machine and the logical machine. It's very similar in concept to memory virtualization - each process is given it's own address space, and really doesn't understand or care how that address space maps to physical memory. In a cloud computing environment, you request a new machine, and the cloud computing infrastructure automatically allocates a machine based on your requirements. The abstraction layer allows your physical hardware to be treated as a pool of resources, that can be expanded, repaired, or replaced without much concern about the impact to the logical machines it supports.
Cloud computing doesn't necessarily require virtualization either; physical computers can be provisioned using cloud infrastructure; https://wiki.openstack.org/wiki/Baremetal
If all you need is a place to dump your code, GIT is a perfectly functional GIT server. If you want full features, and damn the cost, you could consider GitHub enterprise.
I need to offer you credit; you are right. The issue isn't really PAE, it's how the kernel manages memory on 32 bit x86 architectures with more than 1GB of memory installed. PAE simply exacerbates the problem. Here's an explanation of the complaint:
On ia_32 systems, the kernel splits memory into 3 zones; DMA, NORMAL, and HIGHMEM.
ZONE_DMA is the first 16MB of memory, and is generally avoided unless needed (due to lack of available higher memory, or for DMA mappings.) The kernel tries to reserve this address range for devices that use DMA mapping.
ZONE_NORMAL is an address space that is directly accessible to the kernel, and extends from 16MB to 896MB. Kernel data structures are stored in this space, including the kernel page tables. Memory mappings start to consume a lot of memory in ZONE_NORMAL, and thus PAE on ia_32 with a lot of installed memory can cause out of memory issues, even when there is a lot of available physical memory. User data can be allocated into ZONE_NORMAL, but is preferred to be placed in ZONE_HIGHMEM to free ZONE_NORMAL for kernel data structures.
ZONE_HIGHMEM is memory above the 896MB barrier. This address range is not directly accessible to the kernel. In order for the kernel to access anything in this zone, a temporary map must be made into ZONE_NORMAL. These mappings consume pages of ZONE_NORMAL, and suffer a performance hit. User space processes can access these pages directly (handled by the virtual memory manager system, of course.)
Generally, memory will be allocated to ZONE_HIGHMEM, ZONE_NORMAL, or finally ZONE_DMA in that order of preference.
The x86_64 architecture eliminates the need ZONE_HIGHMEM. ZONE_NORMAL extends all the way from 16MB to the end of physical memory. This approach simplifies memory management, improves performance, and is generally more flexible.
You're correct that there was a major issue with my original post... My memory of the kernel architecture had garbled HIGHMEM with PAE, and I was thinking that PAE required mapping pages above 4GB into lower memory. This would of course cause a huge performance penalty for any process consuming memory above 4GB. I deserve downmods for the technical inaccuracy.
Yes, this is a bit of an oversight on my part. I really should have been discussing the way PAE is implemented on ia32 processors. I had a little bit of difficulty finding information about it online, I'll have to consult my architecture books at home, and will expand on the original post. Here's a bit of the info I could find about PAE weirdness on IA32.
PAE allows a processor to address up to 64GiB in theory but, in practice, processes in Linux still cannot access that much RAM as the virtual address space is still only 4GiB. This has led to some disappointment from users who have tried to malloc() all their RAM with one process.
Secondly, PAE does not allow the kernel itself to have this much RAM available. The struct page used to describe each page frame still requires 44 bytes and this uses kernel virtual address space in ZONE_NORMAL. That means that to describe 1GiB of memory, approximately 11MiB of kernel memory is required. Thus, with 16GiB, 176MiB of memory is consumed, putting significant pressure on ZONE_NORMAL. This does not sound too bad until other structures are taken into account which use ZONE_NORMAL. Even very small structures such as Page Table Entries (PTEs) require about 16MiB in the worst case. This makes 16GiB about the practical limit for available physical memory Linux on an x86. If more memory needs to be accessed, the advice given is simple and straightforward, buy a 64 bit machine.
Slashdot Mirror
> The attacks crippled the economy, not the president.
The attacks were a blip on the economy. A giant tax refund and 2 wars put the nation into a massive deficit, and the global banking crisis devastated the economy.
Did you sleep through 2008?
Uh... If anything, Bush showed all the terrorists of the world that one successfully attack is sufficient to cripple the US economy and bleed us through involvement in several foreign wars. Those wars demonstrated that invading and occupying a couple of small middle-eastern nation was sufficient to over-extend and tax our huge military, while simultaneously draining our budget. They also sapped US will to get involved in other theaters.
"You go the war with the army you have, not the army you want." Anyone remember that? What about sending the reserves into battle? Multiple tours of duty with PTSD soldiers? Inability to provide proper veterans care? Lowered recruitment standards?
Devil's advocate: an individual sets a fire in a sub. A company designs a defective product that kills consumers. If it's company policy that causes the harm, the company is at fault, and the C_O is not held responsible.
Is that the way it should be?
Maybe. I think a bigger problem is tort reform. Punative damages were never designed to be a get-rich-quick scheme; they were a tool designed to punish companies that knowingly cause harm in such a way that they will be reluctant to do so in the first place. When a company can gain more from the harm then they will ever pay as punishment, there's no incentive to be honest.
Imagine if we punished bank robbers by fining him $100, and only punished robbers if they were successful in their crimes?
I'm guessing you're in you're 30s.
I'm actually a member of the motorcycling community, and both my wife and myself have looked into the cost of obtaining pilot training and buying a share of an airplane. Risk and liability has very little to do with it. Major changes have been significantly increased costs, combined with lowering discressionary income, and reduced willingness to purchase on credit.
The motorcycling community is trending older; mostly mid 20s to late 40 year olds who have successful careers and disposable incomes. This is a group of people who have been responsible in their lives, and have enough money to pay the cost of entry. As a result, a lot of the industry growth has been at the high end. In the motorcycling community, top-of the line Japanese, German, and Italian imports are selling well. Mid-range is suffering somewhat. Low end has been trending towards more premium offerings.
10 years ago, the community was mostly early 20-somethings that would buy new bikes on fairly insane loans. That market is drying up; more and more folks are either buying used, paying cash, or leveraging their good credit for favorable rates.
The front page of Slashdot just doesn't have the value it used to have.
That's a terrible comparison. Changing the oil according to the manufacturers recommended specifications *is* preventative care. Reactionary care would be ignoring the oil until the engine starts making clanking noises. At that point, you're performing a full rebuild, replacing all the components that were damaged by the oil system failure.
The preventative option costs $50 a few times a year. The reactionary option costs thousands of dollars.
Obama care isn't going to mandate that you go to the doctor every time you stub your toe.
The libertarian ideal assumes that the nautral state of business is competition, when in reality the natural state of business is collusion and consolidation. In a libertarian paradise, one of two things happens:
1. The major insurance companies collude, offering customers no choice in plans. All plans offered have loopholes where the company can easily dump the sick. Customers are given no choice, and insurance companies more or less write a death clause* into their policy,
2. The major insurance companies consolidate to the point where you only have one or two options, neither offering any real choice or competitive reason to chose one over the other. You accept whatever plan is offered.
In either case, start-ups are quickly squelched.
You more or less see this in the drug trade. In mexico, the drug market is more or less deregulated, since the government has no power to control the cartels. While the major cartels do squabble, they prefer not to compete against each other directly, as doing so tends to weaken both, allowing a 3rd cartel to grab for power. Regardless, upstart operations are quickly squashed.
You may argue that this situation is the result of government regulation. I'd agree, but point out that the only thing government regulation has done is artificially raised the value of the commodity. A commodity that is 'necessary' and sufficiently rare or expensive will tend towards the same result if left unregulated (see various oil and communication companies. See also diamonds, where the DeBeers conglomerate created the same artificial scarcity as seen in the drug trade.)
* Prior to the ACA, insurance companies did not have 'death panels' but they did have a 'death clause' in the form of a $3.5 million dollar lifetime cap on coverage. If you hit this cap, your 'pre-existing' condition would disqualify you from purchasing insurance from a competitive provider, and unless you were extremely rich, you clearly would not be able to insure yourself. At this point, you would be stabilized and sent home by the hospital as soon as your medical costs had left your family destitute.
As a side note, the lack of insurance has a tendency of making medical problems worse. Patients won't tend to pay out of pocket for preventative medicine, instead waiting until a medical issue requires emergency care. The ACA can certainly help correct this issue.
Apt platitude: An ounce of prevention is worth a pound of cure.
I can't speak to Doctors, but right now the education industry has pumped out way more nurses than we can employ. If the ACA forces hospitals to expand, the nursing jobs will fill quickly.
This is true... in the sense that a hostage crisis requires a hostage taker, a hostage, and a police force.
A courteous, polite response on Slashdot. Was not expecting that. :)
$800 is definitely doable. With components, there's often a sweat spot on the price/performance curve where you can build a powerful system without spending more than $1200 or so. A high-end gaming computer tends to be expensive. With that said, the main benefit of building a machine from components is that some of those components will be re-usable down the road.
Games typically don't benefit from horizontal scaling. Although many games have gone multi-threaded, there are only so many tasks you can hand off to additional cores.
Would have been nice if you'd put a TL;DR at the top that this is an apple propaganda piece.
The specs you listed above are for a gaming computer. Your Mac is a nice machine and it can certainly play some games, but it wouldn't be ideal for that purpose.
Or did facebook pull a MySQL?
So, basically... MySQL pulled a facebook?
The first lesson I learned from the book 'High Performance MySQL' is that one should never use an ORM. Optimizing for ORM queries is virtually impossible.
http://stackoverflow.com/questions/7707976/php-and-mysql-high-traffic-solution
FWIW: I notice in a later post you mention PDOs... Which look like they won't impact optimization strategies.
I'm genuinely interested in hearing what the benefits of this are. It seems like mSATA drives are more or less on parity with this in terms of size and capacity, but have the benefit of increased longevity, reduced noise, and lower power consumption.
I honestly think spinning hard disks are going to go the way of CRTs within the next 5 to 10 years. And there's a high probability Segate will go with it.
You can MITM a SSL connection if you have access to a valid CA key. However, the attack would not be undetected; you need the sites private key in order to create a duplicate certificate. To create a duplicate certificate, you'd need the site's private key. And if you have that, you don't need a CA cert.
Someone who's paying attention could easily see that the MITM certificate doesn't match the original cert. For example, SSH doesn't use CA key signing. However, clients can still detect a MITM attack because the MITM public key does not match the cached key maintained by the client. (This presumes of course that you aren't performing a MITM attack using the compromised private key.)
I strongly disagree. I'd happily deploy configuration management tools or an inventory service in environments with 2 hosts. Configuration management isn't just automation; it's also build documentation and a handy gateway between your RCS and your systems.
There's always Ansible; the remote agent is a SSH server. Communication model is push only. Configuration files are YAML.
There are a dozen different configuration management tools on the market right now. There is almost certainly an option that fits your needs.
It doesn't really need 1.5 pages of description.
Cloud computing is a strong abstraction layer between the physical machine and the logical machine. It's very similar in concept to memory virtualization - each process is given it's own address space, and really doesn't understand or care how that address space maps to physical memory. In a cloud computing environment, you request a new machine, and the cloud computing infrastructure automatically allocates a machine based on your requirements. The abstraction layer allows your physical hardware to be treated as a pool of resources, that can be expanded, repaired, or replaced without much concern about the impact to the logical machines it supports.
Cloud computing doesn't necessarily require virtualization either; physical computers can be provisioned using cloud infrastructure; https://wiki.openstack.org/wiki/Baremetal
If all you need is a place to dump your code, GIT is a perfectly functional GIT server. If you want full features, and damn the cost, you could consider GitHub enterprise.
Yep, you're right. I corrected myself in another post.
I need to offer you credit; you are right. The issue isn't really PAE, it's how the kernel manages memory on 32 bit x86 architectures with more than 1GB of memory installed. PAE simply exacerbates the problem. Here's an explanation of the complaint:
On ia_32 systems, the kernel splits memory into 3 zones; DMA, NORMAL, and HIGHMEM.
ZONE_DMA is the first 16MB of memory, and is generally avoided unless needed (due to lack of available higher memory, or for DMA mappings.) The kernel tries to reserve this address range for devices that use DMA mapping.
ZONE_NORMAL is an address space that is directly accessible to the kernel, and extends from 16MB to 896MB. Kernel data structures are stored in this space, including the kernel page tables. Memory mappings start to consume a lot of memory in ZONE_NORMAL, and thus PAE on ia_32 with a lot of installed memory can cause out of memory issues, even when there is a lot of available physical memory. User data can be allocated into ZONE_NORMAL, but is preferred to be placed in ZONE_HIGHMEM to free ZONE_NORMAL for kernel data structures.
ZONE_HIGHMEM is memory above the 896MB barrier. This address range is not directly accessible to the kernel. In order for the kernel to access anything in this zone, a temporary map must be made into ZONE_NORMAL. These mappings consume pages of ZONE_NORMAL, and suffer a performance hit. User space processes can access these pages directly (handled by the virtual memory manager system, of course.)
Generally, memory will be allocated to ZONE_HIGHMEM, ZONE_NORMAL, or finally ZONE_DMA in that order of preference.
The x86_64 architecture eliminates the need ZONE_HIGHMEM. ZONE_NORMAL extends all the way from 16MB to the end of physical memory. This approach simplifies memory management, improves performance, and is generally more flexible.
You're correct that there was a major issue with my original post... My memory of the kernel architecture had garbled HIGHMEM with PAE, and I was thinking that PAE required mapping pages above 4GB into lower memory. This would of course cause a huge performance penalty for any process consuming memory above 4GB. I deserve downmods for the technical inaccuracy.
Here's a very brief summary of the problems with HIGHMEM:
http://linux-mm.org/HighMemory
Here's a bunch of links used to refresh my memory:
http://www.makelinux.net/ldd3/chp-15-sect-1
https://www.kernel.org/doc/gorman/html/understand/understand005.html
http://unix.stackexchange.com/questions/5143/zone-normal-and-its-association-with-kernel-user-pages
Yes, this is a bit of an oversight on my part. I really should have been discussing the way PAE is implemented on ia32 processors. I had a little bit of difficulty finding information about it online, I'll have to consult my architecture books at home, and will expand on the original post. Here's a bit of the info I could find about PAE weirdness on IA32.
https://www.kernel.org/doc/gorman/html/understand/understand005.html#sec: High Memory
The key quote: