725 karma · joined June 26, 2021
If I want to block users of my network from accessing website X, why would I not block it at the IP level (level 3) by blocking all packets to all IP address that other DNS providers associate with website X?
That said, I think more and more people are realizing this so I'm hopeful things would improve. For example, one of the most underrated streaming services IMO is HBO Max - they don't have a lot of content but the quality of of what they have is pretty good.
This is highly anecdotal. Apple got to where they are with M1 by vertically interesting which wouldn't be possible if they broke up like you said.
Rather, in a pipeline the bottleneck determines throughout - Intel's bottleneck is manufacturing and that's what they need to fix or cut out. We have no reason to believe their design with TSMC chips won't best AMD it even apple.
A lot of people (do not trust password managers, case in point the recent last pass scare.
You want passwords to your key accounts to be 1) memorable 2) strong 3) only in your head. For these, I think the article is fairly relevant.
They travel towards a far away point from the player but near treasure areas, because of their high navmesh density, all path lead in one direction.
+1. I expect stuff like this from regular social media like reddit but I'm appalled that this is so common here on HN too.
1. You spend too much time optimizing your to-do list. 2. You realize you are spending too much time optimizing your to-do list and you give up in frustration because you feel like you don't get your actual work done.
With a text file, it's a free for all, you don't feel obligated to keep it clean, when you have to make a note you just "do it".
... <file1, bytes 2048-4096> <file2, bytes 0-125> ...
The server has to order critical stuff first on a pipelined connection to reduce latency but this approach can easily send stuff the client requested and will request, while collecting data serverside by any number of threads.
Can you explain what's the difference in gamma correction and color correction? New gamma correction uses perceptual mapping right (e.g. Dolby vision) - doesn't that already put you into a standard color space?
> then, display it on the screen, continuously, within 50ms per frame
That's 20 fps. Don't you need at least 24 to capture cinematic footage?
Interestingly, if any montior you connect is not HDCP 2.2 you don't get 4K.
GeForce Stuff like Nvidia instant replay gets disabled if you have Netflix up in a tab - so close those before you game.
When the logic gets super complex, I would think that a good comprise is to modularize your code - and test the public API of each module. A good heuristic is to see if that modules are (or could be) helpful by themselves in the future.
You then write tests for a module assuming it's dependents cover their edge cases.
Nope, they don't. They just need to keep a list of free indices when the cache is not full. Upon eviction you reuse the deleted element's index.
This way, you store about O(capacity)*32bits for index in the worst case and save 32bits on left, right and the map pointers so your worst case space complexity is down by O(capacity).
I still expect that the saving from cache friendliness with preallocation will be the most significant.
Very thoughtful optimization. I'm usually guilty of just caring about Big O, usually just the time complexity.
This is an excellent point but are there any devs who don't do this? This seems like such an obvious thing to do. I mean I guess if you dealing with tech debt and you want to upgrade from ASCII/bytes to UTF-8 you will not have this invariant for a shirt while but why would you not maintain the invariant in new code?
This is new stuff to learn but once you do you realize it's super helpful.
Not a good idea. You are pretty much asking to be review bomb. You would need very good moderation to be able to trust votes. That means npm spending a bunch of resources on hiring them, not sure if they are up for that (no, free mods aren't the solution).