Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror

Comment Re:Cell phones? (Score 0) 223

Something that is long overdue when it comes to cell phone standards is protocols to force phones to switch off where they are not wanted.
If something like that had existed and been in widespread use, it could have been used here to prevent calls and/or detect phones within the protected area.

Other places where such a system is warranted would be in movie theatres and near MRI machines at hospitals.

But of course, if cell phones did not work inmates would just switch to walkie talkies.

Comment Re:You Have Got To Be Kidding Me (Score 1) 184

Was it really Model M or Model F keyboards, and did you sell them for a reasonable price?

Too often on eBay I see sellers trying to sell some vintage but crap rubber dome keyboard for much more than it is worth. I recon that they must have seen some real collectors' item sell for a lot and not recognised what made that one more special.
And yes, different markets are different and prices fluctuate. In the US, the going price was around $30 for a regular Model M a few years ago, but over here in Sweden the going price has been up to $180 recently.

Comment Re:How is this better than a Model M? (Score 4, Interesting) 184

Some connoisseurs find that the Model F's mechanism has a somewhat nicer feel than the Model M's.
Because the sensing is capacitive and not using a measly membrane, the mechanism is more durable and allows for N-key rollover.

Also, Unicomp does not make the Model M in a compact form factor (relatively speaking). IBM used to have a Space-Saving Keyboard back in the day, but vintage "SSK"s on the second-hand market are quite sought-after and therefore pricey.

The build-quality of the buckling spring keyboards has also gradually gone down throughout the years. The Model F keyboards of old had case parts of parts of metal. Even the first Model M keyboards weight about half a kg (about a lb) more than those Model M keyboards made by Unicomp (and the last IBM-branded ones before that).

Comment Re:Linux Bad Press.. (Score 1) 551

Oh, the GNOME 3 developers already did that years ago.

Not only did they foul up GNOME itself, they also took it on themselves to foul up the mainline GTK+ 3.0 toolkit which thousands of non-GNOME 3 applications use.
On the surface, many widgets work really weird compared to how they used to do on GTK+ 2.0 (and how they do on Windows and MacOS as well). For instance, sliders and scroll bars are now practically unusable (for those who still use them with mice and not just scroll wheel).
When you look deeper you will find that they have introduced API changes on minor version numbers without pushing different dynamically linked libraries, thus making programs written for earlier revisions of the library crash or behave in weird ways. Seriously, that is a cardinal sin.
It is as if some other OS vendor had paid them to do as much damage as they can.

Comment Re:BTW, AMD has a similar bug too (Score 1) 135

Your post is a typical example of the behaviour that has hindered proper discussion on this problem.
People read half of one paragraph from one forum-post and half of a paragraph in another thread and then post a knee-jerk response to something they don't understand.

Comment BTW, AMD has a similar bug too (Score 5, Interesting) 135

AMD Ryzen also seems to have a similar bug, related to hyperthreading that happens only in very special circumstances.

Quite a few Ryzen users have experienced instability problems during heavy compilation loads under Linux, especially those using compile-based distros such as Gentoo, but also under the Ubuntu subsystem on Windows.
There has been some debate whether the problems would have been caused by an actual bug, or if the people who experienced them simply had an unstable overclock - the latter being something that has also cropped up in forums recently.

Matthew Dillon, of Dragonfly BSD fame (and Amiga fame before that...) does believe that he has found a reproducible bug. He sent a test case about it to AMD in April.
This is not the first time Dillon has found a hardware bug in a AMD CPU. He found one for an earlier AMD CPU back in 2012 which was fixed in a microcode update.

I expect this to be fixed in a BIOS/microcode update soon, if not already in AGESA 1.0.0.6 - but I have yet to see any confirmation that it would have been fixed.

Comment Would not work (Score 3, Insightful) 95

The point of having a law that bans texting while driving is to prevent accidents, not to punish people who cause accidents.
Therefore, having a law worded to ban only "careless or imprudent manner" is effectively pointless for prevention.
No idiot who is going to cause an accident will believe beforehand that they are going to do so. That is why accidents are called "accidents".

Comment Re:Metal 2? Idiocy (Score 0) 205

I think that Apple does not want users to be able to run comparable benchmarks and find out how much less graphics horsepower their machines have compared to gaming PCs.

It might also be emotional: that they don't want Macs to even approach the world of PC gaming, with the aesthetic and community that it has being so different from the Apple image.

Comment Re:Who are the people on the graph using both?!? (Score 1) 515

There could be many explanations:
* GNU style formatting of block statements put braces on their own lines, indented half-way.

* Respondents refer not to left-side indentation but to how they line up comments, member names, parameters etc. This can be fidgety when using tabs only (unless you are using elastic tabs) and using spaces for this would make it independent of tab size.

* Other things indented half-way: Preprocessor statements, labels, etc. Indenting of #ifdef's around code become independent of the code it surrounds, switch-case statements don't become so deep. You could also argue that classes (and functions...) become more readable.

Comment Re:Both? (Score 1) 515

People who use both might be using GNU indenting style
where braces are indented half-way between the indenting outer and inner blocks.

Myself, I indent labels and preprocessor directives in C (and like languages) with two spaces less and the rest with four-space tabs.
That way, #ifdef's for disabling code does not affect the indentation of the code they disable and e.g. switch-case statements don't get indented so deeply.

Slashdot Top Deals

"In order to make an apple pie from scratch, you must first create the universe." -- Carl Sagan, Cosmos

Working...