Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Twirrim
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
33 ms
·
451.
▲
by
Twirrim
2y ago
For what it's worth, I ported the sum example to pure python. def sum(depth, x): if depth == 0: return x else: fst = sum(depth-1, x*2+0) # adds the fst half snd = sum(depth-1, x*2+1)
452.
▲
by
Twirrim
2y ago
Weird. I don't think I've ever relied on pickle for sharing data. It's too version specific. I always dump to json, or similar.
453.
▲
by
Twirrim
2y ago
Email address specs turn out to be rather complicated. I really wish people wouldn't code their own checks rather than use already existing standards. Some languages like Java even include proper checks in their standard library: htt
454.
▲
by
Twirrim
2y ago
It's not because it's a threat, it was to make it easier to catch the zebra, which has been getting spooked by all these extra people hoping to see it. There's been all sorts of folks out there causing it to panic and run awa
455.
▲
by
Twirrim
2y ago
All meeting some random arbitrary, maybe not even conscious, decision made by an early S3 engineer when they were implementing something.
456.
▲
by
Twirrim
2y ago
Historically, they've been scared of versioning their APIs (not many services have done it, dynamodb has, for example). It leads to a "bad customer experience", having to update lots of code, and also increases maintenance co
457.
▲
by
Twirrim
2y ago
sqlite uses something like this approach too, and there are additional optimisation advantages from keeping everything in a single file: https://sqlite.org/amalgamation.html Over 100 separate source files are concaten
458.
▲
by
Twirrim
3y ago
I think you missed some of the context/point behind the reference. The bug was reported when it first came up in 23.10, a non-LTS release. The previous non-LTS release is a final proving ground for an LTS release. They had an opportu
459.
▲
by
Twirrim
3y ago
Okay, unless I'm missing something, Kelly Criterion puts it at 0%, which is about what I'd expect. p = 0.5 q = 0.5 b = 1.0 0.5 - (0.5 / 1.0) = 0.0
460.
▲
by
Twirrim
3y ago
True. I tend to shove stuff in to cgroups and adjust niceness to compensate, so e.g. slack and email client are both lower priority and cpu restricted.
461.
▲
by
Twirrim
3y ago
Oh boy, further down the rabbit hole!
462.
▲
by
Twirrim
3y ago
A quick and dirty, shallow one, that I just opted to brute force out of curiosity. An online game I play includes an optional two player Russian Roulette type feature (non-fatal). I got to wondering if there was an optimal betting percenta
463.
▲
by
Twirrim
3y ago
It may do, but the CFS scheduler is really good for generic purposes, and the new replacement for it, EEVDF, that became default in a recent kernel, does even better. What I think is more interesting in this project is it's one of the
464.
▲
by
Twirrim
3y ago
Wow, Cyrix. There's a name I haven't heard in a long time.
465.
▲
by
Twirrim
3y ago
Oracle cloud also ships Ampere based servers. It's probably a larger cloud than you realise
466.
▲
by
Twirrim
3y ago
I'm not sure how much I can safely say, given I was employed by AWS, and provided some element of support to the snowball team from time to time, but Snowmobile was originally targeted towards one or two particular customers that had p
467.
▲
by
Twirrim
3y ago
This is the boot camp school formerly known as Lambda School, that came under a lot of fire in the past for these types of practices, and other issues. Previous trouble they've been in: https://dfpi.ca.gov/2021/04&
468.
▲
by
Twirrim
3y ago
There doesn't seem to be a thread, just that one tweet. There's reasons that the companies they're coming from have built JIT for Javascript, so I assume the angle here is just to avoid unnecessary complexity until it become
469.
▲
by
Twirrim
3y ago
Yes, you're right, you're absolutely the smartest person in the industry, and absolutely everyone else doing all of this work has no clue what they are doing at all, and should absolutely bow down to your superior intellect. You n
470.
▲
by
Twirrim
3y ago
I was reflecting on xz being an absolute triumph of open source software: 1) Someone noticed something that was odd. They were able to go look at what was happening, along with source code and see that suspicious things had happened. 2) Th
471.
▲
by
Twirrim
3y ago
> What really got my goat about this article is that prior to the latest tested version of Gnome, the repaint rate was a fixed 40Hz! Whose decision was that? From a previous VTE weekly status message, leading up to the removal: "I s
472.
▲
by
Twirrim
3y ago
Yes. From what I was told, it was already of reasonable vintage when I joined in 2013.
473.
▲
by
Twirrim
3y ago
Unsurprisingly enough, complicated technology requires complicated manufacturing capabilities and finite time to create, QA etc. These radar systems are many orders of magnitude more complicated than anything manufactured during WW2. It&#x
474.
▲
by
Twirrim
3y ago
Surely it needs more than just emulating the teacher, though, it would require exploring beyond those limitations?
475.
▲
by
Twirrim
3y ago
>It's pretty nifty. It's how Amazon's stuff used to work (though not using Stow) back several years ago. No idea if they've migrated from that approach to containers, or similar, yet. Every application you deployed w
476.
▲
by
Twirrim
3y ago
On the surface of it, it looks like literally no one wins. Redis Labs are going to lose a large amount of labour they've been getting for free. This seems like biting the hand that feeds it. Users lose out on the fruits of that labou
477.
▲
by
Twirrim
3y ago
We're within weeks of cut-off for Ubuntu's next LTS, Red Hat 10, etc. Fail to deliver their code upstream in the next few weeks and they'd be out of luck for getting it in to an enterprise distribution for the next 3-4ish ye
478.
▲
by
Twirrim
3y ago
People love to keep trotting it out, which is annoying. "Can't use MySQL because <thing-that-hasn't-been-true-for-over-a-decade>", which I guess is arguably adjacent to other points in the article about the stuff
479.
▲
by
Twirrim
3y ago
I don't think it was specific effort to exclude others, they took efforts to ensure it happened at packaging time, to reduce chances of detection. So eg other xz devs didn't notice it when compiling it, and so on.
480.
▲
by
Twirrim
3y ago
> A bit random, but has there been speculation on why this seemed to only target rpm/deb packaging? I don't think much speculation is needed. RPM and deb catches every Enterprise Linux distribution, to the best of my knowledge
More ›