It varies from state to state and city to city. Some have the very regulation you are talking about. I have never seen it enforced.
In your case if there was no indicator light. Then you could go for it when the traffic was going in the same direction as you or when clear from the other direction.
The general rule of thumb is from any corner you can cross. That does not mean you get to stop traffic to do so. Though it seems much more common now for people to just cross wherever they want in the area I live in. They seem surprised when I honk at them. It shakes them out of them looking down at their phone while randomly walking around. You may have 'right of way' but the driver does not always see you in time. Be safe.
I don't get this. You acknowledge that they have right of way. You have apparently had plenty of time to stop and have done so. Yet you insist on honking at them as if they did something wrong?
The law under the Uniform Vehicle Code, adopted by most states, is that there is a crosswalk (marked or unmarked) between any two sidewalks at a corner. Drivers have a legal responsibility to yield to pedestrians there. Drivers almost always flagrantly violate this law.
Maybe roll down your window and say something instead of blaring your horn at people who aren’t encased in a car. Although I am not sure why you think you have a right to teach strangers a lesson.
I have to say I am disgusted with HN. Horns aren’t meant for telling people they’re doing something you don’t like. They’re for preventing other cars from colliding with your car. Pedestrians pose no harm to your vehicle, so if you’re out there honking at pedestrians, you’re behaving in a shitty manner and making the road more adversarial for everyone.
Pedestrians absolutely pose potential harm to a car (though, of course, the car poses far more potential harm to the pedestrian), especially with all of the crumple zones and sensors. Even a relatively low speed collision of say, 25 mph, I'd be surprised if the car is getting away with less than $5k in repairs.
Jaywalking is dangerous, especially on busy streets. And I admit to my fair amount jaywalking when I worked in downtown Chicago.
The horn is primarily about expressing anger but about imminent danger. A pedestrian steps out, from limitted visibility between cars, into traffic they deserve to be honked at. Not because of anger, but because they are putting themselves and others at undue risk.
That said, I don't think Ive ever personally seen someone respond to a horn in a fashion to avoid an accident. Twice last year, I was involved in accidents caused by someone else changing into my lane. Both times I saw it coming, laid on the horn and braked, but they kept coming faster than I could stop.
One, I couldnt avoid at all. We were in a construction zone, and the car next to me just kept coming over. I saw it coming, but had no where to go. No shoulder, just a concrete K-rail with about 6 inches of wiggle room. Side swiped me at about 55 mph. Entire driver's side was fuckedd up. Couldnt even open my door. Also managed to fuck up some of the passenger side as I did everything I could to get out of the way. (little bit of fender damage, cut both tires and scraped up a wheel)
The second one was I was in a left turn lane and the dude tried to force is way in. I didnt even see his signal until it was too late. Again, laid on the horn and brake, still mamaged to put his rear door into my passenger side front quarter panel.
Had a third actual miss earlier this year. Was driving in the 2nd from left lane in a rain storm, doing around 80mph on the highway. Car in the left lane, without signaling, starts coming over. Again, slam on the brakes and the horn, asshole keeps coming. Went from 80 to 60 in about a second or so, nearly getting rearended in the process. My car also started going sideways. In a lesser car, I probably would have lost it, but mine is pretty stable. Soon as I let hard off the brake, it recovered easily.
Point is, everyone assumes if someone is honking they're road raging at you, and some surely use it that way, but it's primarily about signaling imminent danger, and you should really take note (and probably return to your lane until you can figure out what the danger is by checking your blind spots, etc).
When the dude is walking across a 3 way 45MPH in each direction street in a low light situation. Then 1 block away was a well lit cross walk. Yeah he gets the horn. Sorry if I did not make that clear. Did not think I had to... Oh that happened to me just last week. Although I am not sure why you think it is OK for that 1 dude to hold up about 40 other people.
That's not what horns are for. You seem to think it's a punitive device, and I certainly would interpret it similarly to you aiming the muzzle of a gun at my chest.
Granted, I'll agree that's a dumb situation to cross the street, but your actions make it even worse.
To be clear, I mean that if everyone did what you do, going around rationalizing how people "get the horn" when they upset you rather than when your car is in legitimate imminent danger of a collision, we're mainly accomplishing two things:
1. Making driving more aggressive as a whole, associating all these little driving interactions with BLARING CAR HORN SOUNDS
2. Cheapening the meaning of the car horn for when it actually matters
The horn isn't a tool for letting out your aggression. Try screaming obscenities loudly in your car or something else fun like that.
> Although I am not sure why you think it is OK for that 1 dude to hold up about 40 other people
This is a perfect illustration of the US's driving-first culture. Let's do some math here. 40 people / 1.7 people per car average [1] = ~23.529 or 24 cars (which may be the case if it's rush hour, but probably not if it's not). If this is a 3 way intersection, and each of the cars is evenly distributed between directions (which I realize is incorrect, of course), then there are ~7.843 or 8 cars per side. Assuming an (informally weighted) average car size of 174 in. per car [2], with 2 ft of distance between each car, then the block length is a minimum of 1406 ft. Given that the average person walks at 4.6 ft/s [3], this distance would take 5.09 min. to traverse, just to get to your well lit next block. The average US commute is 26.1 min [4], which means just getting to the next block to cross at the well lit intersection would be 1/5 of the average commute, let alone the time most people are willing to tolerate to go to the grocery or pharmacy.
Obviously there are a lot of assumptions in this calculation, but it really goes a long way to showing how little American car-first culture thinks of pedestrian infrastructure, attractiveness, and travel times. "Just" walking over to the next, well-lit block, immediately makes a pedestrian trip for chores non-viable for anyone that values their time. To me, there also seems an in-built disdain for the time and safety of the pedestrian, and those attitudes do nothing but make it more difficult for Americans to do anything without their cars.
Anyone who can say with certainty what the market is going to do is usually selling you something. Especially, when they trot out a magic number that predicts something. The division you are noticing has been there for a long time (100+ years).
Will there be a recession? Yeah. When, is the trick, it could be tomorrow or 10+ years from now. That recession will also be followed by a boom. Such is life. That we have not had one recently is a bit unusual but not unprecedented. You could even argue the the world is already in the 'coming' recession, minus the US.
I would posit people wanting a recession is just a form of jealously and resentment. Normal? Not in my experience. But then I may have just not noticed. I remember the gas lines of the 70s. No one really wants that just to feel smug, do they?
I am becoming more and more convinced that keeping my data and programs on other peoples computers is not a good idea. They can not seem to resist the idea of 'harvesting' information from me to 'monetize' me for a small monthly fee. The PC revolution is over. The smartphone killed it.
> I am becoming more and more convinced that keeping my data and programs on other peoples computers is not a good idea. They can not seem to resist the idea of 'harvesting' information from me to 'monetize' me for a small monthly fee.
This has more to do with “free” services than hosting your data elsewhere.
If that were the case paid services wouldn't be doing it too. The reason they do is that there is no large enough incentive/consequence to make a convincing argument to leave that revenue on the table. It is neither hosting it elsewhere nor the "free" services which tend to be the worst examples of it, but rather the lack of any financially valid reason not to.
My issues is it is that data 'elsewhere' bit that they want. Even when I pay they want to harvest my data. Most of the time it is to do the opposite of what the main article is talking about.
I am not on reddit. But I do read it a lot. I usually spend a couple of years before I make yet another account somewhere. Because most of the time other people have made my point and I do not have anything to add. At this point it has saved me many security breaches. As at some point the company almost always loses control of its password database for some reason.
Most of that effort to archive games is not IA. It is from 2 other groups who sometimes work with IA if they all are not fighting. Specifically one group is the one going through all of them and configuring them to work correctly in DOSBox. Another is just going through and just cataloging them. Getting the metadata on that stuff is kind of tough now. Like what was the exact date a game came out on? Does it have artwork still? Is there some odd protection scheme going on? Is there an IMG file for the disks? Or is it just some random pile of files? Can you get a copy from ebay? etc etc etc. IA typically notes who is doing the archive work. IA also respects takedown notices for these games. As many of them sort of came back from the dead and are sold again, or the company just does not want its IP on some random site. A good portion though no one really knows who owns them anymore. Some have clear lineage. Some have been sold over and over to random companies and depending on contracts no one knows.
That 'scene' is also full of drama and very insular. Donate to IA to help them build better infrastructure and better search. But donating because they host old abandoned DOS games I would not call a good reason, and misplaced. Because the people doing the majority of the work are doing it because they like it, not money. IA does have some work around that such as getting dosbox and mame running in a browser. Just be clear on what you are donating to.
It was annoying. The problem they had was the upper left already had a control there. The system menu. In some programs it is still 'there' but hidden. You can see it if you left click on the upper left corner. They could not get rid of it as some old win3x programs went trolling around in that menu and changed it.
Double-clicking the upper-left corner closed the window, a carryover from earlier versions. I think it still does this, to support programs that auto-click (such as quick and dirty corporate IT apps and such). They couldn't put a single-click control in the same spot.
Also, every app, whether it is hidden or not still responds to Alt+Space which does what the single-click used to do and bring up that old window controls menu, and it still drops down from that same Win 3.x corner. It's a fascinating commitment to a strange backwards compatibility.
(Up until Aero Snap in Vista and it's keyboard shortcuts of Win+Arrow Key I used to use Alt+Space,M a bunch because it was always the easiest way to move any window by keyboard in the event it got stuck somewhere out of mouse range or you just didn't feel like switching to mouse.)
It's also a handy way to get a window that got moved off screen easily, which can happen in setups with multiple monitors that get connected and disconnected.
Also, most applications will actually honor Ctrl+C/V as well as the Ctrl+Insert/Shift+Insert shortcuts, from the 1987 IBM CUA guidelines[0].
Remember one of the goals was 'just works' too. As they wanted to move people off win3x. The win3x apps had to work/look the same but pick up some of the nice styling from win9x. Some programs would also roll their own system menu and put it in that spot. That would cause a cover up of the close. For a run of the mill application it was just a style and they could have put it anywhere. For programs that controlled the whole window including the title bar area it was a tough choice. Even then it did not always come out looking right. The win95 style guide basically told everyone to knock it off and let windows control it.
Was it all a good choice? For some it was annoying. There was a shortcut that did the same thing. If you double clicked the upper left it would close the window too. Which is how they taught people to use win3x. Most certainly it was an interesting compromise to the constraints they had.
Copying the style was all on everyone else though. They wanted it to be familiar to windows users. All to 'gain market-share' I guess.
The problem with most economic models is they all work great. In the moment. Right up until it is 10 seconds later and something changed. Then they don't.
However, over time they have hidden variables that no one knows how to measure. Say to day you are in a bad mood. You go to a store pick up an item and go 'nah not going to buy that'. Then tomorrow you are in a good mood. You go to the same store and buy that item. Your neighbor does the same thing but does not buy it at all. Economics is very bad at figuring out what that even meant. But to know if handing people cash, or taxing more/less, or changing policies you kind of need to know what it did mean. Experimenting is a good idea which we have been doing for a long time. But the models still do not match.
The other issue is many of these things are huge systems (macro economics). You can change one little thing and it has an effect on 3 other things that you did not want. To use the classic micro economic model. The pizza joint. I raise my price because (MR=MC). I sell less pizzas but my profit is up. Profit does not come from nowhere. My customers paid more. So they can buy less of something else. I bought less items from my wholesalers so their profit is down. The gov gets more money because of taxes. One little change touched dozens of other stores/governments/people not even related to me. Getting that model right is tricky with thousands of hidden variables that more like functions.
The way I usually follow it is
1) Is this OK? For example It is only called once in the code in an error path?
2) Did I do something silly? For example, I left in some extra debug code.
3) is the code doing something silly? For example extra work, dragging in extra data that is not needed?
4) is the code written in a way that causes extra work, re-init on inner loop, loop hoisting, etc
5) Is there a better algorithm for this? Binary search vs linear?
6) is the code doing too many things at once. De-serialize it re-serialize it
7) Is there a better abstraction for this? Monolith code vs microservice?
8) Is there any compiler switches that are 'easy' wins? Packing, -O2, etc? Usually not.
9) What sort of memory arch does this machine have? It varies between machines even for the x86 world. For example if I rearrange my memory structures do I use less cache and emit less code. The cache line on this box is x bytes and on that box is y bytes. Some languages do not lend themselves well to this one due to the way their VM/ISA is written.
10) is there some asm that would help? usually not.
Usually 1-7 are all you need. If you get all the way to 10 you are in the deep end for most things.
Big O is good for many things. But in reality big O is O(N)+C where the C can get you. That is where the later steps help. But usually you can totally ignore it. Most of the big wins I get are just from flipping out a bad search for a O(log(n)) search, or removing 'extra' code.
Oh I agree. It is just that +C bit. What happens when your O(nLog(n)) basically just trashes the cache because of your data structures? Yet maybe something 'worse' would run better because of the way cache works? That +c bit can sometimes turn into its own big O. It is a nasty little gotcha when it does happen.
It is a good framework to get you in the ballpark of the correct thing. Even usually 99% of the time it is right. But sometimes the arch bites back due to your data.
$56k of earnings in exchange for freezing $70,000 of your income for 30 years? That seems insane if I'm honest.
If it were FU levels of money, or even 100%+ returns, I might think differently. But I can't imagine someone locking away $70k of their earnings for 30 years for only a 70% return.
Would probably depend on the drive. There were utils out there in DOS land that let you format higher than normal. Usually by playing with the sector/track sizes. But it depended on the drive to let you do it. The best I ever got was ~1.6 out of my drives/media.
The trick works by using the double sampling rate to inspect the normal data rate disk surface. When the disk surface already has a double data rate, the drive doesn't have a quadruple data rate mode to be able to read it.
In your case if there was no indicator light. Then you could go for it when the traffic was going in the same direction as you or when clear from the other direction.
The general rule of thumb is from any corner you can cross. That does not mean you get to stop traffic to do so. Though it seems much more common now for people to just cross wherever they want in the area I live in. They seem surprised when I honk at them. It shakes them out of them looking down at their phone while randomly walking around. You may have 'right of way' but the driver does not always see you in time. Be safe.