aseipp

72 ms·

751.
by aseipp 5y ago
People have said this about every social media app that became major for the past 10 years dude, Snapchat, Insta, TikTok, etc. If anything the batting average for social media companies that "make it" in the public's mind ove
752.
by aseipp 5y ago
It's not a matter of absolute numbers, but a question of die area, to some degree. You can either spend X amount of area on a "big core" that can clock all the way down to idle (where it will spend most time) and all the way
753.
by aseipp 5y ago
That's their point, it's literally self selection: people who do not care about the notch are not going to write comments about it, and people who care are never going to shut up about it, giving an extremely poor window for under
754.
by aseipp 5y ago
Today, with WebAuthn, recovery works the exact same way. Which is normally by emailing the user a magical link to a (trusted) address that does some recovery flow. There's nothing different about this, and how much of a weak link it is
755.
by aseipp 5y ago
In the abstract, it's sort of like asking "How can there still be traffic jams on road XYZ, when there's an open lane that was added recently?" The problem isn't the number of lanes, it's that fundamentally tha
756.
by aseipp 5y ago
I just think this isn't true. The reality of the situation is almost nobody actually wants to maintain anything unless they are paid to do so; people just want to throw you patches and have you accept them and then never contribute a
757.
by aseipp 5y ago
A big part of it is that GitHub Issues has essentially been the same product for the past like, 10 years, and even 10 years ago it was still seriously behind contemporary alternatives in a number of ways. The only reason people tolerate it
758.
by aseipp 5y ago
Because most of these systems in the real world are simply designed, by experience, to not use cross-shard transactions, so 2PC isn't relevant. There's nothing to "mention." It's a cultural choice as much as a techn
759.
by aseipp 5y ago
The modern Windows ARM laptops all(?) use standard x86 Secure Boot/UEFI rules, as far as I know. You can install Linux on them pretty easily; I know at least Fedora/Anaconda supports ARM64 pretty well. The bigger problems come aft
760.
by aseipp 5y ago
The labor and physical footprint needed to produce modern electronics is completely insane . You're comparing little league basketball to major league baseball, and it's not like a player like Framework is going to change this at
761.
by aseipp 5y ago
Well to a first approximation I would say phishing is about 1000x more widespread and dangerous to the average user than SMS-based attacks, so the impact is pretty immediate and significantly larger. I haven't seen any indication of SM
762.
by aseipp 5y ago
In a nutshell, you've got the idea. And no: the signed tokens are for all intents and purposes random blobs (often generated literally from /dev/urandom by the server), and the browser strictly associates a WebAuthn keypair t
763.
by aseipp 5y ago
No, there's no standard for any of those things. "Lost" or "Damaged" devices at least are indistinguishable from the service POV: you simply cannot authenticate and need to reset your auth method. "Compromised&
764.
by aseipp 5y ago
That's how it's worked forever, basically; Windows 10 was the minimum requirement for DX12 and Vista with DX11 before that, with 6-7 year time gaps. The APIs also evolved slowly and incrementally with features between those years,
765.
by aseipp 5y ago
Is there any summary of what's changed between K versions, or their lineage, for someone who's not "K-fluent" but a tiny bit familiar with array languages? What changed between K6, 7, and 9? Since Kx is the proprietor of
766.
by aseipp 5y ago
I mean, if you're just curious if literally anyone will do it, sure. Because you can (due to selection bias of Hacker News) find plenty of people here willing to say so. My prediction is twofold. First, that there's very, very lit
767.
by aseipp 5y ago
Many PC UEFI builds from mega manufacturers are heavily customized, but a lot of them are also just based on TianoCore, including the modern RPi UEFI firmware builds. Nothing very strange about it. More specifically, the distinguishing thin
768.
by aseipp 5y ago
Actual IP law and how it conducts itself in the real world has plenty of issues to be sorted out, but there are tons of potential "inefficiencies" in the real world that could be exploited and rectified across a vast array of thin
769.
by aseipp 5y ago
Ossification isn't really a problem for Homa's intended use case IMO; it's meant to be used on intra-DC networks with latencies already as low as 1us-2us, and is optimized exclusively for this design space (lots of short mess
770.
by aseipp 5y ago
Modern allocators divide allocations into "size classes" based on the size of the allocation (normally rounded up to some power of 2 or whatever.) When you call something like free(m), the allocator will often have to figure out w
771.
by aseipp 5y ago
As usual the problem is MITM. Any clone for git://github.com/foo/bar.git can easily be intercepted to git://github.com/evil-foo/evil-baz.git, or fetch, etc. The middleman can also do freeze attacks (i
772.
by aseipp 5y ago
That's a fair point but the reality is this -- if you work on large-ish or actually large codebase (think like, Open Office sized codebases, not your random run of the mill npm package) today and you want to maintain it, publish pack
773.
by aseipp 5y ago
I've been PlanetScale for a test drive recently, and it's a bit of both. I also think they kind of go hand-in-hand: if you have "serverless" things (or just Docker), they can come and go with connections very quickly, so
774.
by aseipp 5y ago
It's fine if most implementations of RPC are Level 1, even the main C++ bindings; due to the design of the protocol there only needs to exist a single Level 4 implementation written in any language, and all other implementations can th
775.
by aseipp 5y ago
What actually happens in that scenario is that one group now writes an adapter on top of SQLite to make it "standardized" to whatever interface you design, increasing the complexity and scope for bugs. To be clear: you're lit
776.
by aseipp 5y ago
I mean, I feel this particular example is really more of standard library design wart that occurs with any kind of syntactic overloading mechanism, e.g. Haskell has the exact same problem as C++ does here even though the overloading mechani
777.
by aseipp 5y ago
The author literally implemented fp16 support in his language. You clearly did not even read the post, which was just about the minor technical hurdles to doing so. Please learn to read next time instead of wasting everyone's time with
778.
by aseipp 5y ago
The entire blog post is literally an explanation of why implementing support for fp16 in Futhark was annoying. Let me repeat the key bit: support for fp16 in Futhark . As in, it exists, and you can use it. Right now! Nobody is stopping you
779.
by aseipp 5y ago
Because the turn-around time from upstream-to-packager is smaller, which in turn helps get problems fixed faster. That in turn means devs have more space to fix issues. It is an effective velocity improvement for them and they think it will
780.
by aseipp 5y ago
Safeguards do not just exist at the level of technology but also politics, social structures, policies, design decisions, human interactions, and so on and so forth. "Criticality" in particular is something defined by humans, not

More ›