Arch485

I think there cannot be an objectively most correct punishment for a given crime. The closest we could maybe get is "undo the harm that you have caused", but some harm cannot be undone.

Hence morality and ethics, I guess.

Re: Max dimensions: You can truncate your input vector specifically for the index, and then when querying, you can query the index via a truncated vector and perform an additional full-length comparison as well.

For example: (taken from a project I'm currently working on)

```

SELECT *

FROM report_embeddings a

INNER JOIN report_embeddings b

    ON (

        subvector(a.embedding, 1, 768)::vector(768) <-> 

subvector(b.embedding, 1, 768)::vector(768)

    ) < $1

    AND b.id != a.id

WHERE a.id = $2

    AND a.embedding <-> b.embedding < $1

```

In this example, I truncate the embedding to 768 dimensions for the index and the lookup, (see the INNER JOIN) but do an additional full vector comparison as well. (in the WHERE clause)

This performs a fast but less accurate lookup into the index, and then only does the non-indexed full vector check for the matched results.

The police are like vampires. So long as you don't invite them, they can't come in. (with some exceptions of course, but that's not as pithy)

It's not that it's optimized away, it's that the authors have done a bad job translating their pseudo code into Rust etc.

In Rust, if you do not `await` a future, it does not run - so in their example where only C is printed, they must have translated this into some Rust code that does not await the call to print AB.

This is simply not something you would ever do in real life, and in fact the Rust compiler emits a warning if you create a future but do not await it.

A more "correct" approach would be to call `tokio::spawn` with the future to print AB. This would result in AB always being printed, usually in the order ACB, but with no hard guarantees on that order because of the semantics of the `sleep` call. (specifically, it will wait at least the amount of time specified, but possibly more)

It is. I definitely agree that strings in Zig can be tedious, but the upside is that if you need it, you can build a string library that does everything you want it to do, in the way you want.

For comparison, while Rust offers a very rich string library, it's also very strict about what you can/cannot do with strings, so if your use case falls outside of that you're out of luck. With Zig, you can pretty easily roll your own and make it do what you want. (and when Zig is post 1.0, I imagine there will be some very nice pre-made string libraries by the community etc.)

Honestly, that was sort of the impression I got. It's not that the meth is contaminated, it's that the meth is way stronger and more pure. I wouldn't be surprised if incredibly high doses of any stimulant causes schizophrenia.

I disagree, if you'd like to propose solutions to these problems as well as an implementation strategy, I'd be very happy to hear them! Source: am the author.

Most AI data centres use evaporative cooling. One of the linked sources talks about this; that 7 billion cubic metres metric is how much water gets evaporated into the air. (which makes that water no longer usable for drinking/watering crops/etc)

Up until pretty recently, I was unemployed and I also wanted a career change for similar reasons (although I'm in my 20s). I was broke, so going to school wasn't an option (plus I applied to a couple universities anyways and got rejected or waitlisted, I assume because of my age).

The economy is so messed up right now that the only jobs I found that didn't require a degree or several years of prior experience were hard labour for minimum wage. Even McDonald's apparently requires 3 years of experience.

So, my advice would be that school is expensive, wages are low, and if you're in a spot where you can reasonably get a decent paying job, you should take advantage of that. (as much as I would love to work in an industry that isn't the total shitshow that software is right now)

I agree completely; I think choosing Rust and then adding a GC is a weird design choice. If I was in a situation where I really, truly needed GC for my memory management, I wouldn't use Rust.

Exactly - purely "data driven" decisions are how we end up with ads really close to (or overlapping with) some button you want to press, because the data says that increase click-through rate! But it's actually a user-hostile feature that everyone hates.

I've never really had the urge to use GC in Rust, but if I were to speculate, I'd say easier cyclic references would be one benefit. And depending on the specific GC implementation, you can probably get around many of Rust's ownership rules because Gc<T> pointers are usually `Copy`, so you can pass things around everywhere and not think about references/ownership as much.

I think you're misunderstanding - most people's beef with AI art isn't that it "isn't made by experts", it's that

1) it's made from copyrighted works, and the original authors receive no credit; 2) it is (typically) low-effort; 3) there are numerous negative environmental effects of the AI industry in general; 4) there are numerous negative social effects of AI in general, and more specifically AI generated imagery is used a lot for spreading misinformation; 5) there are numerous negative economic effects of AI, and specifically with art, it means real human artists are being replaced by AI slop, which is of significantly lower quality than the equivalent human output. Also, instead of supporting multiple different artists, you're siphoning your money to a few billion dollar companies (this is terrible for the economy)

As a side note, if you have a business which truly cannot afford to pay any artists, there are a lot of cheaper, (sometimes free!) pre-paid art bundles that are much less morally dubious than AI. Plus, then you're not siphoning all of your cash to tech oligarchs.