No, it's how you get mens rea for the felony murder rule. You didn't carry the gun with the intent to kill, only to intimidate, but you still had a guilty mind, and if you then used the gun to kill someone in the heat of the moment, there's your mens rea.

And remember that actual cause does not mean literally pulling the trigger. At least in the U.S., the courts apply a "but for" test. If the event would not have happened without the previous event, then the previous event is considered the actual, not proximate cause. The police would not have shot the other person but for the perpetrator pointing a gun at someone (and possibly shooting at the police).

IMO, that's not meaningfully different than involuntary manslaughter convictions for allowing unsafe working conditions at a construction site or leaving your loaded gun out where a child can take it, both of which have happened.

True, but only momentarily. At the end of the first depreciation cycle, assuming purchasing of hardware is not accelerating, you're depreciating 5x as much hardware over 5x the time, and your momentary bubble in the stock price is gone.

And even if hardware purchasing is growing right now, eventually, that will flatten out, and the above will be true.

The only real question should be whether the depreciation rate is reasonable. If you're still getting substantial use out of the hardware after five years, then depreciating it over 3 years is questionable.

Also, the more slowly you depreciate it, the less you save on taxes each year. Faster depreciation is beneficial if you think the tax rate will go down and you will lose the benefit of that depreciation. Slower depreciation is beneficial if you think the tax rate will go up and you will benefit more from depreciating it later. So this may also mean that these companies are expecting corporate income taxes to go up. Make of that what you will.

In my experience, with only rare exceptions, the limit should be three. More than three, and you are likely involving people working on multiple projects who don't really need to know what the people on other projects are doing beyond what an email every few months would provide.

Those rare exceptions are situations where you have a meeting of managers in an org or similar with each other, where everybody is working towards the same goals, and they're planning towards those goals.

Or the way I usually describe it is that the usefulness of a meeting with n participants is one over the square of n minus 2 for all values of n greater than 2.

Depends on what the person was doing at the time. If the person who didn't pull the trigger was holding up a liquor store and the police shot the wrong person, there's at least arguably mens rea, which is how we get things like the felony murder rule. Extending that to involuntary manslaughter when the person didn't actually pull the trigger but directly created a situation where the police did seems like not that much of a stretch to me.

To my knowledge, you are pedantically correct, but that doesn't mean you aren't in legal jeopardy for the death; you just won't face murder charges. You could still very easily be hit with civil wrongful death claims, and maybe negligent homicide or involuntary manslaughter charges for creating the situation that led to that death.

So, buy the DVD.

With Netflix, I'm afraid we'll have to pause the movie to put the kids to bed. Then come back and discover that Netflix has dropped it from their catalog.

As far as I can tell, the Netflix business plan has been about erasing the archives so people will have to watch their new stuff. And if you aren't fast, even their new stuff becomes archival. Then, "Poof!"

Pssst! Hey kid. Wanna buy some vacuum tubes?

Maybe, but only if you assume that the intent is to share that video with others or whatever.

On the flip side, I can think of a lot of useful reasons to do so, mostly involving use of large amounts of AI to go back and process the data. Imagine losing something and being able to ask, "Where is this," and getting an answer about where you left it. Imagine being able to say, "Was [insert person] part of the conversation where I said [insert subject]" and getting an answer. The potential impact of always-on recording for assisting with memory recall is enormous, assuming adequate storage and processing power.

Also, it completely solves the "You look familiar" problem, both in the "Did I meet this person?" sense and in the "What is his/her name?" sense.

Nope. Not true. You can't use it commercially, but the definition of commercial use excludes a lot of things that you might think are commercial, e.g. any form of artwork, book covers, Facebook posting, etc.

This doesn't give you the right to record someone who has asked you not to record them, though, especially if there is audio and it is a two-party consent state. And if you are deliberately confronting someone in public who asks you not to record them, it could also run afoul of harassment laws.

I have an even more radical proposal. Roll back copyright duration to 28 years, but only for works for hire.

• Works of corporate authorship (movies, etc.): 14 +14 (renewal required).
• Works of individual authorship: 50 years or the life of the author, whichever is longer.

This strikes a balance that acknowledges individuals' lower ability to earn money off of a work, and ensures that individuals are able to continue benefitting from their works for the rest of their lives, while still ensuring that musical works written when my long-deceased grandparents were children are no longer locked away where no one can perform them without expensive licensing and ensuring that people who never contributed anything towards the works' creation (e.g. the grandchildren of a composer, author, or artist) don't get to live off of other people's work for the rest of their lives.

It was broken long before that. Minivans have always been treated as light trucks despite not being trucks in any meaningful sense of the word, and industry interference has prevented light truck standards from keeping up with technological improvements.

As long as we have such a culture of regulatory capture, I don't think these sorts of standards are ever going to do what they are intended to do.

Are there states that don't allow that? I know Tennessee and California both do, though the latter is somewhat more problematic because of emissions control laws.

The "at your own peril" thing is a lot easier to justify when you have high situational awareness because of absolutely no expectation of safety in a low-speed collision (bicycle) than when you do have that expectation (vehicle with a roll cage).

Also, bicycles can't rapidly accelerate, are very small, and generally can't get very fast at all, so they are quick to pass compared with something the size and speed of a low-speed car. This reduces the risk of them causing accidents significantly (both with the bicycle and with oncoming vehicles).

In general, the assumption is that if it looks like a car, it should act like one. When that assumption is violated, bad things happen.

America's pedestrian accident rate is increasing primarily because of pedestrian distraction, not because cars are getting less safe. The fatality rate could be caused by cars getting less safe, but not the rate of accidents, except to the limited extent that touchscreens make driving harder.

If you really want pedestrian accidents to stop happening, you need to do three things:

• Mandate that all intersections have a separate pedestrian cycle with a button to activate it or camera-based pedestrian detection.
• Mandate that all intersections have appropriate light control over right turns on red, such that they are not allowed during the pedestrian cycle.
• Strictly enforce this for both drivers and pedestrians for the first few months, ticketing both pedestrians and drivers when they enter an intersection at the wrong time.

This ensures that A. cars don't have to wait for pedestrians that don't exist, B. cars have to wait for pedestrians only once even if the pedestrians are crossing in multiple directions, and C. no cars are in the intersection at the same time as pedestrians.

It improves road throughput for both pedestrians and drivers *and* makes the intersections safer. There's not much downside to this.

Your conditions warrant medical (mental health) treatment and education. Which should be aimed at enabling you to handle the university, employment and the world with the tools that enable you to deal with life. From that point on, a university should treat you as any other student. You either can or can not handle the work given you. Either with the abilities you were born with or those tools our health care system should provide you with.

It is unreaonable for every institution to have to maintain (at their expense) duplicated programs to handle every case that comes along. Where I went to public school, the district had excellent, off campus programs for special needs students. Where they could concentrate the care resources to efficiently handle cases. Instead of expecting the general school faculty to dedicate any extra time to handle them. With the hit or miss skill set that would result. The problem with this approach is that parents of little Beavis would be appaled by the neighbors noticing him loading onto the short bus every morning. Other school districts, unable to deal with this parental pressure just mainstreamed everyone. To the disadvantage of those in need of special help.

Why?

Odds are that, if I'm building a flat pack on my system, I've built the application from source. So the dependency issue doesn't exist. Because they were checked by the build scripts (in any competent source distribution I've ever seen). Or the binary was downloaded through a package manager which also handles dependencies.

For some small s/w house or within a company for enterprise apps, maybe. But there are already tools for this.