katastic

... unless they suffer from the same problem as Intel CPU's Meltdown fiasco. Where the branch prediction runs concurrently with the security checking. The branch predictor hits and speculates, firing the bug, while the security check then decides "that's an invalid branch" and discard it--but it's too late the bug side-effect his occurred.

But I think for it to happen randomly, you'd need an invalid pointer that just so happens to jump to what "becomes" an instruction with a bug, and a branch. That seems pretty rare on first glance.

I love diagnosing Microsoft enterprise frameworks.

Half the time in CRM or NAV, it's either an error code with zero google results, or, "general error."

And yes, I know about tracing.

>* If you get an initial opioid script from a doctor for more than 10 days, you have a 20% chance of being on opioids a year after. Again not a moral failing. [0]

It should be noted that people who are bad enough off to need opiods, may continue to be bad off for a long time. Not because of the opiods, but because of having a condition so bad that doctors are willing to give you opiods.

A script for more than a few days of opiods is very rare. I had a complete back fusion with 21 vertebrae drilled into and only had ~7 days prescribed.

South Park did an episode on this. Where everyone was so afraid of "reality" they elected someone to censor it all and keep their tweets only positive.

Butters had to see every depraved thing. And he ended up trying to kill himself.

And in the end, when he almost died, they blamed him for failing to be the perfect filter.

While I agree, it should be noted ROM is actually incredibly slow by today's standards.

> the freshly installed system boots up in about 30 seconds, including the BIOS doing its thing.

Honest question/clarification, is that... considered fast?

My DOS system used to boot that fast. A C64 is almost instant. And my old ~2013 Chromebook boots in ~7 seconds into Linux with an eMMC drive (slower than an SSD but still fairly fast). It's only got 2 GB of RAM so when it hits swap it'll bog to a standstill so it's often faster just to hit the reset key than try and recover.

WHAT?!

Then shoot those people, or, less hyperbolicly, throw them in prison.

If your cops or military have to live in fear of being murdered for merely wearing their clothes, then your/their country has incredibly serious problems and needs to start treating them directly instead of hiding the consequences.

I have zero frame of reference to understand that kind of environment. I literally can't imagine going out to the store and thinking, "Well, I better not wear that shirt, or I'll be murdered."

Dear downvoter: I dare you to provide logic or a source that rebukes my point.

As usual, the only thing that corporations listen to... is the threat of the dollar.

They didn't give two craps about their policy until this week.

I've created dev environment VM's with classic operating systems (XP, etc) because my job involves updating lots of really old code (most clients only update when they have to, every 5-10 years).

I could definitely see someone doing that with Firefox. They may already exist. I've just, from experience, had so much trouble with compiling large codebases.

On the bright side, the larger a codebase, often, the more popular. And the more popular, the more likely people will have EXACT dependencies listed.

There are various treatments (like Chrome plating) vendors one of my metalworking clients use--all available in the USA.

They compete by being extremely efficient with their use of labor hours and cutting waste. Just-in-time everything.

I'd be careful to extrapolate your direct experience to indicate trends.

The bad guys might wear military clothes...

How does that stop terrorism? The bad guys could just say they're doing official duties.

That's really pathetic that a "consumer ready" embedded piece of software whose whole job is remote-management... needs to be remotely managed because it crashes all the time.

>And you almost certainly can't compile some of them with a modern compiler,

I wonder how long and difficult it must be to get all the required dependencies to compile a modern web browser...

[two hours of obscure error messages later]

"You have v2.3030392.302 of dependency 113, you need to compile v2.3030392.300 in 32-bit first, then build the 64-bit version of v2.3030392.301 then ..."

You get all the compiler errors fixed and then it's on to round two... linker errors.

And then the duplicate doesn't even have the answers you need.

Assembly never stopped anti-virus suites. Where there's a will, there will always be a way.

Without adblock, the majority of web users would be FURIOUS with websites and they'd demand legislative action. Advertisers should shut up and pray they don't poke the hornets nest.

Does it work for usernames?

Here, check mine:

    8ftpenissurvivor

What does that show up as?

In D, I just call super.this(var, var) to ensure I'm calling the correct base constructor. And fire off an assert if super(void) gets called because I didn't explicitly write a specialized one.

But I think C++ has what... parameter lists for that?

I've heard PS/2 was faster (because it's a direct ISA/PCI device / hardware interrupt?), whereas USB can introduce more latency because it has no real-time guarantee and it's packet-based.

https://superuser.com/questions/16893/do-usb-or-ps-2-keyboar...

>There are a number of interesting results, but the point relevant to this question is that there was a fairly significant variance between keyboards, and all the USB keyboards tested had a longer effective scan interval (18.77 ms - 32.75 ms) than the PS/2 keyboards (2.83 ms - 10.88 ms).

>Hopefully Apple will lead the pack again.

Like when they made a calculator that fails to calculate correctly if you push buttons too fast?

https://news.ycombinator.com/item?id=15538666

Definitely applicable because it's talking about UI latency... and Apple.

60's.

Wow, people are butthurt. It's a wildly known fact in the industry. A simple google search for benchmarks or a PDF like this would have satisfied them. But they didn't want the truth they wanted to be butthurt.

https://arxiv.org/ftp/arxiv/papers/1005/1005.2581.pdf

In basically every chart and graph, OpenCL is slower.

OpenCL has a higher level of abstraction, so it's got a higher penalty for it. But, you get cross-platform support. nVidia doesn't optimize for OpenCL either because they don't want you to use it over their own competing framework.

But 'dats cool, keep downvoting, guys. Sources aren't real if you can downvote 'em enough. God, I love Hacker News.

I've actually heard a lot of people say this. At least a couple Ph.Ds, though I can't recall the links.

How many failures in journalism are attributed to "lazy journalism" where nobody will even leave the building these days to even ask someone involved in the story or topic. How the internet made it "easier" but they've become so over-reliant on it that many journalists fail to include information that isn't already online.

Then again, Netflix is probably a phone call away, so that may be a whole 'nother level of lack-of-followup.

OpenCL is slower than CUDA, but it's not the end of the world.

There are plenty of Apple failures.

https://www.macworld.co.uk/feature/apple/11-worst-apple-prod...

The truth is, in hindsight, you can make history and success/failure stories look like the result of anything you want if you think abstractly enough.

> That requires much higher throughput, which causes much of the added latency on the display end.

That's not all the reason. More pixels pushed would only increase latency if the CPU/memory/etc wasn't faster than the older computers.

John Carmack said years ago, "I can send a packet across the world in less time than it takes to put a pixel on the screen."

That was an incredible read. I had no idea about it. Hilariously dangerous.

Well, people smart enough to be the kind of contestant they want, are still fulfilling what the producers want.

Congrats on the work though!