Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Submission + - Slashdot poll: Best cube 3

An anonymous reader writes: 1. Rubik Cube
2. The Cube (movie)
3. Tardis Siege Mode
4. Lament Configuration
5. Weighted Companion Cube
6. Borg Cube
7. The Inhibitors (Revelation Space)
8. Icecube

Comment Re:It's paid for. (Score 1) 189

Nope, that's not what killed it. Ethernet was just as bad before hubs and then switching came along -- even with hubs, one bad ethernet card could take down the whole broadcast domain, and did with some frequency. And with thinnet wiring (coax to the younglings) all it took was one marginal connector, anywhere in the loop, to kill the whole network. Don't even get me started on thicknet.

What killed it was money. Ethernet became very cheap to implement. Once everything moved to a star topology (hubs, then switches) the advantages of Token Ring were not worth the additional cost. Ethernet benefitted from being able to advertise higher bandwidths (10mbps, then 100mbps, vs. TR's 4/16 then, too late, 100) -- the perception was, "why would I want 16mbps token ring when I could have 100Mbps ethernet for less money?" Ethernet wasn't really any faster, and was often slower due to collisions, but everybody just looked at the total bandwidth. Once switch ports got cheap, collisions were no longer an issue and Token Rings fate was sealed.

Of course, Arcnet had a star topology long before Ethernet or Token Ring. But it too suffered from low nominal bandwidth.

Comment Re:It's paid for. (Score 2) 189

Listen up, Junior ...

In some ways, Token Ring was very much superior to Ethernet. A hospital I worked for in the late 90's had a huge (1000 nodes) 4Mbps TR, all as one big subnet, built long before switches came along. If you tried to do that with Ethernet, it would have crashed and burned in a week. This was, on the whole, pretty reliable (if slow). The downside was that if one card in the ring failed, the whole thing would generally die. So it was great until the 10 year old TR cards started failing regularly due to capacitors failing. We ended up replacing the whole thing with 100Mbps switched ethernet, which wasn't really noticeably faster despite a 25-fold increase in nominal bandwidth, and failed more often. :)

Submission + - Comcast Forgets To Delete Revealing Note From Blog Post

An anonymous reader writes: Earlier today, Comcast published a blog post to criticize the newly announced coalition opposing its merger with Time Warner Cable and to cheer about the FCC’s decision to restart the “shot clock” on that deal. But someone at Kabletown is probably getting a stern talking-to right now, after an accidental nugget of honesty made its way into that post. Comcast posted to their corporate blog today about the merger review process, reminding everyone why they think it will be so awesome and pointing to the pro-merger comments that have come in to the FCC. But they also left something else in. Near the end, the blog post reads, “Comcast and Time Warner Cable do not currently compete for customers anywhere in America. That means that if the proposed transaction goes through, consumers will not lose a choice of cable companies. Consumers will not lose a choice of broadband providers. And not a single market will see a reduction in competition. Those are simply the facts.” The first version of the blog post, which was also sent out in an e-mail blast, then continues: “We are still working with a vendor to analyze the FCC spreadsheet but in case it shows that there are any consumers in census blocks that may lose a broadband choice, want to make sure these sentences are more nuanced.” After that strange little note, the blog post carries on in praise of competition, saying, “There is a reason we want to provide our customers with better service, faster speeds, and a diverse choice of programming: we don’t want to lose them.”

Comment 42 years old here.. (Score 4, Interesting) 376

And still technical. 100% technical. There have been a few cases where I felt like I was denied a job because I was too old ... "not a good fit with company culture" and that sort of thing... but as others have said, those companies just disqualified themselves.

The reality is that I'm a better programmer now than when I was 25. I havre a much better understanding of "craftsmanship" -- things like testing, documentation, making sure my code is not "brittle" -- even though my ability to devour new technologies has slacked a bit.

Comment Re:Actually doubles in 60 days (Score 1) 244

You are, of course, correct. And my round figure of 60 days is only a round figure. Anyone who is interested can try it themselves, with as much accuracy as they needed.

I had actually noted this the |irst time I tried to comment, but I went to log in, and my comment evaporated.

Specifically, I had said that if you believed the data, it was 60 day doubling. But if you didn't, you had to go back to the previous curve.

We will find out, in time, whether the infection rate was on the slower curve shown, or at the faster, previous rate.

Comment Actually doubles in 60 days (Score 4, Interesting) 244

Regardless of sourcing the information, the information is incorrect. According to this graph, Ebola is doubling every 60 days now -- so there has been some improvement.

Best way to keep up on this, that I can tell, is to google "ebola africa timeline wiki", and pan down to the timeline, near the bottom of the article. You'll see the graphs.

My favorite graph for keeping track is the logarithmic scale based on population , because it's easy to see where infection totality is: it used to be at 1 1/2 years, and now is about 5 years out.

Another thing of interest that I noted, though: The infection rates before a country mounts a serious response, can be as fast as doubling every 3 or 5 days. For that reason, I think our CDC's active attempts to STOP a proper response, was the worst thing they could do.

Just something to think about.

Submission + - What Does The NSA Think Of Cryptographers? (i-programmer.info)

mikejuk writes: A recently declassified NSA house magazine, CryptoLog, reveals some interesting attitudes between the redactions. What is the NSA take on cryptography?
The article of interest is a report of a trip to the 1992 EuroCrypt conference by an NSA cryptographer whose name is redacted.We all get a little bored having to sit though presentations that are off topic, boring or even down right silly but we generally don't write our opinions down. In this case the criticisms are cutting and they reveal a lot about the attitude of the NSA cryptographers. You need to keep in mind as you read that this is intended for the NSA crypto community and as such the writer would have felt at home with what was being written.
Take for example:
Three of the last four sessions were of no value whatever, and indeed there was almost nothing at Eurocrypt to interest us (this is good news!). The scholarship was actually extremely good; it’s just that the directions which external cryptologic researchers have taken are remarkably far from our own lines of interest.
It seems that back in 1992 academic cryptographers were working on things that the NSA didn't consider of any importance. Could things be the same now?
The gulf between the two camps couldn't be better expressed than:
The conference again offered an interesting view into the thought processes of the world’s leading “cryptologists.” It is indeed remarkable how far the Agency has strayed from the True Path.
The ironic comment is clearly suggesting that the NSA is on the "true path" whatever that might be.
Clearly the gap between the NSA and the academic crypto community is probably as wide today with the different approaches to the problem being driven by what each wants to achieve. It is worth reading the rest of the article.

Slashdot Top Deals

If all else fails, lower your standards.

Working...