Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Comment Re:Not Sound (Score 1) 53

Blowing to push something away is trivial, yeah. Blowing at something to pull it towards you, though, is a wee bit harder.

That's why it's a dumb way to describe what's going on. Speakers, transducers, even static column speakers, none of them just push — every time they push, they pull just as much. But you can change the speed at which they do each thing...

Comment Re:and your solution is? (Score 2) 429

Why? Intel had to recall Pentiums due to the FDIV bug and that was arguably way less serious than Meltdown.

That was just P54Cs. This is every intel processor since the Pentium Pro. And many of the motherboards will require BIOS updates to take a newer processor, so even if Intel could make new processors which fit into the same package and solve these problems, they literally wouldn't work in a huge number of scenarios — especially OEM PCs whose BIOS is designed to carefully restrict which processors and memory you're allowed to install.

Comment Re:and your solution is? (Score 5, Interesting) 429

we must fix things with what is possible, no matter how ugly.

Intel went straight to ugly, and did not satisfactorily explore the realm of the possible. Linus perceived this, and announced it to the world. The ball is now in Intel's court. They can be responsible and competent, or the whole world can know that they are the fuckups that they are. It's their call.

Comment Re: Is there any other option, Linus? (Score 1, Informative) 429

AMD has one problem in common with Intel: Spectre. Meltdown is alone Intel's problem.

Not that it's germane to the AMD vs. Intel argument, but IBM got it wrong too. Power7 through Power9 processors are vulnerable to MELTDOWN, and mitigation will be expensive just as it is on Intel.

Comment (edit) (Score 2) 429

Intel chose to behave in this fashion while AMD (and literally everyone else) did it the correct way.

Correction, everyone else but IBM, whose Power7 through Power9 processors are also vulnerable and where mitigation will be expensive. How far POWER has fallen, from the PPC601 where everything was done right... to today. (PPC601 was actually a POWER processor in a sense, in that it actually implemented the full ISA.)

Comment Re:Is there any other option, Linus? (Score 2) 429

To a lay person like me, this sounds like normal design compromises,

I think a normal person could understand that it makes more sense for the security guard to check their ID before they go into a building, not after they have gone into a building and rifled through the filing cabinets. Intel chose to behave in this fashion while AMD (and literally everyone else) did it the correct way.

Comment Re:Is there any other option, Linus? (Score 5, Informative) 429

And fundamental problems are still fundamental problems. The reason practically every processor has the same issues is because

Is because it doesn't. AMD is not vulnerable to MELTDOWN and is less vulnerable to SPECTRE because they are more scrupulous and responsible than Intel, FULL STOP. There is no other reasonable way to regard the situation.

Every speculative processor has some of the same issues, to some degree, but that is not every processor, and you are still using Intel's bullshit excuse FUD language when you say that all processors are vulnerable to these attacks. That is a lie as stated.

Comment Re: A great leap backwards (Score 1) 352

Everyone stopped making giant nukes because they're pointless. It's better in pretty much every way to scatter lots of little ones than detonate one big one.

But scattering lots of little ones pretty much has to be done from the air, which exposes them to counterfire. Attacking from under water is very stealthy, but you can only hit the coastline. If you want to do damage further inland, you either need to get the bomb(s) further inland... or use a much bigger bomb.

Comment Re:Thanks, $15 minimum wage! (Score 2) 243

You seem to think this situation was avoidable. It was not. The higher minimum wage only made it happen faster.

Absolutely... and speed of change is exactly what we don't want. It takes time for people to adapt. Automation is going to displace a lot of people, so it's important that the changeover happen as slowly as possible, to minimize the pain. High minimum wages are a bad idea.

Comment Re:Someone here once posted BPG, it's impressive. (Score 0) 248

BPG is based on HEVC.

Thus making it no better or worse visually than HEIC, which is also based on HEVC intra frames. HEIC's political advantage over BPG, however, is its backing by MPEG.

Fortunately, AV1 is licensed under royalty-free terms

How can the parties participating in AOMedia be sure that no non-participating party holds essential patents that cover AV1?

Comment Because of RTL vandalism (5:erocS) (Score 4, Interesting) 248

At one point, there was a push to make Slash support Unicode better. That ended when vandals figured out how to use bidirectional override code points to spoof moderation scores and otherwise wreck Slashdot's layout. Others used the new code points to post obscene "ASCII art".* That led to a code point whitelist and a halt on further development of Unicode support in Slash.

Rehash, a fork of Slash maintained by SoylentNews PBC, fully supports UTF-8. I don't know exactly what it does with current and future directionality control characters.

* I mean ASCII art in the broad sense: use of characters from other blocks for their glyphs rather than their meaning, in the same way that ASCII art in the strict sense uses Basic Latin.

Slashdot Top Deals

Outside of a dog, a book is man's best friend. Inside of a dog, it is too dark to read.

Working...