Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kllrnohj
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
24 ms
·
481.
▲
by
kllrnohj
2y ago
that would require an algebraic solver which is definitely possible but more complex than really warranted for a "basic" calculator
482.
▲
by
kllrnohj
2y ago
hint, the problem is doing ipv6 vlans with only a single /64. Spoiler alert: you can't do it while also following spec
483.
▲
by
kllrnohj
2y ago
They didn't invent SLAAC, so no that wasn't a reinvention of IPv6. But even if they had the counter argument to "128 bit addresses are too long, 48 bit would have been better" is obviously not "that's the same
484.
▲
by
kllrnohj
2y ago
> IPv6 is ridiculously easy, in the grand scheme of things. How do I do a guest wifi network with isolation? On ipv4 I just flip a switch and thanks to NATs it just works, always. With ipv6? First I have to figure out what prefix delegat
485.
▲
by
kllrnohj
2y ago
> You can do it with DHCPv6, but of course there's Android. Android aside, it works fine. are you sure? what about homepods, Chromecasts, Hue bridges, kasa smart plugs, esphome, etc etc etc...? How much are you willing to bet your h
486.
▲
by
kllrnohj
2y ago
> Hardcoded DNS servers are just as equally a thing with IPv4. Of course, but they aren't the baseline expectation like it is with ipv6 since ipv6 baseline assumption is SLAAC. And SLAAC is terrible. If you control all the devices o
487.
▲
by
kllrnohj
2y ago
mDNS would work just fine but the given command ('ping foo') wouldn't be using mDNS. That's just standard name resolution. `ping foo.local` would potentially use mDNS if you have a ping that does such a thing, but that&#
488.
▲
by
kllrnohj
2y ago
It breaks SLAAC so routers won't do it. Or if they do, it's non-standard and they won't easily let you do it. /64 is the smallest PD by spec ( RFC 5375 )
489.
▲
by
kllrnohj
2y ago
that's not mDNS that's just dhcp+dns and it's something ipv6 actually breaks, which is part of the problem. DHCPv6 is optional, so local devices don't necessarily ever register their hostname nor do they necessarily ever
490.
▲
by
kllrnohj
2y ago
> I'm also convinced that the length of IPv6 addresses and the difficulty in typing them is a major reason for lack of adoption. Possibly, but I think it's also that some aspects of IPv6 are just badly designed, and subsequent
491.
▲
by
kllrnohj
2y ago
Rust in Linux has official blessing. 99% of the kernel being in C is irrelevant, it's not a C-only kernel anymore officially.
492.
▲
by
kllrnohj
2y ago
While words change and it rapidly escalated over the last 10 years, it's been about police brutality/misconduct for at least 50 years now. Using phrases whose meaning you're unaware of is generally risky behavior. Trying to c
493.
▲
by
kllrnohj
2y ago
Putting in the work is one thing, which is what the Rust-in-Linux people are also doing, but there's also the political requirement to force maintainers to accept it. Android was big enough, and happy enough to fork seeing as it had al
494.
▲
by
kllrnohj
2y ago
What's objectionable is primarily the phrase "thin blue line" - it's highly politically charged language: https://en.wikipedia.org/wiki/Thin_blue_line One would hope it was just a particularly bad
495.
▲
by
kllrnohj
2y ago
You should click through some of the links to see where the clashes actually happened. It didn't have anything to do with the actual hardware support. Rather, it was over stupid shit like the kernel DMA team throwing a hissy fit over t
496.
▲
by
kllrnohj
2y ago
Android would still come with the kernel development caveats which is where Asahi is having the most trouble. Android's HALs help abstract the userspace portion of drivers, but if you need to be in kernel space you're still stuck
497.
▲
by
kllrnohj
2y ago
> which is actively hostile to a second Rust compiler implementation Which is hilarious since Linux itself was actively hostile to the idea of a second C compiler supporting it. Just getting Linux to support Clang instead of only GCC was
498.
▲
by
kllrnohj
2y ago
derbauer did an analysis of the melted connector. It was nickel & gold, not steel. buildzodes analysis showed Nvidia removed all ability to load balance the wires which they used to have with the 30xx connector that introduced it, and t
499.
▲
by
kllrnohj
2y ago
We're not talking about platforms, we're talking about languages.
500.
▲
by
kllrnohj
2y ago
Being a PCI spec connector doesn't mean it isn't an Nvidia thing. It seems pretty likely at this point that Nvidia forced this through, seeing as there's zero other users of this connector. Convincing PCI spec consortium to r
501.
▲
by
kllrnohj
2y ago
That list would be like saying "Java on Android". A single platform's narrow usage of a language != language's standard library having it.
502.
▲
by
kllrnohj
2y ago
> If C++ really wants to help "game-engines" or make actual strides, then it should add basic GUI support to the language itself. That'd kill off 90% of the other framework/libraries out there. Find me a single langua
503.
▲
by
kllrnohj
2y ago
> Waydroid reimplements Android libraries and higher level APIs to convert them to something compatible with your host kernel, This is simply incorrect, though, negating the entirety of the rest of your argument. > No, the main differ
504.
▲
by
kllrnohj
2y ago
> This is like suggesting that running applications in a Windows VM and running them under WINE isn't a big difference. False equivalence. WINE reimplements windows libraries and higher level APIs to convert to Linux-native ASAP. Wa
505.
▲
by
kllrnohj
2y ago
The emulator is just KVM. Yes VMs vs. container is a difference, just like it is in endless cloud discussions, but it's not particularly big in any objective metrics
506.
▲
by
kllrnohj
2y ago
The emulator these days is just using an x86_64 image and with not-that-modern VM hardware extensions the overhead is pretty small. So I'd expect CPU performance to be very similar if not basically identical. GPU performance would be t
507.
▲
by
kllrnohj
2y ago
Musk is a glaringly obvious example. But also basically the entire GOP fits, as well (they all screamed free speech in response to fact checkers only to do this "anti-woke" silencing)
508.
▲
by
kllrnohj
2y ago
> My least charitable view (and immediate reaction) is that they're purposely ruining a viable budget phone to make more sales. Given the legal & regulatory trouble Apple got in and is currently in depending on jurisdiction for
509.
▲
by
kllrnohj
2y ago
> I’m deep into the Apple ecosystem system and they don’t force updates My iPad is pretty naggy to install updates, moreso than my Pixel phone even. iOS doesn't automatically update like Android does, but if anything that seems less
510.
▲
by
kllrnohj
2y ago
I've had "stable" distributions fall over upgrading between their major versions. But you missed the point that Android's system image is immutable and updates are atomic. A user can't screw it up. This is not an in
More ›