Do you believe they should be law?  

189 members have voted

  1. 1. Do you believe they should be law?

    • Yes
      93
    • No
      96


Recommended Posts

i dont think anyone here has said that having DRLS is less safe then not having them. The argument is there are times when you need to have no lights at all.

No, there are no times at all, actually. Being on the road is not about sneaking your GF home after curfew or stuff like that.

No, there are no times at all, actually. Being on the road is not about sneaking your GF home after curfew or stuff like that.

perhaps you misunderstood me. i was not asking your opinion, i was stating fact. there are times when i dont want my lights on. maybe you have not been in a situation when you dont want yours on, and thats fine. cars are not always on the road, though. a driveway is not a public road. if im parked and want to keep the car running, im not driving, i dont want my lights on.

perhaps you misunderstood me. i was not asking your opinion, i was stating fact. there are times when i dont want my lights on. maybe you have not been in a situation when you dont want yours on, and thats fine. cars are not always on the road, though. a driveway is not a public road. if im parked and want to keep the car running, im not driving, i dont want my lights on.

So pull up your emergency brake (it should be up anyway if parked). The lights go out. Problem solved.

Of course, you shouldn't leave your car running for no reason when not moving, but that's another thread.

I've been pondering this for a while, since I first saw the thread come up a while back. I've dodged it a bit and made my little funny comment and have now decided to offer my conjecture.

If, according to research done around the world, that DRL's reduce accident rates somewhere between one to ten percent....

How many accidents occur around the world and what would one to ten percent of that number be?

Let's assume every country has 20,000 accidents per year (I know, not accurate but bear with me)...

How many countries are there?

Let's assume there are 120 countries with cars and roads (I think there are more, but I'm being cautious)...

That means there are (at least) 2,400,000 accidents per year around the world.

Let's humor the anti-DRL crowd and say that ONLY 1% of those accidents would have been prevented by DRL's....

That means that 24,000 people (and up to 240,000 people) could have had their accident avoided or maybe even life saved by DRLs...

That is, if you didn't whine and b!tch about them.

You want your social equality and government hand-outs and tax the rich and I could go on... but...

Are you that selfish that you want 24,000 people dead just because you don't want your headlights on during the day...

... or because you want to sneak into your girl/boyfriends neighborhood?

Best post in teh thread. If a vehicle is moving it needs to be seen. Period.

Hell no, DRL's are just too metro to gain popularity here.

-DRL's were created to deal with lighting deficiencies that we don't have in the US

-Higher natural light requires brighter DRL's = more glare

-They are annoying to other drivers

-No positive effect on bright, sunny days

-Dubiously addresses only one or two types of crashes

-Inefficient

-Detracts from motorcycle use that is proven to be effective

Installing sensors that react to ambient light is a much more elegant solution that this feel good baldurdash but neither should be regulated. GM's latest study only shows that 423 people were 'saved' by them in the last ten years. (Thats about oh, 0.1% and not statistically significant)

Your 'even if it saves just one person!' type arguments scare the hell outta me.

Edited by Dashel
Hell no, DRL's are just too metro to gain popularity here.

-DRL's were created to deal with lighting deficiencies that we don't have in the US

What the hell does that mean?

-Higher natural light requires brighter DRL's = more glare

-They are annoying to other drivers

-No positive effect on bright, sunny days

-Dubiously addresses only one or two types of crashes

I don't believe that any of those are true. For one, they are useful even on bright, sunny days - they make it easier to tell whether a car is running or parked (less likely to be surprised by a car your eyes or peripheral vision thought was parked).

-Inefficient

Then why have car manufacturers like Saab, when asked, insisted that the effect on gas mileage is indiscernable?

-Detracts from motorcycle use that is proven to be effective

Huh?

Installing sensors that react to ambient light is a much more elegant solution that this feel good baldurdash but neither should be regulated. GM's latest study only shows that 423 people were 'saved' by them in the last ten years. (Thats about oh, 0.1% and not statistically significant)

I bet those 423 people would disagree...

