Kind of like ants are an easy target for a human. The problem is that there are so many, and the way the law of the land works, they have to kill each one individually. (No RAID or newpapers.)
Sure they are going to try to make examples out of some folks, but they are just going to be playing whack-a-mole.
Now, do I personally like that people distribute copyrighted material on p2p networks? No. I think the practice is wrong. (Then again, so is xeroxing sheet music for the chuch choir.)
The Music industry is perfectly legally correct. The problem is the same as if I was legally correct in proceeding through a green light while a Mac truck was blowing the red in the other direction. I end up in traction regardless of how many tickets the truck got.
Seriously, both of you. I know, you're good nice understanding parents and all that, but how hard would you have smacked you kid if he was SCO right now?
At this point after a sufficiently tanned bottom, and being bannished to their room, (after removing all toys, game consoles, telephones, and internet), I'll put a Bjork CD on infinite look outside their room, and be casually slipping brochures for Military Academies under the door.
Hey, it's how I learned. Of course back in the 70's it was... no... must fight memories... "Your having my baby"... no, must not remember... "Skyrockets in flight"... AHHHHH
Sounds like they are pointing at the process as the problem
Today. Yesterday they said something else, and the day before was another thing. Whoever is running the PR department is missing a cardinal rule of Spin: it looses momentum after it changes direction.
Right now this case is sputtering like a gyroscope that's about to fall over.
while (horse->status == ALIVE) { smear_campaign(infidel+random()); piss_off(customers); }
/* REMOVED BECAUSE OF AMAZON PATENT
switch (sue(infidel)) { case WON: infidel=infidel->next; break; case LOST: smear_campaign(infidel); appeal(); cut_losses(); } */
sue(infidel); /* SECRET TO SUCCESS Transfer a random number of pennies to Evil Twin Skippy's account. Besides, by reversing the sign I make the legal fund grow! */ slush=money_in_bank * random() * 0.01; send_money(eviltwinskippy_slushfund,slush); & nbs p; money_in_bank+=slush;
/* Using BSA licensed algorithem */ infidel=infidel+random(); }
I've always wanted to finish my PsuedOS, its a phony operating system for simulated robots. The idea was to release the system wrapped with a virtual reality engine, and have folks develop robotic ships, tanks, and fighters to duke it out.
And when they got bored of fighting, use it to model space stations, automated traffic systems, and domestic droids. The idea would by to write the system as a pile of scripts running pseudocode. The trick would be to get everyone to write using the same language, that was really only useful for real-time processing.
My intent was also to develop "PPI" (Psuedo Programming Interfaces) that would act like device drivers, and translate a variable to, say, thrust on a rocket. Another PPI would translate position and orientation into an array. Still more would simulate the outputs from visual recoginitions systems, and so on.
If anyone has visited my website, they would see it presently exists as a paragraph or 2 of "coming soon speak." The project is probably waiting for me to be laid up after being struck by a bus or something.
Why go to the trouble of developing my own OS? Nothing really exists right now to comprehensively handle massive simulations. Yes you have protocols like HLA, but they are just message passing. Sure there is TCP/IP, but it's so neutral as to be of no help to someone starting out. I could develop a Java API, or a C++ library, but they are far too complex in some respects, and far too limited in others.
Frankly every operating system we have now assumes that you are structuring everything around files, documents, and static devices. At some point we have to do better.
There is a slight problem comparing this system to your average whitebox: It's got one of those infamous "All-in-one" motherboards. The graphics card "borrows" system ram. A system compile (RAM and I/O intensive) slows down KDE (Graphics and RAM intensive) because everyone is competing for the memory bus. Ordinarily fast operations like DMA also take a major hit.
In my application I don't give a flying foo. The system is going to live under a counter at a coffee shop as a simple firewall and terminal server.
But, having built many computers, I have noticed that most systems the use the main ram for video ram share this problem. PS: Low-end dell's fall under this category, at least the Optiplex 150. No experience with other vendors, feel free to share.
This case is sounding more and more like Novel V The Regents of the University of CA.
Indeed, how they are finding code that is similar between the linux kernels 2.2, 2.4, and 2.5 is a bit strange. They have re-plumbed most of the major operating elements to handle large memory sizes, you have the preemption patch, the low-latency scheduler, and a few tweaks that take the system our to 32 processors. Not to mention all of the day to day bugfixes.
SCO keeps changing their story. First Linux stole SMP from SCO, which never had SMP. Now Linux stole elements from System IV? Ahem, Novel sued BSD along those same lines and lost when it was revealed that much of System V was in fact lifted from BSD.
I have had the misfortune to have migrated Win2k and WinNT to Linux and Samba. The result is a system that is so reliable that people forget you are there. LOL.
I'm waiting for them to start sawing off the legs from chairs.
Re:Let 'em hire the young minds
on
Ageism in IT?
·
· Score: 3, Insightful
Case in point: I've had an absolutely brilliant guy volunteering at our museum for the last 3 years. He's 18 now, and has been doing a considerable amount of coding for our web-based projects.
His energy is commendable, and his ability to prettify websites is beyond my skills. However, when he isn't here I have to maintain the software. And man is it ugly. There are certain techniques one picks up over the years. Things like using a variable to "stand in" for a decision or condition that you plan on using throughout the code. Subroutines to handle repetitive code. General style issues that make the software maintainable.
For what it's worth, I'm happy to have him go out and forge new ground. Generally I have the software stable and maintainable by the time he comes around the next summer. But alas, he is moving on to college. Time to break in a new apprentice.
I'm getting out of both ends.
on
Ageism in IT?
·
· Score: 2, Interesting
When I was young they wouldn't take me seriously because I was inexperienced. Now that I have experience, I get rejection letters like "bringing someone on board as Senior as yourself would be a mistake at this point in the project."
They want 8 years of experience doing this, and certifications to do that, and for you to be 20 years old and willing to work for minimum wage. And they think they can get it because we are all out there and hungry.
I haven't heard that story. Buran certainly flew unfinished (her avionics and life support systems were unfinished), but AFAIK she was then completed at Baikonur.
That's a fact. Indeed, the craft managed to land in 30 mph winds, 6 feet from the center line on the runway. NASA won't even attempt a shuttle landing under those conditions.
Actually, NASA has funded multiple replacements for the shuttle. They just never seem to get anywhere with them because the insist on developing stuff a "project" at a time, instead of a "technology" at a time. Take the X-33. In one project they were simultaneously developing the Aerospike engines, composite fuel tanks, and a radical air frame.
All failed because unexpected delays, manufacturing problems, and cost overruns caused research to take a back seat to budgets. I'm reminded of the Navy not willing to spend the money to test more than 2 Mark torpedoes. Those torpedoes turned out to have several defects that seriously impacted the early phases of the war in the Pacific.
Slashdot Mirror
Surely you are missing the forrest for the trees. Now wait, that was Sonny...
Sure they are going to try to make examples out of some folks, but they are just going to be playing whack-a-mole.
Now, do I personally like that people distribute copyrighted material on p2p networks? No. I think the practice is wrong. (Then again, so is xeroxing sheet music for the chuch choir.)
The Music industry is perfectly legally correct. The problem is the same as if I was legally correct in proceeding through a green light while a Mac truck was blowing the red in the other direction. I end up in traction regardless of how many tickets the truck got.
Come to think of it, their stock symbol is SCOX.
At this point after a sufficiently tanned bottom, and being bannished to their room, (after removing all toys, game consoles, telephones, and internet), I'll put a Bjork CD on infinite look outside their room, and be casually slipping brochures for Military Academies under the door.
Hey, it's how I learned. Of course back in the 70's it was ... no ... must fight memories ... "Your having my baby" ... no, must not remember ... "Skyrockets in flight" ... AHHHHH
So THEY have the patent on the sharks with the laser beams on their heads!
Today. Yesterday they said something else, and the day before was another thing. Whoever is running the PR department is missing a cardinal rule of Spin: it looses momentum after it changes direction.
Right now this case is sputtering like a gyroscope that's about to fall over.
The statutes are for manufacturing and selling such a system. Technically code is not manufactured until it is compiled.
Linus is off scott free.
You see, they stop with just the first lawsuit. Your code should really read:
They are the castrated guys who used to guard the Vestile Vergins, right?
Do you know what Linux is?
That's the bit of cartilidge at the top of the throat where the sounds of speach are generated, right?
Do you know who SCO is?
Are they the folks who make mouthwash, right?
How high can you count in binary on 4 fingers?
15... DOH!
Move to dismiss your honor...
Surely the folks who rebadged Blackdown Java without attribution still regard open source positively...
(Gratuitous Gentoo High-5, followed by a 360 Waddle.)
And when they got bored of fighting, use it to model space stations, automated traffic systems, and domestic droids. The idea would by to write the system as a pile of scripts running pseudocode. The trick would be to get everyone to write using the same language, that was really only useful for real-time processing.
My intent was also to develop "PPI" (Psuedo Programming Interfaces) that would act like device drivers, and translate a variable to, say, thrust on a rocket. Another PPI would translate position and orientation into an array. Still more would simulate the outputs from visual recoginitions systems, and so on.
If anyone has visited my website, they would see it presently exists as a paragraph or 2 of "coming soon speak." The project is probably waiting for me to be laid up after being struck by a bus or something.
Why go to the trouble of developing my own OS? Nothing really exists right now to comprehensively handle massive simulations. Yes you have protocols like HLA, but they are just message passing. Sure there is TCP/IP, but it's so neutral as to be of no help to someone starting out. I could develop a Java API, or a C++ library, but they are far too complex in some respects, and far too limited in others.
Frankly every operating system we have now assumes that you are structuring everything around files, documents, and static devices. At some point we have to do better.
In my application I don't give a flying foo. The system is going to live under a counter at a coffee shop as a simple firewall and terminal server.
But, having built many computers, I have noticed that most systems the use the main ram for video ram share this problem. PS: Low-end dell's fall under this category, at least the Optiplex 150. No experience with other vendors, feel free to share.
The ROI on $200 is pretty easy to swallow, and frankly I've run these applications on a 486.
Granted, I did napalm the Lindows off the drive and reinstalled a more customizable distro, but at least I knew all the parts have Linux drivers.
This case is sounding more and more like Novel V The Regents of the University of CA.
Indeed, how they are finding code that is similar between the linux kernels 2.2, 2.4, and 2.5 is a bit strange. They have re-plumbed most of the major operating elements to handle large memory sizes, you have the preemption patch, the low-latency scheduler, and a few tweaks that take the system our to 32 processors. Not to mention all of the day to day bugfixes.
SCO keeps changing their story. First Linux stole SMP from SCO, which never had SMP. Now Linux stole elements from System IV? Ahem, Novel sued BSD along those same lines and lost when it was revealed that much of System V was in fact lifted from BSD.
It isn't already on Bit-Torrent?
Anyone have some GPS coordinates for that? No reason, really.
I have had the misfortune to have migrated Win2k and WinNT to Linux and Samba. The result is a system that is so reliable that people forget you are there. LOL.
His energy is commendable, and his ability to prettify websites is beyond my skills. However, when he isn't here I have to maintain the software. And man is it ugly. There are certain techniques one picks up over the years. Things like using a variable to "stand in" for a decision or condition that you plan on using throughout the code. Subroutines to handle repetitive code. General style issues that make the software maintainable.
For what it's worth, I'm happy to have him go out and forge new ground. Generally I have the software stable and maintainable by the time he comes around the next summer. But alas, he is moving on to college. Time to break in a new apprentice.
They want 8 years of experience doing this, and certifications to do that, and for you to be 20 years old and willing to work for minimum wage. And they think they can get it because we are all out there and hungry.
Have fun with it.
That's a fact. Indeed, the craft managed to land in 30 mph winds, 6 feet from the center line on the runway. NASA won't even attempt a shuttle landing under those conditions.
A more detailed account here
Suffice to say, had the will been there, they could have flown the Buran again.
All failed because unexpected delays, manufacturing problems, and cost overruns caused research to take a back seat to budgets. I'm reminded of the Navy not willing to spend the money to test more than 2 Mark torpedoes. Those torpedoes turned out to have several defects that seriously impacted the early phases of the war in the Pacific.
Besides, if you wanted to start from scratch, I know buy some surplus Soviet prototypes.
Not that I watch TV at all.