Priest's invention would make those old phone lines faster than anything on the market, decimating the communications speed limit.
What a terrible mixing of metaphors! Save for the obvious contextual cues in the first part of the sentence, I would read the phrase as "reducing the communications bandwidth by some fraction".
A better choice would be "obliterating" or some similar word without a numerical connotation.
It's truly disappointing that these devices are being used to rake in cash in the name of public safety, especially when the same input data could be used to make the interesections work "better", e.g. minimize the possibility that a car will run a yellow, decrease or increase (to prevent speeding) the stop time at intersections.
We need to finally be beyond the era where a driver has to wait at an empty intersection at 3AM for a light to change.
In my experience with mid- to large-sized companies, I've found that legal departments freak out about licenses that were not developed in-house, regardless of the actual content of the license. In fact, it's quite similar to the "NIH" complex that some engineers develop. ("We can't use that RTOS because , we've got to spin our own.")
Slashdot Mirror
From the article:
.
/.'ers
Priest's invention would make those old phone lines faster than anything on the market, decimating the communications speed limit.
What a terrible mixing of metaphors! Save for the obvious contextual cues in the first part of the sentence, I would read the phrase as "reducing the communications bandwidth by some fraction".
A better choice would be "obliterating" or some similar word without a numerical connotation
- one of the five English nit-picking
It's truly disappointing that these devices are being used to rake in cash in the name of public safety, especially when the same input data could be used to make the interesections work "better", e.g. minimize the possibility that a car will run a yellow, decrease or increase (to prevent speeding) the stop time at intersections.
We need to finally be beyond the era where a driver has to wait at an empty intersection at 3AM for a light to change.
In my experience with mid- to large-sized companies, I've found that legal departments freak out about licenses that were not developed in-house, regardless of the actual content of the license. In fact, it's quite similar to the "NIH" complex that some engineers develop. ("We can't use that RTOS because , we've got to spin our own.")
Bleak software winter
Cleave Microsoft into three!
Spring will soon return
Comments Containing A Copy of the Specification:
"by Anonymous Coward on Tuesday, May 02, @03:37PM EST (#197)"
"by BlueUnderwear on Tuesday, May 02, @04:09PM EST (#239)"
"by BlueUnderwear on Tuesday, May 02, @04:15PM EST (#248)"
"by smartin on Tuesday, May 02, @02:20PM EST (#86)"
Comments Containing Links to Internet Sites with Unauthorized Copies of the Specification:
"by ka9dgx on Tuesday May 02, @2:52PM EST (#133)"
Comments Containing Instructions on How to Bypass the End User License Agreement and Extract the Specification:
"by myconid (my S conid@ P toge A the M r.net) on Tuesday May 02, @07:27PM EST (#362)"
"by markb on Tuesday May 02, @05:47PM EST (#321)"
"by Sami (respect.my@authorita-dot-net) on Tuesday May 02, @01:47PM EST (#19)"
"by iCEBalM (icebalm@[NOSPAM]bigfoot.com) on Tuesday May 02, @01:52PM EST (#33)"
"by Jonny Royale (moc.mocten.xi@notners) on Tuesday, May 02, @01:59PM EST (#51)"
"by rcw-work (rcw@d.e.b.i.a.n.org.without.dots) on Tuesday, May 02, @07:12PM EST (#353)"