Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ninkendo
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
73 ms
·
961.
▲
by
ninkendo
3y ago
If only we had that kind of sanity in the US… the electric hummer is an absolute monstrosity and should never have been made IMO. I am a supporter of EV’s but, I am increasingly skeptical that legacy US automakers will ever “get it” when it
962.
▲
by
ninkendo
3y ago
I mean, if we’re picking models to support our points, I’d counter with the Hummer EV which is 9,630 lbs. Road wear goes up with the 4th power of weight, so doubling the weight increases road wear 16x… it’s not something we should just igno
963.
▲
by
ninkendo
3y ago
It is in the mind of consumers, yes (I have not offered my personal opinion and don’t want to, as it’s irrelevant to the point.) There has been a lot of consumer studies on this and range anxiety is a very real thing.
964.
▲
by
ninkendo
3y ago
> The weight efficiency can only improve from here I don’t think this is a given. I can imagine plenty of future battery tech that is much more physically dense, and also more energy-dense, but with an overall mass that’s heavier than wh
965.
▲
by
ninkendo
3y ago
Begone troll. (Edit: because I noticed this too, and it got me curious, the reason for the incorrect result is that I didn't check the result of the read() call, and it was actually reading fewer bytes, by a small handful. read() is al
966.
▲
by
ninkendo
3y ago
You're basically just gish galloping at this point and there's no need to respond to you any more. All your points about swap are irrelevant to the discussion. All your points about disk cache are irrelevant to the discussion. You
967.
▲
by
ninkendo
3y ago
Please keep in mind the context of the discussion. A prior poster made a claim that they can read a file into memory, and that it won’t actually use any additional memory because the kernel will “automatically take care” of it somehow. This
968.
▲
by
ninkendo
3y ago
NAT64 is just stateful NAT, exactly the same as IPv4 stateful NAT. It happens to be translating between v4 and v6 as part of the translation, but it’s no different whatsoever from pure-IPv4 NAT in this regard. You can call it “tunneling” if
969.
▲
by
ninkendo
3y ago
Fair enough, it’s totally possible that’s what they meant. But the complaint of “every package assumes you loaded the whole dataset in memory” seems to imply the package just naively reads the file in. I mean, if the package was mmapping
970.
▲
by
ninkendo
3y ago
That’s a really misleading thing to say. If the kernel already has the thing you’re read()’ing cached , then yes the kernel can skip the disk read as an optimization . But by reading, you’re taking those bytes and putting a copy of them
971.
▲
by
ninkendo
3y ago
> On an average desktop/server system the OS would automatically take care of putting whatever fits in RAM and the rest on disk. This is not true, unless you’re referring to swap (which is a configuration of the system and may not b
972.
▲
by
ninkendo
3y ago
> The largest problem with this is that that this IPv6 router lives outside of your devices. It lives somewhere at the ISPs infrastructure. I use my own router which supports NAT64. I use OpenBSD which supports it natively in-kernel, but
973.
▲
by
ninkendo
3y ago
Coming from the Apple ecosystem, this is solved on macOS/iOS by a native implementation of 464XLAT on the device (particularly the CLAT relay part.) If you have a working NAT64/DNS64 setup, macOS can make a AAAA (ipv6 DNS) request
974.
▲
by
ninkendo
3y ago
> Unicode the complete, total and utter clusterfuck that it is. Yikes, does it really deserve that much derision? They’re trying to standardize all written human language here. I think they’ve done a fantastic job. Pre-Unicode you had
975.
▲
by
ninkendo
3y ago
We can assume that modeless was referring to the dust generated by the brake pads themselves, I should think…
976.
▲
by
ninkendo
3y ago
They didn’t suggest therapy because of the point about not wanting kids. They suggested therapy because of the point about life being nothing but challenge and hardship , misery, etc. I think it’s not controversial to point out that therap
977.
▲
by
ninkendo
3y ago
I’m talking about replies to other people’s comments. If someone asks you a question in a review, it seems crazy to me that you should submit your own review of your own code, complete with an approval (huh?) just to answer it. If you’re sa
978.
▲
by
ninkendo
3y ago
> either by silencing obviously false positives (Off-topic) Oh how I wish this were possible in the language I use at $dayjob. Swift does not let you silence warnings on a line by line basis. It’s easily one of the top 5 worst things abo
979.
▲
by
ninkendo
3y ago
GitHub seems to have no interest whatsoever in making the process of reviewing code any better or easier. It’s still essentially the same as it was 15 years ago. They introduced batched review comments well over five years ago, and still ha
980.
▲
by
ninkendo
3y ago
Right. To elaborate on my original point, because ObjC includes C, saying "ObjC has safe arrays because it crashes on OOB" is both true and irrelevant. It has safe arrays, but that's not all it has. It also has very, very
981.
▲
by
ninkendo
3y ago
A lot of people are asking you how it's possible you're getting deadlocks, so I'll reply to all of them here: It's definitely possible without doing anything wrong in your own code, if you're calling poorly written
982.
▲
by
ninkendo
3y ago
> Trying to access the 20th element from an array of 2 elements would cause a crash in almost all languages including Objective-C It depends on which part of objective C you’re referring to: the C part, or the objective part. ObjC has
983.
▲
by
ninkendo
3y ago
The dropbox article others and myself have linked provided such benchmarks, for an 11% speedup. Seem plausible?
984.
▲
by
ninkendo
3y ago
We know that the webp project does use unchecked access. We know this is intentional because they go through a lot of effort to do up front bounds checking rather than at every access. We also know that companies like Dropbox, when implem
985.
▲
by
ninkendo
3y ago
That’s not google’s webp library, that’s a totally different project. It doesn’t really matter what that project does.
986.
▲
by
ninkendo
3y ago
Elsewhere in the comments someone linked to this: https://dropbox.tech/infrastructure/lossless-compression-wit... It looks like dropbox experimented with disabling bounds checks in their huffman coding impl, and found
987.
▲
by
ninkendo
3y ago
> The extra ceremony ("unsafe { foo.get_unchecked(n) {" vs "foo[n]" makes this even simpler to catch in code review Right, and in said code review, the webp author could have easily said “yup, we want unsafe here beca
988.
▲
by
ninkendo
3y ago
A memory-safe language could have easily resulted in the same vulnerability. In this context, “memory-safe” means it does bounds checking on an array when you try to access an element. But the webp code does bounds checks up-front so that a
989.
▲
by
ninkendo
3y ago
Interesting! My info is way out of date then. Thanks for the link.
990.
▲
by
ninkendo
3y ago
> With IPv6 privacy extensions, your address changes regularly. This seems like an improvement. Eh… If I was a company that wanted to use IP addresses to fingerprint users, IPv4 vs IPv6+privacy extensions both seem identical to me. Multi
More ›