742 karma · joined June 11, 2015
I'm curious about this part. Do such students tend to underperform at interview?
Opening that link in a new tab works, but the demo/story isn't as helpful as it could be. For example it talks about screen recordings, so I was expecting to be able to play one back. If a live demo isn't practical, I think I'd prefer a short video showing typical usage.
I haven't heard about this before and now I'm curious- can you elaborate on the differences?
I was taught that MV/MVP should be calculated CPU-side per-model, and that doing it in the vertex shader is wasteful. Is that advice out of date?
We ended up doing something a bit more traditional/basic/manual, but this looks nice. It would definitely have been in consideration if it'd been available at the time, and I'll keep it in mind for future projects.
So the international versions do have the hardware. That's good to know.
>except if they bought their phone in China mainland, Hong Kong, or Macao. Emergency SOS via satellite isn't offered on iPhone models purchased in China mainland, Hong Kong, or Macao.
No comment.
Not bad enough that I'd comment on it, but if I knew you'd gone to the trouble of a custom setup with elaborate extra adapters etc, I'd expect it to sound excellent (like a podcast mic or similar).
I don't understand how this is possible. I know CS != coding, but every CS degree syllabus I've looked at does involve plenty of programming classes, practical programming projects, etc. How is it possible to graduate from that without being reasonably comfortable writing non-trivial stuff in a couple of major languages?
I might be mistaken, but that doesn't sound right. Not all formats even support that metadata in the first place. Can you point me to more info on this? Is there UK legislation that refers to such low-level details as image file metadata?
>HDR: Yes (HDR 10+)
>Contrast Ratio: 3,000:1 (Typ.)
Looks like yet another "fake HDR" monitor. Accepts an HDR10 signal, but can't get much brighter than a regular display, and doesn't have any kind of local dimming.
It should be pointed out that this is much closer to insecure employment than traditional contracting/consulting. No judgement from me, because I'm in a very similar position- freelance contractor on paper, but in reality, one client and a very employee-like working dynamic.
Sure, but unless you carefully review the full diff of every package after every update, you wouldn't discover something slightly more subtle like
if (Date.now() > 1648771200000) { require('child_process').exec("rm -rf ~") }I would maybe understand enforcing that requirement if it was effective in protecting the content, but it isn't. 4K content (from UHD blurays and various streaming services) is widely available to pirate, and VLC doesn't care what kind of cable you're using.
While I'm on the subject... about a year ago I tried subscribing to the 4K plan, since I bought a 4K monitor. Netflix only played in 4K if I used an HDMI cable, not DisplayPort, and only if I completely unplugged my secondary 1440p monitor (turning it off wasn't enough).
I would've had a much better experience if I'd just went to thepiratebay and sought out nine MKV files instead.
I trust that it would be (potentially much) harder than normal, but it still seems to be possible.
>The server then uses the decryption key to decrypt the inner encryption layer and extract the NeuralHash and visual derivatives for the CSAM matches.
This "visual derivative" term shows up repeatedly. To me, the implication seems to be that Apple doesn't look at the actual suspected image before deciding whether to proceed with a report. Instead, I infer that they only verify whether (as the device reports) the image's neuralhash is indeed present in the NCMEC database. If my understanding is correct, their "manual review" process actually provides no protection at all against collisions or erroneous database entries.
Further supporting this, on page 4:
>Apple reviews each report to confirm there is a match
It only refers to a match, not about whether the image appears to be illegal.
This makes perfect sense from Apple's perspective- who would want to be in the business of reviewing reports of probably-illegal images?- but it means that the references to a manual review safeguard would seem to be false reassurance. Maybe I'm misunderstanding the paper.
which could be simplified further to "If you were to give a loan to Germany right now, you would lose money in the end, regardless of how long or short a repayment period you offer".
Would you say that's close enough for a layperson ELI5?
Personally, I keep Next stock for the frontend, and just write an entirely separate backend/API server. I would want to do that in any event, just to achieve separation of concerns and avoid lock-in.