There are times when you hit the light behind a slow car, enter on green, exit on red.
Let's assume the intersection is 50 feet wide (about 2 lanes in each direction) and the yellow is 3 seconds (the low end of the recommended range). Then the slow car is moving at less than 50 feet/3 seconds, or about 10 MPH. If traffic is moving that slow, then there's most likely a traffic jam just beyond the intersection and a risk that you wouldn't get through anyway. And even if there isn't, then it's still so slow that stopping and starting again isn't a big deal.
Then there's the 101 crossing on Fair Oaks where two lights are a hundred feet apart and if you pull off the first one, about half the time, the second one starts to change while the front car is still accelerating, so you don't have time to switch pedals, and thus you either gun it and run it or you end up stopped in the middle of the intersection!
The answer is, don't even start moving until the people in front of you move up enough for you to clear the intersection!
I thought it was 1-1.5 seconds per every 10 MPH of the speed limit. 45 MPH zone = ~4-6 seconds.
They become pretty much equivalent, once you realize that nobody puts a traffic light on a road where the speed limit is less than 30MPH (or more than 60MPH) anyway.
Did you ever see the video where a group of vehicles decided to drive 55 MPH maximum (I think it was in the DC beltway).
Nope, that was on the Perimeter (I-285, around Atlanta). IIRC, it was a group of Georgia State University students who performed the experiment.
It's too bad they only did it that one day; if somebody started a club to do that consistently then we'd see a big change in Atlanta's transportation policy, real quick.
When the light turns red, staying put would be even worse than going, so you go
More importantly, already being in the intersection means that you're not breaking the law when the light turns red -- it's only illegal to enter it under a red light.
The trick is to measure the volume of through traffic on both streets per hour on weekdays and weekends and adjust the light timings accordingly, finding the "sweet spot" between causing congestion due to long waits and causing accidents due to short waits.
Highway engineers already have enough trouble as it is trying to find the "sweet spot" between causing congestion due to long waits and causing congestion due to short green durations. Adding another constraint is likely to make the system unsolvable.
(Note: I am a civil engineering student, and I have taken a course on this.)
Also, understanding pointers and how memory is laid out is a pretty fundamental thing, wouldn't you say?
Exactly! Even in Java, if you don't understand the difference between duplicating an object vs. operating on a reference, your code could easily be really slow (because you're making 10,000 copies when you don't need to) or wrong (because you're overwriting data and don't realize it). Paying attention to memory is important!
But it turns out that unemployment is not massively high. Trade has gone up substantially in the post-NAFTA era, but unemployment has gone down.
On the contrary, "unemployment" only counts those people who are still "actively looking" for jobs.
It doesn't count people like my father, who got laid off in February 2007, gave up looking last Fall, and now calls himself "retired" even though he hadn't intended to retire yet and doesn't have as much money as he wanted saved up.
It also doesn't count people who are underemployed -- people who used to be making $75K/year as white-collar workers, and now flip burgers at Mickey D's. And that particular statistic, I believe, has gone way up.
Those consumers used to be employed at Schwinn, and now they've starved to death in the gutter. They're not consumers anymore!
Instead, the new consumers are the Chinese working at the outsourced Schwinn factory. They're doing just fine on their shiny new bicycles.
It's a great deal for the people the work gets outsourced to, but not so great a deal for the corpse in the gutter the work got outsourced from. Do you get it now?!
Remember, going to 64-bit on x86 can make programs faster, but not because of the extra bits. The speedup comes from the fact that, in addition to increasing the bits, AMD also added a bunch of extra registers to the spec.
The problem is that Lincoln and others after him have been pissing on it when convenient
Can someone illuminate what is meant by this?
It was the states that originally ratified the Constitution, which they only could have done if they were sovereign. Some people believe that, since the states had sovereignty to enter into the Constitution then they also must have sovereignty to leave it. But when South Carolina (and the rest of the South) actually tried to exercise that sovereignty, Lincoln made war on them and forced them to recognize the sovereignty of the Federal government instead.
Before the Civil War, the Federal government had very little power and the individual states had quite a lot; after the Civil War it was the opposite, and the balance has only continued to further shift (particularly under FDR) since.
The thing I find mosy annoying about Firefox 3 is that it's STILL not a native cocoa app.
Of course it's not a native cocoa app! It's a XUL app, where XUL is Mozilla's own cross-platform widget toolkit. And it has to be a XUL app, because extensions have to be able to modify the UI and extensions are written in XUL. And extensions have to be written in XUL, because they have to be cross-platform. And Firefox has to support extensions, because otherwise it wouldn't be Firefox anymore.
Bottom line: if you want a Gecko browser that's a native cocoa app, use Camino. If you want a browser that supports extensions, use Firefox. You will never, ever be able to have a single app that does both, because XUL and cocoa are different, incompatible technologies.
I don't know about your definition of "just now" or your definition of "development releases" but it seems to me that you're way off on at least one of those.
Does any version of Firefox less than or equal to 2.0.0.13 (the current released version) pass Acid2? No? Then any builds of Firefox that do pass are development releases!
Or the Firefox developers (and you) could stop being stupid and realize that the address bar is just that: a bar for typing in addresses! If you want a bar to have some fancy searching going on when you type in "bank," use the fucking search bar for it!
Something else could be that I filed for a patent before I introduced my software and it took 5 or 10 years to get through the process before being granted. This has happened a couple of times recently where something had been in use for so long, it is almost a standard way of doing something before the patent is awarded but the application was originally filed in the mid 90's or so.
Releasing code that implements something that's "patent pending" ought to violate the GPLv3 too. (Note that "ought to" does not necessarily mean "actually would.")
You know, I thought this stuff has been hashed enough YEARS ago...
It was!
As far as the FSF is concerned, the rights they believe "people should have to their software" *haven't changed. All that's happened is that the FSF has realized the old version of the license (GPLv2) didn't quite reflect those beliefs completely because of a legal tactic they didn't anticipate.
In other words, they discovered a bug in the license and released a new, patched version to fix it. The intent never changed because it was supposed to be like the GPLv3 (or more accurately, like whatever the final version of the GPL will be) from the beginning)
* Note: "people" refers to users, not developers, and "their software" refers to "software they use," not "software they own the copyright of." See the GNU Manifesto for more info.
Slashdot Mirror
Then those people are not competent to operate a vehicle, and should have their licenses revoked. How's that for a solution?
Where I live, mild speeding is 1 or 2 points; running a stop (sign|light) is 3.
Let's assume the intersection is 50 feet wide (about 2 lanes in each direction) and the yellow is 3 seconds (the low end of the recommended range). Then the slow car is moving at less than 50 feet/3 seconds, or about 10 MPH. If traffic is moving that slow, then there's most likely a traffic jam just beyond the intersection and a risk that you wouldn't get through anyway. And even if there isn't, then it's still so slow that stopping and starting again isn't a big deal.
The answer is, don't even start moving until the people in front of you move up enough for you to clear the intersection!
They become pretty much equivalent, once you realize that nobody puts a traffic light on a road where the speed limit is less than 30MPH (or more than 60MPH) anyway.
Nope, that was on the Perimeter (I-285, around Atlanta). IIRC, it was a group of Georgia State University students who performed the experiment.
It's too bad they only did it that one day; if somebody started a club to do that consistently then we'd see a big change in Atlanta's transportation policy, real quick.
More importantly, already being in the intersection means that you're not breaking the law when the light turns red -- it's only illegal to enter it under a red light.
Highway engineers already have enough trouble as it is trying to find the "sweet spot" between causing congestion due to long waits and causing congestion due to short green durations. Adding another constraint is likely to make the system unsolvable.
(Note: I am a civil engineering student, and I have taken a course on this.)
Ha ha ha ha ha ha ha! Oh man, that's the funniest joke I've heard in a long time!
Well, Comcast even violates that! In fact, by forging packets Comcast is making its "best effort" to prevent service!
Exactly! Even in Java, if you don't understand the difference between duplicating an object vs. operating on a reference, your code could easily be really slow (because you're making 10,000 copies when you don't need to) or wrong (because you're overwriting data and don't realize it). Paying attention to memory is important!
On the contrary, "unemployment" only counts those people who are still "actively looking" for jobs.
It doesn't count people like my father, who got laid off in February 2007, gave up looking last Fall, and now calls himself "retired" even though he hadn't intended to retire yet and doesn't have as much money as he wanted saved up.
It also doesn't count people who are underemployed -- people who used to be making $75K/year as white-collar workers, and now flip burgers at Mickey D's. And that particular statistic, I believe, has gone way up.
Those consumers used to be employed at Schwinn, and now they've starved to death in the gutter. They're not consumers anymore!
Instead, the new consumers are the Chinese working at the outsourced Schwinn factory. They're doing just fine on their shiny new bicycles.
It's a great deal for the people the work gets outsourced to, but not so great a deal for the corpse in the gutter the work got outsourced from. Do you get it now?!
No, MFC is like Cocoa (object-oriented and all that, C++ vs. ObjC). Carbon is more equivalent to the Win32 API (both procedural C).
What do you mean, "moment's notice?" Apple has been telling people to switch to Cocoa for years and years now, ever since 10.0 came out!
Remember, going to 64-bit on x86 can make programs faster, but not because of the extra bits. The speedup comes from the fact that, in addition to increasing the bits, AMD also added a bunch of extra registers to the spec.
Weren't the Articles of Confederation entirely superseded by the Constitution?
It was the states that originally ratified the Constitution, which they only could have done if they were sovereign. Some people believe that, since the states had sovereignty to enter into the Constitution then they also must have sovereignty to leave it. But when South Carolina (and the rest of the South) actually tried to exercise that sovereignty, Lincoln made war on them and forced them to recognize the sovereignty of the Federal government instead.
Before the Civil War, the Federal government had very little power and the individual states had quite a lot; after the Civil War it was the opposite, and the balance has only continued to further shift (particularly under FDR) since.
Of course it's not a native cocoa app! It's a XUL app, where XUL is Mozilla's own cross-platform widget toolkit. And it has to be a XUL app, because extensions have to be able to modify the UI and extensions are written in XUL. And extensions have to be written in XUL, because they have to be cross-platform. And Firefox has to support extensions, because otherwise it wouldn't be Firefox anymore.
Bottom line: if you want a Gecko browser that's a native cocoa app, use Camino. If you want a browser that supports extensions, use Firefox. You will never, ever be able to have a single app that does both, because XUL and cocoa are different, incompatible technologies.
Does any version of Firefox less than or equal to 2.0.0.13 (the current released version) pass Acid2? No? Then any builds of Firefox that do pass are development releases!
Or the Firefox developers (and you) could stop being stupid and realize that the address bar is just that: a bar for typing in addresses! If you want a bar to have some fancy searching going on when you type in "bank," use the fucking search bar for it!
But "oldbar" should be the default, and the new thing should be the extension!
Releasing code that implements something that's "patent pending" ought to violate the GPLv3 too. (Note that "ought to" does not necessarily mean "actually would.")
Not really; the software license is only dictacting lack of mis-features of the hardware.
It was!
As far as the FSF is concerned, the rights they believe "people should have to their software" * haven't changed. All that's happened is that the FSF has realized the old version of the license (GPLv2) didn't quite reflect those beliefs completely because of a legal tactic they didn't anticipate.
In other words, they discovered a bug in the license and released a new, patched version to fix it. The intent never changed because it was supposed to be like the GPLv3 (or more accurately, like whatever the final version of the GPL will be) from the beginning)
* Note: "people" refers to users, not developers, and "their software" refers to "software they use," not "software they own the copyright of." See the GNU Manifesto for more info.
But your patent would still be destroyed anyway, so it doesn't matter.