My car has both light sensors (which are optional, they're only used if you have the lights set to "auto"), and DRLs which have an on/off switch. Though on my car the DRLs appear to be the high-beams, which I haven't yet read about (likely has something to do with the bi-xenon setup), and so far I've left them disabled.

I'm not saying they should be regulated, just that your arguments against them seem shallow and illogical.

DRL (and the majority of 'positive studies') originated in northern countries with lower levels of outdoor ambient light than we experience in the US. If we can't see another car on a bright, sunny day I think there are more pressing issues at stake. I really don't see how your example is of that much importance. If the car is behind me what do I care for if he is parked or not? That it would enable you to see if a car in front of you was going to pull out just doesn't hold weight.

They were created to assist with head-on and front-corner collisions only (i.e. taking a curve or passing and not 'clipping' each other due to misleading light).

Having something run all the time will consume unnecessary engergy. What you are really asking is that if a 'nominal' fee is worth it for the percieved safety. I don't think 1.2B of mandated technology is the answer.

I could see the state of Alaska reasonable push for this during certain seasons, but even there 24/7 lights aren't the answer. Really though, its simply a matter of taking power away from the driver, which is where it belongs. Proponents want to install something you can't turn off. Do you really need anymore reason than that?

-DRL's were created to deal with lighting deficiencies that we don't have in the US
Nope, for better visibility in ALL conditions.
-Higher natural light requires brighter DRL's = more glare
Nope, the candela level is regulated.
-They are annoying to other drivers
Nope, I can't imagine anyone saying, "damn you, your DRL made me notice you more on the road. How dare you?"
-No positive effect on bright, sunny days
Let's say you're correct; what's the negative effect? BTW, you're actually not correct. Bright days don't suddenly render DRLs useless.
-Dubiously addresses only one or two types of crashes
What's your point? Better yet, which studies are you referring to? Nothing posted was so limited, except for the single study done in the US
-Inefficient
Compared to what?
-Detracts from motorcycle use that is proven to be effective
So DRLs are useless but they also make motorcycles more visible? :blink: Which one is it?
Really though, its simply a matter of taking power away from the driver, which is where it belongs. Proponents want to install something you can't turn off. Do you really need anymore reason than that?
So your whole point is that there's something out of your control? Seatbelts are mandated; do you NOT wear them just to be contrary?
Cars are more visible. You don't notice it probably because you don't see it much. It's just one of those things that you get used to.

Indeed AND there are plenty of cars down here which don't turn on any lights when it rains so we see them really late. Therefore such law would be handy there you always have to turn on your lights.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Hello, Installed here without issue. Regards, Aryeh Goretsky
    • Microsoft updates Visual Studio Code with easier language model discovery and in-app search by Paul Hill Microsoft has released Visual Studio Code 1.125, its latest weekly release. This week, the company has focused on discovering and installing extra language models via the Marketplace; searching the web and securely browsing over remote connections without leaving VS Code; choosing how long VS Code waits before installing extension updates; and delivering managed Copilot settings through existing device management tooling. In older versions of VS Code, extensions could contribute their own model providers, but to find these extensions, you needed the right tags to search for in the Extension view. Now, the Language Models editor gives you an Install Model Providers button that opens the Extensions view, which is filtered to extensions that contribute model providers, making it easier to find and install them. Once you install a provider, its model will appear in the model picker. If you use the integrated browser much, you can now look up information without leaving VS Code by typing a query into the integrated browser’s address bar. It will use your configured search engine, the same way a standalone browser does. You can use workbench.browser.searchEngine to pick a search engine. When the browser is opened in a remote workspace, it's now possible to proxy HTTP(S) traffic via the remote connection. This allows you to connect to any ports or services that can only be accessed from the remote machine. If you read our coverage from two weeks ago about VS Code 1.123, you might have seen that extension updates have a two-hour delay as a safety measure. In this update, Microsoft is giving you the ability to configure the time of the delay. You can find it under extensions.autoUpdateDelay. Finally, with this update, admins can deliver managed GitHub Copilot settings through native device management (MDM) channels on Windows and macOS, in addition to account-based enterprise settings files. Settings delivered via MDM appear as policy-enforced in VS Code and can’t be overridden locally. Future updates will extend the supported policy keys across Copilot surfaces. You can download the update from the Visual Studio Code website now.
    • "it opens up new doors for people who prefer using Edge, but cannot be bothered to configure a Microsoft account" You already have a Microsoft account if you are using Windows 11, because you can't set it up without one.
    • This is how much iPhone 18 Pro could cost after Apple's price hike confirmed by Hamid Ganji Image via Apple Apple CEO Tim Cook confirmed in a recent interview that the company may have to raise prices on some of its products due to the ongoing memory shortage. While he did not elaborate on the scale of the price hikes, new estimates suggest that Pro iPhone models could become significantly more expensive this fall. The Wall Street Journal and research firm TechInsights have come up with an educated estimate of how much the upcoming iPhone 18 Pro could cost after its launch in September. The estimate is based on current increases in memory and storage chip prices. For starters, the iPhone 18 Pro base model is expected to feature 12GB of RAM and 256GB of internal storage. According to TechInsights estimates, 12GB of DRAM for the iPhone 17 Pro cost Apple $39 last year. However, for the iPhone 18 Pro, the cost of the same amount of DRAM could soar to $145. Likewise, 256GB of flash storage that previously cost $13 could now cost around $51. Producing a base iPhone 17 Pro reportedly cost Apple around $582, but TechInsights estimates that the production cost of the iPhone 18 Pro could rise to $726. If Apple wants to maintain the roughly 47% profit margin it enjoys on the iPhone 17 Pro, the base price of the iPhone 18 Pro would need to reach $1,371. After standard pricing adjustments, customers could end up paying around $1,299 for the base model. However, that may not be the end of the story. As we previously reported, the iPhone 18 Pro is said to feature a variable-aperture lens, which could cost Apple at least 50% more than the current camera system. The estimated $1,299 price tag does not include the additional cost of this upgraded camera hardware. Once that expense is factored in, the base model could cost at least $1,399. A $1,399 price tag for the base iPhone 18 Pro would represent a significant increase over the current $1,099 starting price of the iPhone 17 Pro. If Apple wants to keep its upcoming iPhones competitive, it may need to accept lower profit margins.
    • Oh man, but what if I have the PS3 version?
  • Recent Achievements

    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
    • One Month Later
      Vincian earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      543
    2. 2
      +Edouard
      171
    3. 3
      PsYcHoKiLLa
      84
    4. 4
      ATLien_0
      64
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!