rudian
Joined 5 years ago
Joined 5 years ago
querySelector *does not* take 62ms to run. Both of them take 0.01ms at most, try it yourself. This is the sort of micro optimization you should not concern yourself with.
How often do you need to select unique elements by ID? Don't use IDs in the first place.
This is akin to using `i--` in loops to "speed up your code" — we're past that.
Doubt. Your "[email protected]" in Deno is no different than "something": "^1.2.3" in npm. The problems will appear when you update stuff.
The only thing benefiting deno currently is the clean slate and the lack of hacks (for now).
Either way, 100% agree. Stop trying to change a OS’s text rendering, if you still are.
What people see is that they get free money from the government and maybe they’re lucky to see it go up. They don’t know it could be half tomorrow.
- too many street names make for a noisy/busy/ugly map, and we all know maps must be beautiful and nothing else
- streets don’t pay for ads, businesses do, so between the two they prefer showing the latter.
Technically now you can tap anywhere on the map once to place a pin and get more info; In practice tapping in Google Maps has become horrendous, it never does what you expect. One such example is tapping on a business near a “walkable area”: you can’t. The area will always focus instead, even if painted behind the business.
But then again that doesn’t mean the id should be used for selection (in JS nor CSS) as it’s probably easier to target many elements with a class, should they ever co-exist. This is basically what you end up with if you build components anyway (even without specific frameworks)