Seems like it would be much easier to solve that problem than it would be to cross the brain barrier and start interfacing with our thoughts, no? Just provide some context on the company etc

“Sounds like it would” yes, but on practice no off the self solution works remotely well enough.

> Just provide some context on the company etc

The necessary “context” includes at least the name and pronunciation of the names of all workers of a company with a non English first name, so it's far from trivial.

> off the self

Was that deliberate, or a typo? I am genuinely wondering!

It's a typo.

This is a huge fumble, but it will be inevitably swept under the hype train and forgotten about.

They will be embedded in the existing interfaces for voice, Siri, Alexa etc.

How is this possible? Can someone point me in the direction of what mechanism is used here.

If I open a pdf in chrome for example am I opening myself up to this kind of attack?

I would say first thing is to disable Windows Explorer from hiding the extension of files.

From what I understand, it was an executable inside a zip attachment to an email disguising itself as a partnership proposal from a reputable source.

The file inside the zip probably had a .pdf.exe extension. By default, Windows Explorer would show it as a .pdf, making it easy to run by mistake.

Wait it wasn't an executable pdf that escaped the sandbox, it was a *.pdf.exe?? Why does Windows even still have this vulnerability?

That should be stopped by the smartscreen prompt which is pretty hard to bypass by accident.

PDF can run JavaScript

Not necessarily, the component itself can work without a key. Adding a key is just one approach to resetting component state from a parent. If a component can’t work properly without a key it should be wrapped further to make it usable rather than documenting it for all consumers.

That last bit seems like a recommendation that should be in the docs. It’s sensible from a “don’t leave boobytraps” perspective but it won’t be intuitive to many people. It’s one more little rule to learn, another comment on a sizable chunk of PRs. While it may be idiomatic and sensible JSX, it seems like an outlier for React, and I wonder if there’s an opportunity to improve the developer experience of this very common use case.

I find it hard to believe that almost half of remote workers are watching porn on company devices.

I’d also like to see a comparison of “wasted hours” when in the office as well. This kind of stuff went on long before remote work got popular.

Almost half of those that use ExpressVPN i.e. not many.

Someone please correct me if I'm wrong, but as far as I understood they could only see the chat title and not the whole chat history.

This is all just fluff (especially the emojis), the usefulness of a commit message is the why. I'm yet to see AI accomplish that. Until then I'll continue writing my own commit messages.

Yep it can be a useful pattern, but it must be in a conditional to stop an infinite loop.

This useful guide points it out as well: https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-...

This page should be mandatory reading for any dev working in react. The biggest mistake I see with devs of all levels is over use of effects.

This seems to be especially bad for anyone who originally worked with class components. The mental modal shift was large and people tried to fit their understanding of lifecycle methods into hooks, attempting to replicate similar behaviour. The docs at the time did a poor job of explaining why this was a bad idea.

100%. Effects are an escape-hatch, and it's really common for people not to treat them that way. All of the new docs are gold, but if I could only pick one to recommend that every React developer read, it would be this one

Second is abuse of useState for calculated values