Hacker Newsnew | past | comments | ask | show | jobs | submit | dimview's commentslogin

Brown bears attack people in Russia quite frequently [1].

[1] https://meduza.io/en/feature/2026/09/11/russia-has-a-bear-pr...


Author here, if that word still applies to code written with the help of an LLM.

I paired Russ Cox’s idea to add images inside QR code [1] and spelling out the contents in a low resolution bitmap font.

[1] https://research.swtch.com/qart


You can do it a bit faster by not quicksorting the entire array, as you don't really care about the order of the lowest and highest numbers as long as they are not close to the middle.

There is also an approximate algorithm that does not keep all the data in memory at the same time.


The rabbit hole goes deep fast with this one!

https://rcoh.me/posts/linear-time-median-finding/

I vaguely recall learning a randomized (approximate) streaming median algorithm in grad school, but the details have left my brain…


For Opus 4.8, 142.3k input, 2.0m output for the entire project. No longer have access to Fable 5 to check.


Thank you. Of course the dates were out of order. The Java library (com.hp.creals) is 1999-2004, paper is from 2005. Unfortunate price of LLM-assisted development. Corrected.


That should be doable, too. Maybe as a next project.


Correct, but if you don't know the next digit is 2, you can think it's all 9s, another representation of an integer number.


Author here. I could not find a constructive‑reals calculator on iPhone, so I ported the engine Android uses: Hans Boehm's com.hp.creals plus AOSP's UnifiedReal/BoundedRational. Used Opus 4.8 to do the port and Fable 5 for the review.

Fable 5 caught a couple of real concurrency bugs the port introduced while adapting Java's synchronized/AsyncTask to Swift concurrency, including one that was a memory‑safety bug on shared singletons like π, not just a wrong digit. None would have shown up in the unit tests. Writeup has the details.

It's an early iPhone TestFlight beta (link in the post); happy to go deep on either the constructive‑reals side or the AI‑assisted‑dev side.


Maybe you should correct the errors in your post before worrying about the code.


Corrected the dates, thank you! What are the other errors?


The old HP calculators, and their emulators, have a computer algebra system, for symbolic maths, that supported this. The user interfaces leave much to be desired, but some also have reverse Polish notation!


This is different from a CAS. For example, if you ask it to do exp(100)+1-exp(100), it does not rearrange and cancel out the two exp(100)s. Instead, it does exp, addition, and subtraction, all with as many digits as you ask for.


Sure. I was speaking to the what, not how.

> that doesn’t round at all. It computes with constructive real numbers: every result is exact, and you can scroll any answer for as many correct digits as you want.

A CAS is a practical way to achieve this, where everything is stored symbolically, with no rounding, until final calculation. Unlimited precision was through Erable [1]. This was included with/as HP49 CAS, but was an add-on with HP48. Many HP48 are on the iOS app store. The one I tried about a decade ago had the add-on, and I see many still there (but not sure if they have the add-on).

The "S" in CAS is "system", so it's a bit open.

[1] https://en.wikipedia.org/wiki/Erable


Looks like it uses seven colors (including bodies of water). Can it be done with fewer colors? The four color theorem does not quite apply, as all bodies of water have to be the same color.


Why does everyone likes bowline so much when eskimo bowline or kalmyk loop (http://dimview.org/knots/) is much better?


Can you quantify why it is better?

Bowline -- outrageously strong, simple to tie, easy to undo, can tie it around things.

What can be better?


Kalmyk loop is exploding - pull to untie. Bowline is not.

Bowline requires stopper knots when used on on modern ropes, otherwise it can slip. I've never seen kalmyk loop slip.

Both are simple and can be tied around things.


I would never trust an exploding knot while rock climbing.


Eskimo bowline is non-exploding, nevertheless I wouldn't use bowline (or eskimo bowline) while rock climbing without somehow securing the working end.

Kalmyk loop (which is exploding variant of eskimo bowline) is probably not secure enough for rock climbing, but better than bowline for other tasks. Less likely to spill and easier to untie.


In climbing, a great property to have is to be able to identify if a knot is tied correctly by just glancing at it. Figure-8 is obvious. A double bowline is fairly easy. Not so sure about other knots...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: