Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
aseipp
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
24 ms
·
241.
▲
by
aseipp
2y ago
You can do that with Sapling, in fact it's both very easy and conceptually more robust than Git because with Sapling you are just manipulating commits. Sapling also includes `sl web` which makes interactive commits, splitting, and reba
242.
▲
by
aseipp
2y ago
To be fair, the website has changed very little since OSS launch (when this blog post first came out) and almost all of the main points of the blog are still the same, and the selling points are the same, too. So, I think it's fine,
243.
▲
by
aseipp
2y ago
The server-side IS open source -- it's basically been in the source tree since day 1, but "inert" due to facebook-only dependencies that made the code unusable, but most of the stuff was actually there if you were willing to
244.
▲
by
aseipp
2y ago
> Sapling's problem is pretty obvious: I would have to get others to use FBs merge stack tool and get that past security approval. You don't have to use Sapling's integration at all, FWIW. I completely avoided PR functiona
245.
▲
by
aseipp
2y ago
Payroll. It turns out that when you actually pay money to people for their work, it is expensive. That is because the value provided by the labor of humans is, in fact, valuable. However, if you instead just exploit people and take advant
246.
▲
by
aseipp
2y ago
> It could have helped Narrator: It could not have helped, it would have mostly just made them even more burnt out, because they (as they said in the post) were already on call effectively 7 days a week and have been since the site start
247.
▲
by
aseipp
2y ago
> If you think about it, the /etc tree is just a hierarchical key-value store Well, you're in luck, I have good news for you -- Windows also has its own version of this concept: it's called "The Registry". You mi
248.
▲
by
aseipp
2y ago
Multiple other distributed version control systems in the 2000s had support for easy hosting. Darcs was actually the best in this era, IMO, because it was far simpler than both Hg and Git -- a Darcs repository was just a directory, and it s
249.
▲
by
aseipp
2y ago
> An SSH key is effectively a really long password with cryptographic properties "An SSH key is basically a really long password, but also at the same time it's not a really long password, and you interact with it entirely diff
250.
▲
by
aseipp
2y ago
Yeah. I think they just don't like you. I log in probably once every 3 months or something, on every device. Nowhere close to every day. Can I ask what country you're from? Maybe that has something to do with it?
251.
▲
by
aseipp
2y ago
Yes, thanks! Obvious "accounting fingers" typo.
252.
▲
by
aseipp
2y ago
No, I was in fact thinking of 103 early hints, which are relatively new.
253.
▲
by
aseipp
2y ago
With a mailing list you download a patch and apply it with "git am", then push it to the repository -- as you are presumably the maintainer who has permission to do that, and assuming the patch is good. You basically just do code
254.
▲
by
aseipp
2y ago
To me, ordinary login is one of the things they've genuinely improved over time I feel? I absolutely never deal with logins more than once a day per machine? With stuff like Passkey support now, I basically click two buttons in 1Pass a
255.
▲
by
aseipp
2y ago
There are some alternatives like https://grep.app or https://sourcegraph.com/search if you want fast live search, but at the end of the day these are services offered by companies, and rather expensive ones espe
256.
▲
by
aseipp
2y ago
Coq doesn't seem meaningfully harder to build than in the past but maybe I'm just not in touch. It was always the Gtk bits that added issues for me, not Dune or anything. > which despite all the hate for them are always the mos
257.
▲
by
aseipp
2y ago
Honestly using Rust recently has taught me that, the only reason C and C++ dependencies in Rust are remotely tolerable (unlike most other languages) is because Rust has an unusually high degree of talented developers, many former C/C
258.
▲
by
aseipp
2y ago
Preload headers DO NOT function "effectively the same" the same as HTTP/2 Push. Yes they have similar outcomes, no that does mean they function the same. They are related, but are not actually that similar except in the most
259.
▲
by
aseipp
2y ago
Yeah, I don't think either of these are really big problems. People identify the vuln, the fix, and they tend to share the patches for backports across versions + across distros, and/or immediately update downstream users to fixed
260.
▲
by
aseipp
2y ago
The design of any library for a microcontroller and an "equivalent" for general end user application is going to be different in pretty much every major design point. I'm not sure how this is any more relevant to fmt than it
261.
▲
by
aseipp
2y ago
Not all distributions suffer from this, because they have the tooling to patch all crate versions given a name. Compile times are actually the worst part but can be mitigated. But these distros also fundamentally accept the language's
262.
▲
by
aseipp
2y ago
You can call any decision you want crazy, but it's not relevant in a matter of trademark, and they talked about this at the time of the original license change. The word "Elastic" isn't enough on its own. In contrast Ama
263.
▲
by
aseipp
2y ago
> What you really want is for the arch to be able to disallow 4KB pages like on apple silicon which is the main piece that allows their giant 128LB and 192KB L1 caches. Minor nit but they allow 4k pages. Linux doesn't support 16k an
264.
▲
by
aseipp
2y ago
The vector width stuff is overblown. There are in practice 3 widths for all desktop architectures (128-bit, 256-bit, 512-bit) and the 95th percentile of all desktops are squarely in the first two buckets, or alternatively you're target
265.
▲
by
aseipp
2y ago
No, the FSF specifically requires ownership transfer for GNU projects, so that they can do things like go after infringements in court, or relicense GNU projects to newer versions of the GPL unconditionally, e.g. when GPLv3 was released. Ir
266.
▲
by
aseipp
2y ago
The website is also slow if the browser requests a resource from an origin that is very far away. Nothing is free. The typical benefit for large-scale CDNs is TTFB latency reduction, which tends to be felt rather acutely by users; and the c
267.
▲
by
aseipp
2y ago
MPX is dead, but memory protection keys are a distinct feature and work fine (with some limitations); I haven't seen anything about them being removed at all and Intel doesn't note them in their deprecated features list. AMD even
268.
▲
by
aseipp
2y ago
What exactly do you think CDNs do?
269.
▲
by
aseipp
2y ago
By that point the player base can already be devastated, and it can kill the game. Cycle: Frontiers was an extraction shooter, and the immediate cheating was rampant; the game's design meant dying to hackers was devastating -- imagine
270.
▲
by
aseipp
2y ago
> The only thing sad here is that all this work to enable full-width AVX512 is going to be mostly wasted as approximately 0% of all client software will get recompiled to an AVX512 baseline for decades if ever. Well, the other thing is t
More ›