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

> No human can write better code than LLMs.

Bold claim...


I had a feeling when I read the title and then started reading the post, "this person must be young, probably a student." I think it's ironic that they're using such unscientific terminology like "fastest" given their background https://xiangpeng.systems/. So clearly, it's in the interest of marketing. Maybe some kind of job advertising/resume thing.

I can almost guarantee that someone has built a custom btree for their specific domain which is faster than this; and that they probably have some or all of the techniques used in this library that are the main contributors to performance, as well. Prefetching is probably the main one they'll claim, and I know personally of some proprietary implementations which have it.

I would like to see some more humility, but I suppose that when you've already resigned your own potential to being below an LLM, then what's the point.

It's not possible or useful for them to grow anymore. Some new frontier model next week will outdo whatever ephemerally useful project this person writes, right? That's the logic?


Especially since it's trivially proved wrong by inspecting the code. It's invariably awful.

This is only a statement that could be written by someone that doesn't read the code.


I wish his llms included sanakirja* in the comparisons, which has some (human made) speed claims*.

* https://docs.rs/sanakirja-core

* https://pijul.org/posts/2021-02-06-rethinking-sanakirja#benc...


.gh is Ghana, not Greenland


oops :)

I misread.

Thanks for the correction.


It's not a subset of python.

For instance this program works in this interpreter, but not in python:

    fxx i in rxxxx(10):
        pxxxx(i)


That isn't part of the language though. That's just input that it doesn't handle properly. The author acknowledged it lacks error handling.


If the original code was written in Rust, then I don't think the Rust compiler is allowed to do any of these "optimizations" of rewriting floating point expressions.


The C compiler also isn't allowed to do all of them. However some people use fast-math or compilers that default to fast-math to break the rules. Some older targets also may use the 80 bit fpu, which is its own mess and any sane compiler will default to properly sized SSE instructions instead.


On x86, LLVM does not follow strict IEEE 754 behavior all the time.


IIRC it also depends on the CPU's storage and capabilities.


There is a PoC that does exactly that here: https://github.com/tgies/copy-fail-c


I have set up Ctrl+k to kill (SIGKILL) the front process in my terminal. I just use that for hanging connections and other hanging processes.


> The only real disruption I'd say is if you happen to be buying something online that triggers the 3DS prompt (an additional security layer to prevent cards getting stolen/scam). In Denmark the 3DS prompt for VISA at least uses MitID to verify you are the owner of the card, so that'll obviously not work when MitID is down.

If you use Lunar, the 3DS prompt uses the Lunar app and not MitID.


You probably just want to use `.peekable()`: https://doc.rust-lang.org/stable/std/iter/trait.Iterator.htm...


Note that `peekable` will most likely break autovectorization


> Invalid Date is just a Date with the "Unix epoch timestamp" of NaN. It also follows NaN comparison logic: > > > invalid === new Date(NaN) > false

This is just because a JS Date is an object and have nothing to do with the inner representation.

    > new Date(0) === new Date(0)
    false


I got a 403 Forbidden error when trying to register a user.


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

Search: