dgacmu

It's probably not. I tried to extract the commit hash from the version of bun packaged in claude code. the commit hashes from previous versions resolve, whereas the commit hash for the current 1.4.0 isn't available.

from strings:

   bun-v1.4.0
   f6d0fcd24abd48061873c2f1a6fb2a67eee487b8
    Upgraded.
   Welcome to Bun's latest canary build!

(In contrast, earlier builds that I have locally have commit IDs that can be found in the public repo). I don't think it's particularly damning for them to vendor a canary release, mind you.

I used it for a bunch of remote monitor boxes to have a way of centrally managing ssh access to things that were often on- and off-line. It was simple and convenient and access was easily revocable.

Recently, there's a lot of talk about AI allegedly finding security flaws in software. That is an unsubstantiated claim. As such, it would need to be verified by a non-machine, and arguably, the verification process would require the same amount of effort or more than would be required to find the issue to begin with.

This is simply not true. Security flaws are a great use-case for AI specifically because they're easy to verify. If you can drive a program to segfault based on inputs, you've got a good indicator it is, in fact, a security vulnerability (at minimum a DoS, but usually you find out later it was exploitable). You could even have the AI generate an exploit PoC. Shell? Valid hole. Done.

The bad use cases for AI are the ones where it's as or more expensive to verify correctness as it would have been to find the solution in advance.

Intriguing. I should benchmark my dust-gathering-stack of Titan V's, unless someone already has?

It's definitely cribbing from other papers.

https://scholar.google.com/scholar?q=W.T.%20Tutte%2C%20Perso....

Sloppy scholarship. On the other hand, it's simply a credit attribution of posing the problem, so it's not material in evaluating the results. I observe that the majority of references I can find that attribute this to Tutte are very indirect - i.e., citing sources that themselves claim Tutte was one of the people who formulated it - so it would take someone with a little more time on their hands (or perhaps an LLM) to track down the original...

I had meta's crawler hitting the pi searcher at something like 5qps for days on end, just ... querying for substrings of pi, ignoring robots.txt, etc. it wasn't enough to break anything but it triggered a lot of alerts.

I can imagine that sites with dynamic content and potentially unbounded query types or pathnames are in danger from particularly stupid crawlers.

I'm not sure it's about overworking as much as stress - stress is a known potential trigger for manic episodes. Typically in people who already have some biological potential for experiencing it. And the stress of having your partner come down with dementia and suddenly becoming their full-time caregiver must be absolutely massive.

But re the underlying physical thing: You might look back and be able to spot some episodes of hypomania in your uncle's life. Perhaps just reduced sleep, or twinges of paranoia, or periods of on-again/off-again hyperproductivity, etc.

Hope that if this story is recent he's doing well. The recent generations of medications to prevent and treat mania are a huge improvement on the ones available in the past, so fingers crossed.

Russia's inability to have a decisive victory against Ukraine is at odds with the idea that it has sufficient stockpiles and launch capability to reduce kiev to rubble any time it wishes. If it had that capability, it would have the capability to destroy Ukraine's defense manufacturing sector - or simply its entire manufacturing sector - which it clearly does not. It's also at odds with the evidence that Russia is launching missles roughly as fast as they can build them.

I think you're over-estimating the capability of both sides of the fight (absent nuclear weapons on the part of Russia). Both sides appear to be using drones and missiles as fast as they can manufacture them. One could argue Russia could be more selectively targeting industrial infrastructure - I don't know if their attacks on residential areas are an inability to target well or some kind of hope that demoralization will be effective - but Ukraine is, I believe, doing as much as they can to Russia's oil & defense sectors as they are able.

example: "CAR’s analysis, based on physical examinations of marks on the remnants, shows that the missile that struck Okhmatdyt hospital was produced at most three months before the attack. Or perhaps even eight days before. " [1]

Sanctions and limited parts availability are limiting Russia's ability to manufacture weapons [2]

[1] https://global.espreso.tv/russia-ukraine-war-car-researchers...

[2] https://www.kcl.ac.uk/warstudies/assets/kcl-fasi-paper31-win...

Sorry - I really wasn't trying to be a jerk, but I do acknowledge that directly addressing the author is aggressive.

I was mostly trying to emphasize the importance of avoiding the negative experiences of people interviewing when the interviewer was wrong about something and won't flex, as exemplified in a couple of comments in this thread:

https://news.ycombinator.com/item?id=48839767

https://news.ycombinator.com/item?id=48840261

So to clarify my point in a more general way: We _all_ have some concepts wrong in our head, and we should all strive to be not only graceful but delighted if an interviewee is correct when we're wrong.

* introselect implementation often worst case n log n, typo

Depends if you're talking theory or practice. introselect is worst case O(n) but a lot of implementations implement it with avg case O(n) and worst case O(log n). Median of medians is worst case O(n) but it's slow so mostly avoided.

Right out the gate: the numbers must be sorted.

But they don't. I hope you, as an interviewer, have the grace to learn when one of your interviewees points out your mistake. :-) Median is O(n), not nlogn

