The cable companies own their own lines, but the DSL providers all lease lines from AT&T. The 4g wireless is newer, but the 3g providers are all 1-2 Mbps. DSL speeds are all over the map.
On the north side of Chicago (Lincoln park), you can choose between two cable, two 4g wireless, six 3g wireless, and about 10 xDSL providers.
Oh, and that laggy sattelite service too. All this choice in the most corrupt political climate in the country. Maybe Fairfax needs to hire Todd Stroger.
There may exist such applications, but I haven't seen them before, and I would think they have already been moved to SSD.. The average service time for an IOP with SATA is indeed longer, but most applications (even simple file servers) issue a queue of many requests, so aggregate throughput matters more. For writes, cache makes the difference unimportant. For databases, file servers, etc. throughput is king.
Obviously it wouldn't be cool if it was really slow, but isn't data redundancy the primary purpose?
Not really, performance has been the driver for the growth of companies like EMC. 99.999% availability is an absolute requirement as well. Say I have built a banking system. It absolutely, positively must be able to handle 30000 transactions per second, and those transactions require data from over 20 TB of account data. The only way to do that with magnetic disks us by lashing a fuck-ton of them together in parallel. Until very recently, only high-end arrays from EMC, hitachi, etc. could do this sort if thing.
We haven't purchased 15k disks for years. In most cases, it is actually cheaper to buy 3x or even 4x SATA spindles to get the same IOPS. Plus you get all that capacity for free, even when you factor in extra chassis and power costs. We use all that capacity for snapshots, extra safety copies, etc.
If your enterprise storage vendor is charging you the same price for a 1TB SATA spindle as a 300GB 15K spindle, you need to find a new vendor. Look at scale-out clustered solutions instead of the dinosaur "dual fiber controllers and a bunch of disk" offerings.
But all indications are that the effect is instead particularly an American one. So no, it isn't about "socialized education".
Try wearing Muslim headwear to a state-run school in France. Try having a swastika (or even an empty white circle on a red background) scribbled on a notebook in Germany. This general issue is not limited to the USA.
I never claimed, and I don't think anyone claimed, that all the design decisions in Vista were bad. No, the issue is that the Vista release, like most Microsoft products, was at best beta quality, more like alpha quality.
By the same criteria, most userland open-source software is released as alpha-quality. And a lot of kernel-space drivers. OpenOffice, GIMP, all media players, X.org, most wireless drivers... you name it, they all have major issues and shipped as "stable" in distros. Desktop Linux has been, on the whole, far buggier than Vista ever was.
Silverlight is an open specification that anyone can implement royalty-free. Moonlight already exists, to prove that point.
Conversely, HTML5 is not even close to official, and will likely not implementable in any standardized way (too big, with too many optional behaviors). Flash and Silverlight exist because the W3C sucks as a standards body. They should hand the keys over to the IETF or ISO.
As web developers, we NEVER should have coded to anything but the W3C standards.
Except the W3C standards have been addressing imaginary needs, filled with errors and omissions, way too late to matter. The reason Flash exists and is so entrenched is because of the W3C and many of the zealots who steer it.
There's a reason that the IETF's RFCs are followed more strictly than the W3C, and that is because the standards themselves are generally written by a group of no more than 3-4 people, with limited scope, and a clear goal. The W3C suffers from serious "design-by-committee" issues, and cannot seem to generate consensus (which is the whole purpose of a standards organization).
Per Slashdot tradition, I will pick on your analogy a bit, because I can't argue with most of the rest you wrote. We already already have the Apache for video... and it is: Apache. And IIS. And nginx, lighttpd, etc.
Move Networks and Microsoft have shown that the best way to do streaming in today's internet is via HTTP, while chunking the video into variable bit-rate segments. This allows easy caching of video fragments via CDNs or even Squid-style caching proxies at ISPs, universities, etc. Yes, you can do live streaming this way, and the Move Networks/Limelight Oprah event streamed to something like 1M viewers simultaneously.
Of course Move Networks has this patented this up the wazzu, and I imagine Microsoft has some of their implementation patented as well. But the actual chunking of video files is pretty obvious, and there's lots of prior art, so I imagine their specific patents can be avoided by an open standard.
So we don't really need an Apache for video, the distribution problem isn't hard, and we already have Apache.
What we need is the content generation toolchain, as you describe later. So we really need the Eclipse/gcc/Spring analogues for video. A free-and-open codec, file formats, and widely distributed players. As you state, the hardest of all these is the codec. I took a fair bit of maths and even some CG and DSP classes back in the day, and I can barely understand how MPEG-2 works, let alone something like H.264.
What about the Great Salt Lake? Or the Caspian Sea? (hint: one is salty, the other isn't). I live a few blocks from Lake Michigan, and just call it "the ocean" like my two-year-old.
Sidebar for covetous Southern Californians: no, you cannot have any of our trillions of cubic kilometers of cool delicious freshwater. You chose to move to a desert with 30 million other lemmings, and are suprised that water is a problem? Stop whining about water pipelines and move back to the snow you pansies.
Dude, virtual memory architectures of the Linux and Windows kernels (and almost all other modern operating systems) are essentailly the same. Everything runs on x86, and so everything utilizes the memory management features of x86 chips.
Or you can write perhaps five lines of VBA inside Excel and accomplish the same task with one tool. You could be shot for even enabling VBA of course, but whatver negative things you want to say about Excel, it does have lots of functionality.
You missed my point... end-user-oriented applications are not set up to use SELinux by default. And given the reduced functionality, they likely never will be.
An exploit in any executable you run on Linux, say Firefox, can do whatever the user acount under which Firefox is running can do. Same as Windows. This includes accessing or writing to various parts of the filesystem, creating outbound network connections, or, as is common in Windows, installing some form of rootkit using local priviliege escalation and persistent infection. Local privilege escalation is often not needed on Windows, since most non-corporate users run with local admin privileges, but that is about the only major difference.
A JPEG parsing bug in one of the libraries used by Gwenview would result in the attacker having the same privileges as the account from which you run Gwenview, and could do whatever it wanted to your home dir (steal cookies?), and read from most places on the system looking for sensitive information.
Yes, you can have certain programs that drop privileges on Linux. You can do that on Windows, too (IE8 does this by default on Vista-x64 and later). But most end-user programs do not do that, as it limits functionality.
Can you send me an example where Anthropomorphic Global Warming Theory accurately predicts known experimental results? Also, what experiments would you posit to prove or disprove Anthropomorphic Global Warming?
Tens of millions of stable Windows corporate systems in the real world prove you wrong. Hundreds of millions of OEM systems prove you wrong (they use Sysprep and cloning, too you know). My own compnay has been deploying servers and workstations from cloned images since the early days of Win2K - maybe 10K images since then. Never has an issue arisen that could be traced to the cloning. All "inexplicable" issues I'm aware of have usually been traced to bad hardware, corrupt filesystems, buggy drivers, the usual suspects. But never to the fact that a machine was cloned using Sysprep.
Lucene has a horrifying tendecy to corrupt it's indexes frequently. And it doesn't do what the OP wants in any case, as it doesn't understand file formats or respect native OS permissions. Even the Lucene- based Nutch is not a good fit.
All sharepoint content is accessible though WebDAV, which is how you "mount" a sharepoint document store to a client. We've used WebDAV as a Sharepoint integration mechanism for years. And there's always the possibility getting at the DB layer directly, which supports ANSI SQL better than any DB except Postgres. The schema is as sensible as you can reasonably expect from a system that allows users to define their own table structures.
"Lock-in" for Sharepoint data is very low on my list of concerns. Stability and DR for Sharepoint server farms on the other hand....
I don't know, I don't use WX at all, so I'm not dodging anything.
My point is that it is your fault that code made it into production. Everything has bugs, which is why you must test with realistic data sets, at all levels.
Clean up your own yard before knocking on your neighbor's door.
It also does infuriating bugs. Programs that work fine with small amounts of data explode when you get them into production. Doom!
And why, exactly, are your programs not exposed to realistic data sets until they are in production? I don't think you can blame wxWidgets for that massive failure.
Slashdot Mirror
The cable companies own their own lines, but the DSL providers all lease lines from AT&T. The 4g wireless is newer, but the 3g providers are all 1-2 Mbps. DSL speeds are all over the map.
On the north side of Chicago (Lincoln park), you can choose between two cable, two 4g wireless, six 3g wireless, and about 10 xDSL providers. Oh, and that laggy sattelite service too. All this choice in the most corrupt political climate in the country. Maybe Fairfax needs to hire Todd Stroger.
There may exist such applications, but I haven't seen them before, and I would think they have already been moved to SSD.. The average service time for an IOP with SATA is indeed longer, but most applications (even simple file servers) issue a queue of many requests, so aggregate throughput matters more. For writes, cache makes the difference unimportant. For databases, file servers, etc. throughput is king.
Obviously it wouldn't be cool if it was really slow, but isn't data redundancy the primary purpose?
Not really, performance has been the driver for the growth of companies like EMC. 99.999% availability is an absolute requirement as well. Say I have built a banking system. It absolutely, positively must be able to handle 30000 transactions per second, and those transactions require data from over 20 TB of account data. The only way to do that with magnetic disks us by lashing a fuck-ton of them together in parallel. Until very recently, only high-end arrays from EMC, hitachi, etc. could do this sort if thing.
We haven't purchased 15k disks for years. In most cases, it is actually cheaper to buy 3x or even 4x SATA spindles to get the same IOPS. Plus you get all that capacity for free, even when you factor in extra chassis and power costs. We use all that capacity for snapshots, extra safety copies, etc. If your enterprise storage vendor is charging you the same price for a 1TB SATA spindle as a 300GB 15K spindle, you need to find a new vendor. Look at scale-out clustered solutions instead of the dinosaur "dual fiber controllers and a bunch of disk" offerings.
But all indications are that the effect is instead particularly an American one. So no, it isn't about "socialized education".
Try wearing Muslim headwear to a state-run school in France. Try having a swastika (or even an empty white circle on a red background) scribbled on a notebook in Germany. This general issue is not limited to the USA.
I never claimed, and I don't think anyone claimed, that all the design decisions in Vista were bad. No, the issue is that the Vista release, like most Microsoft products, was at best beta quality, more like alpha quality.
By the same criteria, most userland open-source software is released as alpha-quality. And a lot of kernel-space drivers. OpenOffice, GIMP, all media players, X.org, most wireless drivers... you name it, they all have major issues and shipped as "stable" in distros. Desktop Linux has been, on the whole, far buggier than Vista ever was.
Silverlight is an open specification that anyone can implement royalty-free. Moonlight already exists, to prove that point. Conversely, HTML5 is not even close to official, and will likely not implementable in any standardized way (too big, with too many optional behaviors). Flash and Silverlight exist because the W3C sucks as a standards body. They should hand the keys over to the IETF or ISO.
Except the W3C standards have been addressing imaginary needs, filled with errors and omissions, way too late to matter. The reason Flash exists and is so entrenched is because of the W3C and many of the zealots who steer it.
There's a reason that the IETF's RFCs are followed more strictly than the W3C, and that is because the standards themselves are generally written by a group of no more than 3-4 people, with limited scope, and a clear goal. The W3C suffers from serious "design-by-committee" issues, and cannot seem to generate consensus (which is the whole purpose of a standards organization).
Per Slashdot tradition, I will pick on your analogy a bit, because I can't argue with most of the rest you wrote. We already already have the Apache for video... and it is: Apache. And IIS. And nginx, lighttpd, etc.
Move Networks and Microsoft have shown that the best way to do streaming in today's internet is via HTTP, while chunking the video into variable bit-rate segments. This allows easy caching of video fragments via CDNs or even Squid-style caching proxies at ISPs, universities, etc. Yes, you can do live streaming this way, and the Move Networks/Limelight Oprah event streamed to something like 1M viewers simultaneously.
Of course Move Networks has this patented this up the wazzu, and I imagine Microsoft has some of their implementation patented as well. But the actual chunking of video files is pretty obvious, and there's lots of prior art, so I imagine their specific patents can be avoided by an open standard.
So we don't really need an Apache for video, the distribution problem isn't hard, and we already have Apache.
What we need is the content generation toolchain, as you describe later. So we really need the Eclipse/gcc/Spring analogues for video. A free-and-open codec, file formats, and widely distributed players. As you state, the hardest of all these is the codec. I took a fair bit of maths and even some CG and DSP classes back in the day, and I can barely understand how MPEG-2 works, let alone something like H.264.
What about the Great Salt Lake? Or the Caspian Sea? (hint: one is salty, the other isn't). I live a few blocks from Lake Michigan, and just call it "the ocean" like my two-year-old.
Sidebar for covetous Southern Californians: no, you cannot have any of our trillions of cubic kilometers of cool delicious freshwater. You chose to move to a desert with 30 million other lemmings, and are suprised that water is a problem? Stop whining about water pipelines and move back to the snow you pansies.
These sure look like seas to me...
Dude, virtual memory architectures of the Linux and Windows kernels (and almost all other modern operating systems) are essentailly the same. Everything runs on x86, and so everything utilizes the memory management features of x86 chips.
Or you can write perhaps five lines of VBA inside Excel and accomplish the same task with one tool. You could be shot for even enabling VBA of course, but whatver negative things you want to say about Excel, it does have lots of functionality.
You missed my point... end-user-oriented applications are not set up to use SELinux by default. And given the reduced functionality, they likely never will be.
An exploit in any executable you run on Linux, say Firefox, can do whatever the user acount under which Firefox is running can do. Same as Windows. This includes accessing or writing to various parts of the filesystem, creating outbound network connections, or, as is common in Windows, installing some form of rootkit using local priviliege escalation and persistent infection. Local privilege escalation is often not needed on Windows, since most non-corporate users run with local admin privileges, but that is about the only major difference.
A JPEG parsing bug in one of the libraries used by Gwenview would result in the attacker having the same privileges as the account from which you run Gwenview, and could do whatever it wanted to your home dir (steal cookies?), and read from most places on the system looking for sensitive information.
Yes, you can have certain programs that drop privileges on Linux. You can do that on Windows, too (IE8 does this by default on Vista-x64 and later). But most end-user programs do not do that, as it limits functionality.
You're getting the Brits mixed in with the rest of Europe, and forgetting another Billion plus people.
Here is a better comparison.
1939M >> 591M, so stuff it you continental pansy.
Can you send me an example where Anthropomorphic Global Warming Theory accurately predicts known experimental results? Also, what experiments would you posit to prove or disprove Anthropomorphic Global Warming?
Tens of millions of stable Windows corporate systems in the real world prove you wrong. Hundreds of millions of OEM systems prove you wrong (they use Sysprep and cloning, too you know). My own compnay has been deploying servers and workstations from cloned images since the early days of Win2K - maybe 10K images since then. Never has an issue arisen that could be traced to the cloning. All "inexplicable" issues I'm aware of have usually been traced to bad hardware, corrupt filesystems, buggy drivers, the usual suspects. But never to the fact that a machine was cloned using Sysprep.
Windows is now supposedly > 50 Million lines of code. I imagine that it would take man-years to inspect every hit on the SID in the source code.
Lucene has a horrifying tendecy to corrupt it's indexes frequently. And it doesn't do what the OP wants in any case, as it doesn't understand file formats or respect native OS permissions. Even the Lucene- based Nutch is not a good fit.
All sharepoint content is accessible though WebDAV, which is how you "mount" a sharepoint document store to a client. We've used WebDAV as a Sharepoint integration mechanism for years. And there's always the possibility getting at the DB layer directly, which supports ANSI SQL better than any DB except Postgres. The schema is as sensible as you can reasonably expect from a system that allows users to define their own table structures.
"Lock-in" for Sharepoint data is very low on my list of concerns. Stability and DR for Sharepoint server farms on the other hand....
I don't know, I don't use WX at all, so I'm not dodging anything.
My point is that it is your fault that code made it into production. Everything has bugs, which is why you must test with realistic data sets, at all levels.
Clean up your own yard before knocking on your neighbor's door.
It also does infuriating bugs. Programs that work fine with small amounts of data explode when you get them into production. Doom!
And why, exactly, are your programs not exposed to realistic data sets until they are in production? I don't think you can blame wxWidgets for that massive failure.
Rackspace honors their SLAs. We've received two months credit for two outages of 1 hour in the last 3 years. that's over US$35K for my org.