What I find funny in all of this is that Cable companies want to throw up even MORE channels. But every content provider more or less is trying to grab EVERY eyeball instead of grabbing a few eyeballs all of the time.
Let's think of it this way. How much does it honestly cost to run a Cable channel? Yes you have to produce content, but this is Science people. Ditch some glitz, and edit using a handicam and a Mac running Premier.
Now with a ultra-low budget, go find some free suppliers of content. One area the comes to mind immediately are PH.d candidates. Each and every one of them is begging to be published. Have them work with your production staff to work their thesis into a segment on the show. It won't be long until you are turning content away.
Worst case, you'll inspire a dozen or so sister stations that will specialize in a certain discipline.
Amoung my many aquaintances are a few historians. All of them snicker when I mention I've seen something on the History Channel. The problem with HC is that TV does not handle differing viewpoints all that well. In one case outlined to me by professional historians, they guy who got most of that airtime in one presentation is considered a crackpot in the field. But he photographed well.
Also look at their selection of subject matter. Their call letters might as well be WWII.
With cars the 1995 model was in showrooms starting September of 1994. If ford released it's new models in February of 2000, S&P would have their rating pegged at toilet paper.
Microsoft picked the model designation scheme for windows to match that of the Big 3 automakers. Of course, automakers put out a new version every year and are required to support each model for at least 10 years, including recall work and repairs.
Maybe someone should found "microdot", a propaganda and smearing forum for Microsoft partisans. In all fairness, the Linux folks should get a "linuxdot", and the folks who just want to fling mud head over to "bashdot."
In the meantime, posts bitching about everyone else's predjudices predjudice me (at least) to consider you either a)naive or b) deflecting attention from the real issue.
I for one work with both operating systems on a daily basis. Hell I have the 2 peacefully coexisting. Now I can tell you unequivocally that our Windows boxes are broken into, wormed, or die of spontaneous OS implosion (SOSI) an awful lot. Or Linux boxes suffer from about the same rate of SOSI. For every registry that croaks, we have an EXT2 partition meet it's maker. Both drop linked libraries, or lose programs to bit rot.
What distinguishes them is the susceptibility to intrusion or worms. Linux compared to windows is like fruitcake compared to potato salad. Fruitcake will go bad, eventually. Potato salad can't be trusted for more than a few hours outside, or a few days in the fridge.
I think that's pretty funny considering Longhorn is going to be embedding SQL as part of the file structure.
We have a pretty beefy database that is running our membership info. The vendor just told us that 512MB of memory is too little for SQL. We need 2GB to fit all of the tables in memory.
I don't know about you, but the index files on my NTFS partitions are pretty beefy...
You have obviously never rolled out a new version of Windows or Office. I've had all of those problems, AND MORE. And that's from the same vendor with the same supposed product.
I have set up Linux and Windows workstations in production environments. Hell, most of the people who use my Linux terminals are oblivious to what's running underneath, save that it is windows. Is it a drop in replacement for Windows: hell no. Can it work on a large scale: hell yes. Do you realize that certain design assumptions built into windows are utterly assine: only if you did it right.
Your first sign of trouble is a "week long rollout." For god sakes, It's taken our organization 3 years to migrate to 2000. And that's only 300 workstations. We are installing Linux on our end-of-life machines and setting it up in a few public labs for people to beat on. I find out what people break (or percieve as broken) before I reformat one machine.
And for the record, if you are migrating to Linux to save money you missed the point.
Except, do you really want the overhead of having to implement Ethernet and TCP/IP stacks on a device that is supposed to fit on the end of you keychain?
What is going to give out addresses? Do you honestly want to have to hand-configure each device's network settings?
Okay, name the last time a laid back people slaughtered a neighboring country, or leveraged a buyout of a competitor just to kill them. Laid back managers would be too damn lazy to ship work overseas.
Looking at things productivity wise, you can hire a lot more lazy people that stick around. And the produce about the same volume of work as a batch of 80 hour workweek trainees.
So what's taking it's place?
on
Is Bluetooth Dead?
·
· Score: 2, Insightful
So what competing technology is stepping in to take Bluetooth's place? It's low power, short range, and doesn't need a fancy access point.
Come on people, electricity took 50 years to become commonplace. This is technology, not pet rocks.
Linux is recognized as the leader of the project and nothing more. If you have ever looked in the source, it is littered with the names and email addresses of those who have contributed. There is even a CREDITS file in the root level of the source tree.
Everyone who writes code for the kernel does so to improve the kernel, not satisfy their ego. The ego seekers quickly get bored or disgusted and move on. Slashdot should have a similar system if you ask me.
If you do something, ANYTHING well enough someone will be more than happy to pay you to do it. Look at a typical street begger. He might collect a few quarters just sitting there. Now, put a musical instrument in his hands. Maybe a dollar bill or two.
I put this question to you: have you ever seen a musician who was any good on the street? I've seen a few. Very few, and mostly in Europe or high-traffic areas of New York. Instead of a cup, they had a music case open. Usually it's got quite a bit of currency at the bottom. People will stop what they are doing and applaud at the end of sets. They usually end up moving on to better things at coffee shops or Jazz clubs.
Folks, sit back, relax, and just do what you do for the joy of doing it.
Linus, you are my freaking hero.
Re:Lessig said it first-Metered packets.
on
Trusted Computing
·
· Score: 1
Sure you can COUNT packets. Now where are you going to STORE your counted packets? How do you handle the fact that a packet can be copied and sent along multiple routes at once? And how do you prevent someone from setting up a bogus service and simply writing invoices for packets? Or funneling packets through their system? Or designing their systems to maximize router hops?
What results is a regulatory nightmare. You see with water, natural gas, electricity, even phone calls there is a finite quantity to be tracked. You can't bill for more electrity than you have generated. At least not for long. Network packets are a complete figment of the imagination. They can be created or destroyed at will.
And don't think for a minute that industry can regulate itself. They will find, exploit, and enlarge any loophole in the rules to screw all parties involved. It's not evil, it's self interest.
Slashdot Mirror
I'm just worried about the Flat Earth Society staging a protest.
Let's think of it this way. How much does it honestly cost to run a Cable channel? Yes you have to produce content, but this is Science people. Ditch some glitz, and edit using a handicam and a Mac running Premier.
Now with a ultra-low budget, go find some free suppliers of content. One area the comes to mind immediately are PH.d candidates. Each and every one of them is begging to be published. Have them work with your production staff to work their thesis into a segment on the show. It won't be long until you are turning content away.
Worst case, you'll inspire a dozen or so sister stations that will specialize in a certain discipline.
The rub with common sense is that it's not all the common, and it involves gestaltic thinking rather than sensation.
Also look at their selection of subject matter. Their call letters might as well be WWII.
Microsoft picked the model designation scheme for windows to match that of the Big 3 automakers. Of course, automakers put out a new version every year and are required to support each model for at least 10 years, including recall work and repairs.
Oh well, that's what I keep the XP partition on my laptop for. Alas, Win4Lin only emulates 98/ME. Still works for Poser and Photoshop though.
Well, you could theoretically replace OpenSSH with a functional equivilent. (But it's so candylike...)
In the meantime, posts bitching about everyone else's predjudices predjudice me (at least) to consider you either a)naive or b) deflecting attention from the real issue.
I for one work with both operating systems on a daily basis. Hell I have the 2 peacefully coexisting. Now I can tell you unequivocally that our Windows boxes are broken into, wormed, or die of spontaneous OS implosion (SOSI) an awful lot. Or Linux boxes suffer from about the same rate of SOSI. For every registry that croaks, we have an EXT2 partition meet it's maker. Both drop linked libraries, or lose programs to bit rot.
What distinguishes them is the susceptibility to intrusion or worms. Linux compared to windows is like fruitcake compared to potato salad. Fruitcake will go bad, eventually. Potato salad can't be trusted for more than a few hours outside, or a few days in the fridge.
Ma, someone broke mu windows!
Then quit chuckin' rocks ya old fool!
Hmmm. The India-Linux connection explained.
We have a pretty beefy database that is running our membership info. The vendor just told us that 512MB of memory is too little for SQL. We need 2GB to fit all of the tables in memory.
I don't know about you, but the index files on my NTFS partitions are pretty beefy...
Sorry, you can't deliberately invoke Godwin's law. The thread still lives...
It's 24 hours in microsoft time.
I have set up Linux and Windows workstations in production environments. Hell, most of the people who use my Linux terminals are oblivious to what's running underneath, save that it is windows. Is it a drop in replacement for Windows: hell no. Can it work on a large scale: hell yes. Do you realize that certain design assumptions built into windows are utterly assine: only if you did it right.
Your first sign of trouble is a "week long rollout." For god sakes, It's taken our organization 3 years to migrate to 2000. And that's only 300 workstations. We are installing Linux on our end-of-life machines and setting it up in a few public labs for people to beat on. I find out what people break (or percieve as broken) before I reformat one machine.
And for the record, if you are migrating to Linux to save money you missed the point.
Thank you, I couldn't have said it better myself.
What is going to give out addresses? Do you honestly want to have to hand-configure each device's network settings?
In the meantime the Blue Chicken flies at Midnight.
Looking at things productivity wise, you can hire a lot more lazy people that stick around. And the produce about the same volume of work as a batch of 80 hour workweek trainees.
Come on people, electricity took 50 years to become commonplace. This is technology, not pet rocks.
Say, open-source CAD anyone?
Everyone who writes code for the kernel does so to improve the kernel, not satisfy their ego. The ego seekers quickly get bored or disgusted and move on. Slashdot should have a similar system if you ask me.
I put this question to you: have you ever seen a musician who was any good on the street? I've seen a few. Very few, and mostly in Europe or high-traffic areas of New York. Instead of a cup, they had a music case open. Usually it's got quite a bit of currency at the bottom. People will stop what they are doing and applaud at the end of sets. They usually end up moving on to better things at coffee shops or Jazz clubs.
Besides, who needs food when you have code...
Well for the record, I read this deep in the tree. ;)
Linus, you are my freaking hero.
What results is a regulatory nightmare. You see with water, natural gas, electricity, even phone calls there is a finite quantity to be tracked. You can't bill for more electrity than you have generated. At least not for long. Network packets are a complete figment of the imagination. They can be created or destroyed at will.
And don't think for a minute that industry can regulate itself. They will find, exploit, and enlarge any loophole in the rules to screw all parties involved. It's not evil, it's self interest.