HN user

terseus

455 karma
Posts9
Comments12
View on HN

Why do we believe that LLMs are going to stop there?

Why do you believe they wont? I think it's reasonable to assume that we will hit a ceiling that current models will not be able to break.

We have robots walking just fine now, by the way.

Walking and reasoning are unrelated abilities.

I understand that it is not easy to relate to the author who pays (or was paying) $150 for a house cleaner, I understand that this is a 1-person history and may be highly biased, I understand the author is motivated to create a story from it.

However, if you think that any of the conditions described in the article are acceptable or that this is a fair price to pay for having AI, I think you are a horrible human being and I hope you'll be expelled from civilized society.

Is it, though? Can we really keep saying that "hardware will always be cheaper than human labour" when RAM prices are soaring, GPUs are becoming prohibitively expensive, and we're looking at a probably chip shortage?

I think the era of "poor software for fantastic hardware" is coming to an end.

I don't know in other countries, but in Spain you definitely don't go to the doctor asking for anything more complex than a paracetamol.

You tell the doctor your symptoms, he explores you and perform any tests considered appropriate, and the doctor decides the prescription.

Given that YAML it's a configuration language I'd say that not being turing complete it's a feature, not a bug nor a limitation; I always want my language files to be declarative to not suffer the perils of logic.

Edit: Also, I don't see the need for a turing complete language for something like docker compose, if you need something really complex you can always script a docker-compose.yml generator with all the logic and complexity you need.

I can't believe that people is comparing opening a project in a code editor with running a build script.

The PoC doesn't even open a file, it just opens the directory. It's a pretty big difference, when you execute a build script you _expect_ to run code, when you open a directory in your editor you don't expect any side effect _at all_.

My guess is that since the proc_macros returns a TokenStream, rust-analyzer have no way to know what it provides except running it.

I'm not sure there's a solution for this that doesn't cripple macros in Rust, apart from being able to configure rust-analyzer to ignore the macros, which clearly limit its usefulness.

Rclone is really a fantastic tool, its configurability based on backends allow for amazing combinations!

You can configure any cloud storage backend (B2, S3, GCS ...) and combine it with other utility storage backends, like "crypt" [1], "cache" [2] and "chunker" [3], I highly recommend it to anyone searching for a backup solution.

The only feature I miss from Rclone is automatic directory monitoring and mirroring, which I solved using Syncthing (but forces me to host an additional server for it).

[1] https://rclone.org/crypt/ [2] https://rclone.org/cache/ [3] https://rclone.org/chunker/