(Well, the answer is "Anthropic, with claude code", but I'm not in possession of material information related to whether they are or are not in their right minds.)

But yes, of course there will be new bugs. But that's why 1.4.x for x > 0 is interesting. If the branch is being used and people are not reporting _more_ bugs, and the bugs you care about it are being fixed (successfully) on it, and it passes your tests, etc., ... I dunno. This is an application domain where you can do some pretty solid testing of it, comparative fuzzing, etc., so it doesn't strike me as entirely mad to jump over after a few minor releases where you can see the bug trajectory.

I'm a little puzzled: Why should you care? The language in which Bun is written isn't part of its API, if you will. You care that you have something that does various javascripty things according to a particular spec of what it's supposed to do. If a bug is fixed in 1.4.x it's fixed, why should it matter, really, if that's in Zig or Rust?

I wonder if this is part of what's clever about pitching their consultancy as slop cleanup -- nobody's likely to engage them to work on a pile of logic that's been evolving over a decade with weird load bearing corner cases. The "I just vibe coded a massive tangle" situations are more likely to be newer.

At least, one could hypothesize. Perhaps incorrectly. :)

You seem to be turning this into a discussion of vehicles, but the post you're replying to was purely about batteries. I get it - ICE cars suck. But speaking for myself, I waited until I could get LFP batteries before adding a lot of lithium to my house. I deemed the fire risk of NMC not worth the benefits. I now have about 15kWh of LFP and I'm happy as a clam.

Strongly agreed, and thank you - TIL about the truckee hitch, I've always been using trucker's hitches and now I'm going to go try to reprogram myself.

I'd add a butterfly loop to this list for those times you need to add a tie-in point to the middle of a rope for whatever reason.

Consumers having a preference is not ok?

I feel the same way about Android auto. I refuse to be locked into some terrible, never updated or expensive subscription vendor nav unit. I have a phone. I want to be able to use it.

Filippo Valsorda doesn't work for Google. He left there several years ago. He runs an independent "buy contracts with me to support development of open source cryptography software" thing.

I have no horses in this race and lack the expertise to judge, but this is part of a larger fight and djb seems to be on the other side of a lot of good cryptographers:

https://mailarchive.ietf.org/arch/msg/tls/ZBpcicZX1Dxnam2gMa...

Accepting 100% that it should be in some way deemed unacceptable (socially or legally) to fake what an apartment actually looks like, I did find using an image model really helpful in making design choices for my bathroom remodel. Mostly about whether to tile certain things where we couldn't quite visualize ourselves what the effect on the entire space would be.

One of the best queries I've done with an LLM recently was: Create a plan for improving the robustness and resilience of this code, particularly to untrusted inputs.

Gemini wouldn't do a security audit. But it came up with a great set of mitigations and identified an extant XSS flaw in the process of improving robustness.

There's an awful lot of good that can come from proactive, defensive use of LLMs. I realize there's also a lot of pain when the difficulty of exploit finding drops suddenly, but in the long term we may all benefit from the defensive side of this.

Read my comment more carefully if you think I'm describing the study instead of providing more general context for why people might find this particular study interesting.

I'm giving context for why a study of higher intensity cardio -in older people- might be interesting to people, and why it's not just "exercise good"

Mostly because functional strength is useful and keeps you alive. major goals as you age are avoiding falls and being able to continue doing things for yourself. Strength fits that bill pretty well (and it also improves fat free mass).

And on a slightly more technical note, recovering from higher volume becomes harder as you age, so focusing on a smaller number (5ish) of reps at higher weight gives you adaptation without quite as much stress.

But I should be clear, when I said real lifting, I don't mean to exclude any form of well calibrated progressive overload, whether that's strength focused or hypertrophy focused. I do mean to exclude the "go to the gym and lift a 10 lb weight the same number of reps each time" BS

No, but past recommendations for older adults (note that the average age in the study was 72 years old) were towards "gentle" or moderate exercise. We're seeing a shift now towards recommending real weight lifting and higher intensity as we age. ("Real" -> closer to powerlifting in terms of goals and methods)

That's incorrect, I have one on my desk right now. They've stopped selling it now, but I got one a year and a half ago:

Apple M4 Pro chip with 14‑core CPU, 20‑core GPU, 16-core Neural Engine 64GB unified memory 2TB SSD storage 10 Gigabit Ethernet Three Thunderbolt 5 ports, HDMI port, two USB‑C ports, headphone jack Accessory Kit $2,649.00

That's not nearly as true when you look at AI training clusters. They're basically supercomputers but without an FP64 focus.

(These are the systems to which GP was referring at Google.)

Sorry! Power Usage Effectiveness. It's a measure of the overhead of delivering power to the servers (or motherboards, depending on how you measure it), taken to include all other datacenter power overheads: AC/cooling, UPS losses, and sometimes transformer/rectifier losses.

A PUE of 1.2 means that for every watt of power you're using in a server, you're using 1.2 watts drawn from the grid (approximately). Those extra 0.2 watts are being spent on cooling and other things.