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

 



Forgot your password?
typodupeerror
×

Comment Re:Errrm, .... no, not really. (Score 1) 94

That was 12 years ago. A 12 year out of date critique of a web technology that has had ongoing language updates and two entire rewrites in that interval should be viewed with some suspicion. Also, are you really just citing the title of the article and none of the content?

I'm not even defending PHP here, just questioning lazy kneejerk, "but it sucked once, so now I hate it forever" thinking.

Comment Re:A Voyager 4? (Score 1) 80

I'll disagree a little bit: we have heavy lift rockets bringing mass to orbit at a greater rate than any time in history and new larger and more efficient rockets on the cusp of being brought to use, with next generations planned for the future. Space launch technology -- the actual raw launching of mass to orbit, where it can be useful -- has advanced. And mass to orbit means more fuel -- if we really wanted to get something out there faster.

And that's where our statements arrive at the same conclusion: there's little need to do anything but super efficient deep space probes. While I can quibble with your implied assertion about newer technology not making a difference in ability, in a practical sense given our funding of deep space research, the big tech upgrade has been to data collection devices and communication. We'll have to have way cheaper lift capability before extra fuel to cut time off a project makes any kind of sense. But it is now at least plausible as an option.

(Also, this appears to be the only thread that isn't making Trek or Aliens jokes)

Submission + - JPEG XL won the image format wars. It's time to embrace it.

ergo98 writes: Now that Apple has thrown-in behind JPEG XL, with the format supported on their upcoming software releases — both in the Safari browser and in the various OSs, immediately providing support in app media components — in the next few months the deployed base of compatible devices will explode exponentially.

By year end over a billion devices will support JPEG XL. We can finally take advantage of much better visual fidelity, alpha channels for photographic images, HDR, and numerous other advances.

The time to leave JPEG behind, or at least relegate it to a compatibility shim, has arrived.

Submission + - SPAM: Understanding Floating Point numbers

ergo98 writes: While we've all spent years using single- and double- precision floating point numbers, machine learning has led to some intense optimizations and specializations, yielding loads of new FP types including some so extreme that they fit in 4-bits and host zero mantissa bits (e.g. E3M0).

It can be unintuitive to grep, but this page gives some interactive examples that make it easier to understand. Even if you never need to directly flip or interpret the bits of an FP number, it's important to know the real strengths and weaknesses.

Link to Original Source

Comment Re:Where's the story? (Score 1) 110

By his own narrative, it wasn't creating PowerShell specifically that got him demoted. It was doing "unassigned" work during work hours.

He details that it was specifically that Microsoft did/does not have the 80/20 type thing some competitors have, where you get some time to free range random concepts and ideas, so some pissy middle manager got mad that he wasn't going through the whole project approval (you know, the let everyone comment on the color of the shed stage) and he got demerits.

Comment Re:It may not be possible to mitigate (Score 1) 67

*What is YOUR source for this. Do you even have one?*

THE PAPER THAT WAS SUBMITTED. They are very open about the *incredibly* narrow known threat model (basically ASLR pointer obscuring *in the same process*), albeit -- as all papers do -- opining that maybe there is something worse that could be done. These sorts of security papers come out by the dozen per year, and generally no, there isn't any further risk, and the latent risk is negligible to irrelevant.

To be clear, when security researchers are pitching a novel vulnerability, the foundation of their claim is a proof of concept, because the chasm between "well it could...." and the actual can be enormous. No proof of concept. Not even a vague inclination of the knowledge of how to make a proof of concept. And this issue has been very widely disseminated, every hacker group pounding on Augury -- theoretically it is trivial to exploit on an array of pointers -- and no one else has a proof of concept yet. Weird, right?

Comment Re:It may not be possible to mitigate (Score 1) 67

"No bias there at all."

Because I have an M1 Mac I have a "bias"? Yeah, not really. I'm typing this on an Intel box. I have servers on AMD, Graviton 2, among many others. That's a modern life.

"Sources are people in the security industry in which I work."

ROFL. Yeah, no you don't. You are claiming ridiculous things.

These sorts of "you know it *could* hypothetically be exploited" (in a profoundly narrow sense) security papers come up by the dozens per month. The overwhelming majority have no real impact whatsoever. This one is particularly spurious.

The "amateur hour" bit in your comment was particularly hilarious, and betrayed that you're just some guy saying dumb stuff.

Comment Re:It may not be possible to mitigate (Score 2) 67

What source says it's "impossible to mitigate this"? Do you have even one?

Because the notion is preposterous. Not only is this largely a theoretical attack (I'm being generous by not calling it a fully theoretical attack), with extremely little real world consequences, mitigations are *trivial* if it were something real.

"I really want Arm on the workstation and server to succeed."

You seem to know literally nothing about security or chip design, and decided to post some tosser, laugahble anti-Apple screed. Me, I'll keep using my M1 Mac, and have been using ARM on the server for half a decade now. Hurrr.

Comment Re:Yeah... Elon says a lot of thing.... (Score 1) 260

"Last time I checked the public statistics, it's actually already doing that."

Tesla's stats on this are incredibly deceptive.

Firstly, the only place where Tesla drivers engage autopilot is on highways. The accident rate on highways is dramatically lower than city streets and aren't separated out, yet Tesla compares their autopilot numbers of that overall number. Highway driving is the baby first steps of self driving.

Secondly, Tesla drivers already are significantly less likely to be in accidents minus any of the aids. 1 accident per 1.82 million miles for Tesla drivers, versus 1 accident per 479,000 miles for the average vehicle. Again, this is with zero of the assists or safety aids in the Tesla. This is courtesy, presumably, of newer cars (older vehicles are in far more accidents) and perhaps a more enthusiast owner who is more attuned to the world.

Elon Musk has been pitching full self driving for years, increasingly trying to get buyers to pay for a product they aren't actually getting. And I'm sure Elon is looking at the progress and thinking "wow, we're at 95%...only the last little bit left", but in realms like this that last 5% takes 5000% of the time and effort.

Comment Re:No it's not (Score 4, Interesting) 510

Ah, the death certificate claim. This is an argument presented by two types of people-

a) Liars and people who just want to see the world burn
b) The gullible who have been misled by a) and just don't realize it

The CDC gets death certificates often with MONTHS of delay. If you track their counts in real time, past periods will continually percolate up as death certificates from all causes eventually make their way to the CDC.

https://www.cdc.gov/nchs/data/...

The CDC gets COVID-19 data very rapidly because it's a pandemic. They get data on every other cause of death much more slowly.

It's remarkable how virtually any topic gets exploited and misdirected by people who just like trolling the world.

Comment Re:So... (Score 1) 510

Currently the deaths / known cases (positive tests) = 5% CFR

If 10x more people have had COVID-19 than known (e.g. 25 million rather than 2.5 million), that would make the CFR 0.5%. Which would still be terrible, as an aside.

If we assumed 100X more people had it than known, that would still be a CFR of 0.05%, which would still be quite bad for a highly viral disease. But given the spreading patterns of the virus, that is clearly and obviously not even remotely possible.

Slashdot Top Deals

"Why can't we ever attempt to solve a problem in this country without having a 'War' on it?" -- Rich Thomson, talk.politics.misc

Working...