That just means those who already have money will register any- and everything habitually, while amateurs get screwed over further for no reason other than corporations having easier access to their works.
Once something is published, it is no longer 'their' work. The only reason that people have any ability to control what happens to 'their' work once they make it public is because the public voluntarily decides to refrain from using the now public work.
If the work is unpublished, then it doesn't matter. No one has seen the work, it is as if it never existed. However, if a creation is abandoned, the amateur loses NOTHING if their creation is propagated.
If the amateur in your example were to withold the work and never publish it, then they need no protection for the work as it might as well never have existed. If the amateur publishes the work, and then witholds it from the public, it fails to serve its purpose as a copyrighted work. If the amateur publishes the work and wishes to market it, then it is in the artist's interest to maintain the registration.
The artist is really only a minor stakeholder in a work once it has been published. The 'owner' of the creation is in reality, the public, and their interests must be considered. Given that orphaned copyrights are one of the biggest threats to the longevity of a creation, requiring the people who wish to benefit from copyright perform minor custodial tasks is hardly an onerous proposition.
You make it sound like you have some chilly Bob Cratchit hunched over a desk with a quill pen and stacks of ledgers trying to work it out. These days it's all done with software on these nifty machines called "computers" - Your online shopping cart calculates and posts the tax to a General Ledger Account based on region, then you just remit that amount based on the GL, often automatically.
Glad everyone uses the 'software' and that their current 'software' already provides this currently non-existent feature.
I wonder how this wonderful system would work for my dad. He currently takes orders via web/email/phone, and negotiates a deposit to start work. About 1.5 years later, he finishes the carving, requests the remainder of the payment, then packages and ships the carving. (It takes a long time to do his carvings because there are multi-month treatment steps) If sold in person, sales tax is simple, it's the sales tax of where he lives since he is selling from his home. His 'software'? A literal accounts book. If you are only processing 20 orders per year, a full blown software suite is pretty overkill. (and you try to teach an 80 yr old former steelworker to use financial software)
It's an added expense, and it isn't necessary. Why should the resident of one state be burdoned with the regulatory cost of enforcing the laws of another state? Don't forget that an interstate tariff is Unconstitutional. The free flow of goods and services between states was a pretty important part of establishing the US.
The problem for the States is that some of them collect revenue from methods which are no longer appropriate in a modern era. Isn't that the point that we keep raising with regard to the music industry?
I've been doing a 2-drive ripping operation to backup all of my music CDs to FLAC. I toss in a few CDs every week or so, and I'm slowly working my way through the stack. (I'm rarely at this machine, so I usually only go through 6 discs in a sitting).
However, I noticed that one of my drives was taking so long, I was quite worried that I had purchased a faulty drive. Actually, the other drive was so much faster that I started to wonder if the FASTER drive was actually ripping all the music or just failing on track 2 and not reporting the error.
Turns out, that the FAST drive was one I had actually run a USB to IDE converter (inside the machine) because the motherboard only supported SATA. The slower drive was the 'new fancy' SATA drive.
This thread basically made my day in trying to figure out what the hell was wrong with my drives in that the jerryrigged USB conversion one was outperforming the newer drive.
You are such a fucking idiot. That would be both unethical and almost definitely illegal. Unbelievable that someone would think to post something like this.
If you like, I can post several 'contracts' I received from Chesapeake Energy for the leasing of my land for natural gas exploration. Every single 'copy' is slightly different in mundane, but legally interesting ways.
I wasn't even told that the contracts were different, until I pressed them to declare them identical to the contract I sent them. Then it came out that some definitions had changed, (how the pad site is defined), as well as a few other 'cleanup' changes. (This was an 80 page contract, so there were lots of areas for worry)
I only found out that there were changes by SCANNING the document, applying OCR, and then doing a differential comparison to flag 'questionable areas'. I then went back to the original physical copy to verify that indeed, the changes were there and weren't just the OCR bugging out.
I'll agree it is unethical (and if all it was, was cleanup, it's still bad practice), but as far as illegal is concerned, that all depends on how much money you feed your lawyer. I wasn't about to try and outlast an oil company's legal team.
(And of course, I didn't sign the contract, the way I figure is that the gas/oil is still there, so they will come back sooner or later. And I'll either get paid now, and stick it in a retirement account, or get paid later and just use it for my retirement or grandkid's education)
Well, your 'dsylexia' is causing my OCD to flare up something terrible! However, I did have to look at every single instance where you used the term, 'dsylexia', and I applaud your consistency.
(Well, of course I had to check to make sure that they were all spelled the same. I'm not kidding about the OCD. I don't even care about spelling or grammar in most circumstances, but I had to check)
I DON'T want my phone to bend. A rigid structure is very nice for a lot of reasons.
If you are reaching up to push a button on your phone, and it is held in a clamp (like a car-dock) You want it to be rigid so that it doesn't flex when you are pushing a button.
I currently use a case which has a silicone sleeve, and a rigid 'exoskeleton' design. The rigid exterior is very nice for distributing the force over a larger area, and the silicone acts as a great shock absorber. I'm certainly not going to stop using such a case because even a flexible phone would have sensitive parts, so I'm still going to want to protect it with a case and thus the flexibility is pointless.
It will be damned nice to have a flexible display and mount it on my car's windshield, but I don't really want that flexing. The advantage of this technology is that you aren't limited to planar surfaces for displays, not that you want your displays to flex.
First, that's not the same as 'works out of the box'. But let's assume for a moment that everything does work out of the box without any extra work on Dell's part.
Before a sane person would release a PC they would do the following: (This is all before the product even ships btw)
1. Evaluate that the SW and HW package they are shipping works at the basic level (drivers load, components work, etc) 2. Make sure that the SW/HW package can do what they have advertised it can do. You don't want to advertise USB 3.0 only to find out that your HW was actually only running at USB2.0. Even if it works, it has to work the way you say it's going to work. 3. Develop manuals and user side documentation for the system equivalent to that of the Windows version. 4. Develop manuals, training, and perform the training on your support staff. 5. Develop installation procedures for the new process to install and setup the system. Likely it is just an image that gets flashed, but you need to make sure that image is controlled, distributed, and won't conflict with your existing procedures. 6. Update your support software with the appropriate terms/codes/actions for tracking user problems. You probably don't want to register Linux users complaints as "Other" all the time. 7....
Some of that may not seem like much, but it all has to be done, and it is a non-zero cost. A zero-cost solution is just selling your current product. I can't imagine how you can believe that the cost to produce, sell, and support a variant(at best) of one of your current products is zero.
Imagine if you went to Toyota, and told them:
"I want you to start selling, along with your current lineup, a Camry that comes in a different color. However, I don't want you to spend any money to start doing this."
You don't really think it would be as simple as: Pick a paint color, buy it, and drop off a few gallons the assembly line and tell them to start using it?
IF you don't mind me asking, what size strip did you find to work best for you?
In my case, I'm using the drives as an OS/game file ONLY array. I wanted 120GB of storage, (60 is just slightly too small for modern games and an OS). I'm running 16GB of ram, so I completely removed the swap file. In theory, the writes on them should be pretty limited except for when I'm installing new programs, updating settings, and a few logs. I probably could get by with two 120gb drives in a RAID1 to maximize read performance and just not worry about writes. For large volume data, I have a simple RAID1 of spinning disks.
Monthly: OS/Game RAID0 is 100% copied to the 2TB RAID1 spinning drives Constant: Select folders on the RAID1 spinning drives are uploaded to Carbonite.
I figure that if the decidedly unreliable OS/Game driveset could fail, and all I would really lose is just the OS and installed games. All non-replaceable data is on the RAID1, and the real important stuff there is also uploaded on Carbonite. (I repeat this often on Slashdot because it's always good to hear someone tell me where I'm being an idiot and that I overlooked xyz).
So the striping size is something I've not really considered. Any suggestions? Or should I just stop bothering with the RAID0?
Firstly once you have entered a intersection legally it does not matter if the light goes red. Running a red light is entering the intersection on red not being in the intersection on red. Cross traffic is required to give you right of way to clear the intersection.
You may be correct. I'm wary to assume that this is the same for all jurisdictions, but let's assume that you are correct.
People don't know this. I sure as hell don't know the exact metrics by which a machine will trigger the camera, and I'm not wealthy enough to want to risk finding out. I'm sure most people are the same way.
Consider the behavior near speed cameras. People will be driving along at a safe speed. Perhaps even under the speed limit. But the instant someone glimpses that speed camera, brake lights turn on. It doesn't matter if they were doing 10 over, or 10 under the limit, the typical response to seeing any sort of automated ticketing device is to hit the brakes. The same thing has happened for years when drivers pass a hidden police car. Regardless of their current speed, the natural tendency is to respond to the threat as conditioned, and for good or ill, we have conditioned drivers to brake when they see a police car.
Living in Northern Virginia, I've received parking tickets from live human beings while I was literally walking to the multi-space meter from my car! It took 6 months before my court date, which took 4 hours, and even with my receipt from the multi-space meter, I was told that I probably just ran up to the meter when I saw the metermaid approaching. I guess you are supposed to drive on the sidewalk up to the meter and pay without leaving your vehicle before driving to your spot... Thankfully I noticed that the parking lot for the Arlington Court house was only 3 hour parking when I entered the building (notice that the court session lasted 4 hrs). The metermaids who finished court early had begun rounds in the court's parking lot.
So while I'd like to believe you that all jurisdictions are uniform and follow your reasonable standard. My experience with revenue generation through fines has been anything but reasonable.
I'm running two Vertex 3 60GB drives in possibly the worst configuration from a reliability perspective: RAID0
It's been about a year without an issue. I'm hoping that my old rule of thumb for solid state devices holds: If it doesn't break in 45 days, it should last for years.
I agree completely. However, we aren't trying to convince Linux users to switch to Windows. Right now, Windows has no learning curve from the windows user perspective. You can't really say one side has problems of a similar scale than the other when someone is already ON one side.
It doesn't really cost the Windows user anything to maintain the status quo and remain a Windows user, so the eventual payout of switching to Linux has to be great enough to offset that initial investment.
It's the exact same situation for almost any product that is better, but not ubiquitous. Consider geothermal heating for my home. That would be great to have, I'd love to install it, but is it worth a $30k investment right now?
And thus Linux. Great once you get invested, but a high cost in time now.
Oh, well it's cool you solved the problem. You probably should hurry over to Syria, tell them to just 'stop shooting each other'. I'm really surprised they didn't figure that out yet.
So the real problem is people approaching the intersection too quickly. Before cameras, they just went right through, causing right-angle collisions. Now they scared of the fine and breaking quickly, causing read-end collisions.
I'm not comfortable with having 1/10th of a second to decide if I need to decelerate my vehicle from 45MPH to zero or if the 0.25s it takes me to approach the intersection is too long for me to proceed through the arbitrary length of the intersection before the unknown duration yellow light changes to red and nails me with a $200-$400 ticket.
Now, my only options when I see a yellow light are: 1. Too close to stop safely: ACCELERATE to avoid taking too long 2. Unsure of yellow duration: STOP NOW ASAP don't want to risk going slightly past that white line.
Before I had the option: 1. Too close to stop safely: Decelerate and proceed cautiously. If it turns red, that's ok because I have enough room, and I'm taking my time to make sure no pedestrians are crossing against the light. I'll also be out of the intersection before opposing traffic starts so I'm not inconveniencing them.
2. Unsure of yellow duration: Stop the car, using care not to decelerate too quickly. I may stop just slightly beyond the white line, but I'm not in the plane of traffic, so no one is impeded. The car behind me could also decelerate safely.
If I made a mistake on 1 or 2 in the non-traffic camera situation, there is always the potential for a police officer to pull me over and let me know it was too far out of bounds. Strangely enough though, that has NEVER happened. Why, it's almost as if I'm a cautious driver, without a single citation for running a redlight or a speeding camera despite living in DC, yet the cameras have modified my behavior to be much less safe (for you), but much safer for my wallet.
2. No visible flashes to distract or blind drivers.
Those bug the hell out of me. Bright flashes on the opposite side of the highway as I'm driving. Great, now I've got after-images floating in my vision.
Oh yeah, while I was wondering what the hell that flash was, oh yeah that guy on the other side of the road was driving too fast, yeah I guess it looks like he is driving pretty fast... ^^^ The above thoughts contributed nothing to the safe operation of my vehicle.
I've got similar complaints about 'LED' style billboards that cycle images. Those bastards should be limited to one image per 24 hour period or banned outright. It's impossible to not at least glance away from the road when a giant 50' jumbotron switches images in your peripheral vision. It's like telling some to not read the next word: Soup.
What honest excuse do you have for running a red light? It isn't like you don't get plenty of warning that the thing is going to change.
Most infractions are not for the blatant 'solid red' light runners, but more for the people who simply made slight errors in judgement. Maybe they did try to 'beat the light', or maybe they just leisurely traveled through the intersection and took a bit longer than the yellow. The thing is, opposing traffic doesn't even have a green light yet, so the only real 'danger' these people pose is the danger that they may delay opposing traffic slightly and increase traffic. Not great, but certainly not T-bone style collision risks.
I'm a pokey driver, I've never received a speeding camera ticket or a redlight camera ticket (And hopefully I can keep it that way), but I HAVE encountered intersections where I've entered the intersection on a Green, watched it turn Yellow just as I enter, and turn Red before I clear the other side. And it isn't like I was doing 20 in a 50mph zone or entered before the intersection cleared. This is just me, driving carefully maybe 10mph below the limit, and having it go from green to red before I pass through. On some intersections, that would be a ticket, and that's appalling to me. Hell, they are forcing you to either break one law (speed) or another ('run' a redlight) Some of the longer intersections I've even proceeded through at the speed limit and still noticed that the light turned red.
So do I speed through, minimizing my time in the 'danger zone', and brake after, or do I brake too early, and unnecessarily disrupt the traffic flow and put others in danger?
These money making schemes really degrade the quality of life, and pervert the purpose of these laws. And it's all the more grating to me when a police officer can do the job better, and actually use some judgement in determining if someone is actually driving in a dangerous manner.
Traffic cameras are just school 'zero tolerance' polices put in place to line someone's pockets.
That's insurers' problem, and has no real effect on the state treasury. And having the cameras makes it easier to pin down blame and liability.
No, that's the problem of everyone who pays insurance premiums. And liability in a rear-end collision at an intersection is pretty easy to determine even without cameras.
Honestly we shouldn't ever use law enforcement as a revenue generation tool. It creates perverse incentives for the government.
If we could be trusted to develop fair and reasonable laws without corruption, then maybe, but just like well run Communisim, I think that's something that only exists in theory.
So what happens at intersections without red light cameras? Oh, the light turns red and two to three additional cars still finish their left turns on RED. Ideally, every intersection should be photo enforced.
So miniscule fraction of drivers performed what is really not that dangerous of a maneuver, more inconsiderate than dangerous, and you want to have red-light cameras at every intersection as ideal?
A single police cruiser, for 2 hours rotated around problem intersections could not only cite the drivers, but he could also cover the entire gamut of other traffic offenses which could occur, many of which are much more dangerous than simply doing a yellow-light car conga line. The best part is, after those two hours, the police officer could do all sorts of other police work. Heck, even during those two hours, the officer could respond to actual important calls.
Your entire response reeks of someone who either can't handle another person behaving slightly out of configuration, or the best satire/troll that has ever reeled me in.
T-bone crashes aren't the type of crashes prevented by red-light cameras to any significant degree.
A T-bone crash can only occur a few seconds into the light when the other lane of traffic has already begun to pass through the intersection. No driver WANTs to run a true red-light. Those times you see someone blow through a red-light that wasn't just someone squeaking through or missing a yellow? Those mid-red light runners completely missed that there was a redlight there at all! They didn't run the red-light because they wanted to, they ran the red-light because they weren't paying attention.
So what effect does a red-light camera have on people who aren't paying enough attention to see that there is a red-light there in the first place? Well, as we can see by these numbers, not much of an effect at all.
I'd be willing to be that there are fewer T-bone style crashes, because of an increased number of people stopped at the intersection, providing something else for the inattentive driver to see (or as the numbers suggest, rear-end)
I'm not even saying it's flawed. I've run into issues to be sure, but that's the nature of the beast.
I was just saying that "It's faster" isn't really so true as to be a selling point people should use to advocate using Linux. There are plenty of other points that are a lot better to use instead.
I like to tinker, and thus eventually break things. So for me, an OS that let's me get down into the nuts and bolts is great! For my parents? Not so much. For them I'm actually going for a just works approach. I'm hoping to get a VM running, and let them be hardware agnostic. Basically a slightly more formal version of a liveCD.
If someone criticizes Linux, don't take it as a personal attack. It's a necessary part of the improvement process. Even if a criticism is off base its still important to understand why someone had that perception. Maybe the guides work for experienced users but mislead neophytes? I've certainly made that mistake in the past.
The python thing was for a class, and they use a very fickle grader, so I was trying to use the exact setup they directed.
But yeah, normally I'd have just used the built in stuff. I'm glad I had to do it their way, to learn, and hell, I'm glad they listed a Linux install as an option in the first place. Otherwise I'd have just stuck with doing it on Windows to avoid complications.
The work spaces are a pleasant way to code over windows though.
Slashdot Mirror
That just means those who already have money will register any- and everything habitually, while amateurs get screwed over further for no reason other than corporations having easier access to their works.
Once something is published, it is no longer 'their' work. The only reason that people have any ability to control what happens to 'their' work once they make it public is because the public voluntarily decides to refrain from using the now public work.
If the work is unpublished, then it doesn't matter. No one has seen the work, it is as if it never existed. However, if a creation is abandoned, the amateur loses NOTHING if their creation is propagated.
If the amateur in your example were to withold the work and never publish it, then they need no protection for the work as it might as well never have existed. If the amateur publishes the work, and then witholds it from the public, it fails to serve its purpose as a copyrighted work. If the amateur publishes the work and wishes to market it, then it is in the artist's interest to maintain the registration.
The artist is really only a minor stakeholder in a work once it has been published. The 'owner' of the creation is in reality, the public, and their interests must be considered. Given that orphaned copyrights are one of the biggest threats to the longevity of a creation, requiring the people who wish to benefit from copyright perform minor custodial tasks is hardly an onerous proposition.
You make it sound like you have some chilly Bob Cratchit hunched over a desk with a quill pen and stacks of ledgers trying to work it out. These days it's all done with software on these nifty machines called "computers" - Your online shopping cart calculates and posts the tax to a General Ledger Account based on region, then you just remit that amount based on the GL, often automatically.
Glad everyone uses the 'software' and that their current 'software' already provides this currently non-existent feature.
I wonder how this wonderful system would work for my dad. He currently takes orders via web/email/phone, and negotiates a deposit to start work. About 1.5 years later, he finishes the carving, requests the remainder of the payment, then packages and ships the carving. (It takes a long time to do his carvings because there are multi-month treatment steps) If sold in person, sales tax is simple, it's the sales tax of where he lives since he is selling from his home. His 'software'? A literal accounts book. If you are only processing 20 orders per year, a full blown software suite is pretty overkill. (and you try to teach an 80 yr old former steelworker to use financial software)
It's an added expense, and it isn't necessary. Why should the resident of one state be burdoned with the regulatory cost of enforcing the laws of another state? Don't forget that an interstate tariff is Unconstitutional. The free flow of goods and services between states was a pretty important part of establishing the US.
The problem for the States is that some of them collect revenue from methods which are no longer appropriate in a modern era. Isn't that the point that we keep raising with regard to the music industry?
That means it is good advertising.
It certainly helped me:
I've been doing a 2-drive ripping operation to backup all of my music CDs to FLAC. I toss in a few CDs every week or so, and I'm slowly working my way through the stack. (I'm rarely at this machine, so I usually only go through 6 discs in a sitting).
However, I noticed that one of my drives was taking so long, I was quite worried that I had purchased a faulty drive. Actually, the other drive was so much faster that I started to wonder if the FASTER drive was actually ripping all the music or just failing on track 2 and not reporting the error.
Turns out, that the FAST drive was one I had actually run a USB to IDE converter (inside the machine) because the motherboard only supported SATA. The slower drive was the 'new fancy' SATA drive.
This thread basically made my day in trying to figure out what the hell was wrong with my drives in that the jerryrigged USB conversion one was outperforming the newer drive.
You are such a fucking idiot. That would be both unethical and almost definitely illegal.
Unbelievable that someone would think to post something like this.
If you like, I can post several 'contracts' I received from Chesapeake Energy for the leasing of my land for natural gas exploration. Every single 'copy' is slightly different in mundane, but legally interesting ways.
I wasn't even told that the contracts were different, until I pressed them to declare them identical to the contract I sent them. Then it came out that some definitions had changed, (how the pad site is defined), as well as a few other 'cleanup' changes. (This was an 80 page contract, so there were lots of areas for worry)
I only found out that there were changes by SCANNING the document, applying OCR, and then doing a differential comparison to flag 'questionable areas'. I then went back to the original physical copy to verify that indeed, the changes were there and weren't just the OCR bugging out.
I'll agree it is unethical (and if all it was, was cleanup, it's still bad practice), but as far as illegal is concerned, that all depends on how much money you feed your lawyer. I wasn't about to try and outlast an oil company's legal team.
(And of course, I didn't sign the contract, the way I figure is that the gas/oil is still there, so they will come back sooner or later. And I'll either get paid now, and stick it in a retirement account, or get paid later and just use it for my retirement or grandkid's education)
I am dsylexic and have met other dsylexics.
Well, your 'dsylexia' is causing my OCD to flare up something terrible! However, I did have to look at every single instance where you used the term, 'dsylexia', and I applaud your consistency.
(Well, of course I had to check to make sure that they were all spelled the same. I'm not kidding about the OCD. I don't even care about spelling or grammar in most circumstances, but I had to check)
When you think about it, giving someone the source code for syphilis is the cause of the problem.
I DON'T want my phone to bend. A rigid structure is very nice for a lot of reasons.
If you are reaching up to push a button on your phone, and it is held in a clamp (like a car-dock) You want it to be rigid so that it doesn't flex when you are pushing a button.
I currently use a case which has a silicone sleeve, and a rigid 'exoskeleton' design. The rigid exterior is very nice for distributing the force over a larger area, and the silicone acts as a great shock absorber. I'm certainly not going to stop using such a case because even a flexible phone would have sensitive parts, so I'm still going to want to protect it with a case and thus the flexibility is pointless.
It will be damned nice to have a flexible display and mount it on my car's windshield, but I don't really want that flexing. The advantage of this technology is that you aren't limited to planar surfaces for displays, not that you want your displays to flex.
Mutually assured destruction doesn't require 30 seconds... if you are on the moon. Think how long it took Apollo to get to the moon.
work pretty much out of the box
First, that's not the same as 'works out of the box'. But let's assume for a moment that everything does work out of the box without any extra work on Dell's part.
Before a sane person would release a PC they would do the following: (This is all before the product even ships btw)
1. Evaluate that the SW and HW package they are shipping works at the basic level (drivers load, components work, etc)
2. Make sure that the SW/HW package can do what they have advertised it can do. You don't want to advertise USB 3.0 only to find out that your HW was actually only running at USB2.0. Even if it works, it has to work the way you say it's going to work.
3. Develop manuals and user side documentation for the system equivalent to that of the Windows version.
4. Develop manuals, training, and perform the training on your support staff.
5. Develop installation procedures for the new process to install and setup the system. Likely it is just an image that gets flashed, but you need to make sure that image is controlled, distributed, and won't conflict with your existing procedures.
6. Update your support software with the appropriate terms/codes/actions for tracking user problems. You probably don't want to register Linux users complaints as "Other" all the time.
7....
Some of that may not seem like much, but it all has to be done, and it is a non-zero cost. A zero-cost solution is just selling your current product. I can't imagine how you can believe that the cost to produce, sell, and support a variant(at best) of one of your current products is zero.
Imagine if you went to Toyota, and told them:
"I want you to start selling, along with your current lineup, a Camry that comes in a different color. However, I don't want you to spend any money to start doing this."
You don't really think it would be as simple as: Pick a paint color, buy it, and drop off a few gallons the assembly line and tell them to start using it?
IF you don't mind me asking, what size strip did you find to work best for you?
In my case, I'm using the drives as an OS/game file ONLY array. I wanted 120GB of storage, (60 is just slightly too small for modern games and an OS). I'm running 16GB of ram, so I completely removed the swap file. In theory, the writes on them should be pretty limited except for when I'm installing new programs, updating settings, and a few logs. I probably could get by with two 120gb drives in a RAID1 to maximize read performance and just not worry about writes. For large volume data, I have a simple RAID1 of spinning disks.
Monthly: OS/Game RAID0 is 100% copied to the 2TB RAID1 spinning drives
Constant: Select folders on the RAID1 spinning drives are uploaded to Carbonite.
I figure that if the decidedly unreliable OS/Game driveset could fail, and all I would really lose is just the OS and installed games. All non-replaceable data is on the RAID1, and the real important stuff there is also uploaded on Carbonite. (I repeat this often on Slashdot because it's always good to hear someone tell me where I'm being an idiot and that I overlooked xyz).
So the striping size is something I've not really considered. Any suggestions? Or should I just stop bothering with the RAID0?
Firstly once you have entered a intersection legally it does not matter if the light goes red. Running a red light is entering the intersection on red not being in the intersection on red. Cross traffic is required to give you right of way to clear the intersection.
You may be correct. I'm wary to assume that this is the same for all jurisdictions, but let's assume that you are correct.
People don't know this. I sure as hell don't know the exact metrics by which a machine will trigger the camera, and I'm not wealthy enough to want to risk finding out. I'm sure most people are the same way.
Consider the behavior near speed cameras. People will be driving along at a safe speed. Perhaps even under the speed limit. But the instant someone glimpses that speed camera, brake lights turn on. It doesn't matter if they were doing 10 over, or 10 under the limit, the typical response to seeing any sort of automated ticketing device is to hit the brakes. The same thing has happened for years when drivers pass a hidden police car. Regardless of their current speed, the natural tendency is to respond to the threat as conditioned, and for good or ill, we have conditioned drivers to brake when they see a police car.
Living in Northern Virginia, I've received parking tickets from live human beings while I was literally walking to the multi-space meter from my car! It took 6 months before my court date, which took 4 hours, and even with my receipt from the multi-space meter, I was told that I probably just ran up to the meter when I saw the metermaid approaching. I guess you are supposed to drive on the sidewalk up to the meter and pay without leaving your vehicle before driving to your spot... Thankfully I noticed that the parking lot for the Arlington Court house was only 3 hour parking when I entered the building (notice that the court session lasted 4 hrs). The metermaids who finished court early had begun rounds in the court's parking lot.
So while I'd like to believe you that all jurisdictions are uniform and follow your reasonable standard. My experience with revenue generation through fines has been anything but reasonable.
I'm running two Vertex 3 60GB drives in possibly the worst configuration from a reliability perspective: RAID0
It's been about a year without an issue. I'm hoping that my old rule of thumb for solid state devices holds: If it doesn't break in 45 days, it should last for years.
I agree completely. However, we aren't trying to convince Linux users to switch to Windows. Right now, Windows has no learning curve from the windows user perspective. You can't really say one side has problems of a similar scale than the other when someone is already ON one side.
It doesn't really cost the Windows user anything to maintain the status quo and remain a Windows user, so the eventual payout of switching to Linux has to be great enough to offset that initial investment.
It's the exact same situation for almost any product that is better, but not ubiquitous. Consider geothermal heating for my home. That would be great to have, I'd love to install it, but is it worth a $30k investment right now?
And thus Linux. Great once you get invested, but a high cost in time now.
Oh, well it's cool you solved the problem. You probably should hurry over to Syria, tell them to just 'stop shooting each other'. I'm really surprised they didn't figure that out yet.
So the real problem is people approaching the intersection too quickly. Before cameras, they just went right through, causing right-angle collisions. Now they scared of the fine and breaking quickly, causing read-end collisions.
I'm not comfortable with having 1/10th of a second to decide if I need to decelerate my vehicle from 45MPH to zero or if the 0.25s it takes me to approach the intersection is too long for me to proceed through the arbitrary length of the intersection before the unknown duration yellow light changes to red and nails me with a $200-$400 ticket.
Now, my only options when I see a yellow light are:
1. Too close to stop safely: ACCELERATE to avoid taking too long
2. Unsure of yellow duration: STOP NOW ASAP don't want to risk going slightly past that white line.
Before I had the option:
1. Too close to stop safely: Decelerate and proceed cautiously. If it turns red, that's ok because I have enough room, and I'm taking my time to make sure no pedestrians are crossing against the light. I'll also be out of the intersection before opposing traffic starts so I'm not inconveniencing them.
2. Unsure of yellow duration: Stop the car, using care not to decelerate too quickly. I may stop just slightly beyond the white line, but I'm not in the plane of traffic, so no one is impeded. The car behind me could also decelerate safely.
If I made a mistake on 1 or 2 in the non-traffic camera situation, there is always the potential for a police officer to pull me over and let me know it was too far out of bounds. Strangely enough though, that has NEVER happened. Why, it's almost as if I'm a cautious driver, without a single citation for running a redlight or a speeding camera despite living in DC, yet the cameras have modified my behavior to be much less safe (for you), but much safer for my wallet.
2. No visible flashes to distract or blind drivers.
Those bug the hell out of me. Bright flashes on the opposite side of the highway as I'm driving. Great, now I've got after-images floating in my vision.
Oh yeah, while I was wondering what the hell that flash was, oh yeah that guy on the other side of the road was driving too fast, yeah I guess it looks like he is driving pretty fast...
^^^
The above thoughts contributed nothing to the safe operation of my vehicle.
I've got similar complaints about 'LED' style billboards that cycle images. Those bastards should be limited to one image per 24 hour period or banned outright. It's impossible to not at least glance away from the road when a giant 50' jumbotron switches images in your peripheral vision. It's like telling some to not read the next word: Soup.
What honest excuse do you have for running a red light? It isn't like you don't get plenty of warning that the thing is going to change.
Most infractions are not for the blatant 'solid red' light runners, but more for the people who simply made slight errors in judgement. Maybe they did try to 'beat the light', or maybe they just leisurely traveled through the intersection and took a bit longer than the yellow. The thing is, opposing traffic doesn't even have a green light yet, so the only real 'danger' these people pose is the danger that they may delay opposing traffic slightly and increase traffic. Not great, but certainly not T-bone style collision risks.
I'm a pokey driver, I've never received a speeding camera ticket or a redlight camera ticket (And hopefully I can keep it that way), but I HAVE encountered intersections where I've entered the intersection on a Green, watched it turn Yellow just as I enter, and turn Red before I clear the other side. And it isn't like I was doing 20 in a 50mph zone or entered before the intersection cleared. This is just me, driving carefully maybe 10mph below the limit, and having it go from green to red before I pass through. On some intersections, that would be a ticket, and that's appalling to me. Hell, they are forcing you to either break one law (speed) or another ('run' a redlight) Some of the longer intersections I've even proceeded through at the speed limit and still noticed that the light turned red.
So do I speed through, minimizing my time in the 'danger zone', and brake after, or do I brake too early, and unnecessarily disrupt the traffic flow and put others in danger?
These money making schemes really degrade the quality of life, and pervert the purpose of these laws. And it's all the more grating to me when a police officer can do the job better, and actually use some judgement in determining if someone is actually driving in a dangerous manner.
Traffic cameras are just school 'zero tolerance' polices put in place to line someone's pockets.
That's insurers' problem, and has no real effect on the state treasury. And having the cameras makes it easier to pin down blame and liability.
No, that's the problem of everyone who pays insurance premiums. And liability in a rear-end collision at an intersection is pretty easy to determine even without cameras.
Tell that to the guy behind me.
Sure, I'm not at fault, but I'm still delayed, my car is broken, I'm potentially injured, I hope he has insurance too.
Earn?
Honestly we shouldn't ever use law enforcement as a revenue generation tool. It creates perverse incentives for the government.
If we could be trusted to develop fair and reasonable laws without corruption, then maybe, but just like well run Communisim, I think that's something that only exists in theory.
So what happens at intersections without red light cameras? Oh, the light turns red and two to three additional cars still finish their left turns on RED. Ideally, every intersection should be photo enforced.
So miniscule fraction of drivers performed what is really not that dangerous of a maneuver, more inconsiderate than dangerous, and you want to have red-light cameras at every intersection as ideal?
A single police cruiser, for 2 hours rotated around problem intersections could not only cite the drivers, but he could also cover the entire gamut of other traffic offenses which could occur, many of which are much more dangerous than simply doing a yellow-light car conga line. The best part is, after those two hours, the police officer could do all sorts of other police work. Heck, even during those two hours, the officer could respond to actual important calls.
Your entire response reeks of someone who either can't handle another person behaving slightly out of configuration, or the best satire/troll that has ever reeled me in.
T-bone crashes aren't the type of crashes prevented by red-light cameras to any significant degree.
A T-bone crash can only occur a few seconds into the light when the other lane of traffic has already begun to pass through the intersection. No driver WANTs to run a true red-light. Those times you see someone blow through a red-light that wasn't just someone squeaking through or missing a yellow? Those mid-red light runners completely missed that there was a redlight there at all! They didn't run the red-light because they wanted to, they ran the red-light because they weren't paying attention.
So what effect does a red-light camera have on people who aren't paying enough attention to see that there is a red-light there in the first place? Well, as we can see by these numbers, not much of an effect at all.
I'd be willing to be that there are fewer T-bone style crashes, because of an increased number of people stopped at the intersection, providing something else for the inattentive driver to see (or as the numbers suggest, rear-end)
I'm not even saying it's flawed. I've run into issues to be sure, but that's the nature of the beast.
I was just saying that "It's faster" isn't really so true as to be a selling point people should use to advocate using Linux. There are plenty of other points that are a lot better to use instead.
I like to tinker, and thus eventually break things. So for me, an OS that let's me get down into the nuts and bolts is great! For my parents? Not so much. For them I'm actually going for a just works approach. I'm hoping to get a VM running, and let them be hardware agnostic. Basically a slightly more formal version of a liveCD.
If someone criticizes Linux, don't take it as a personal attack. It's a necessary part of the improvement process. Even if a criticism is off base its still important to understand why someone had that perception. Maybe the guides work for experienced users but mislead neophytes? I've certainly made that mistake in the past.
The python thing was for a class, and they use a very fickle grader, so I was trying to use the exact setup they directed.
But yeah, normally I'd have just used the built in stuff. I'm glad I had to do it their way, to learn, and hell, I'm glad they listed a Linux install as an option in the first place. Otherwise I'd have just stuck with doing it on Windows to avoid complications.
The work spaces are a pleasant way to code over windows though.