Patryk27

I’m pretty sure they meant the “post death” copyright, considering the context.

> And even if he changed his mind about some things, he cannot admit it, as that is not what his followers want to hear from him.

I don't think that's true - over the years he's changed his mind from "LLMs are useless slop machines" to "LLMs can be useful when applied wisely".

For instance in "The AI Hater's Manifesto" he says:

> It just came to me — the problem that I have with most people using LLMs is the delineation between outsourcing work and outsourcing thought. Those using LLMs to write little scripts or BQL code on a Bloomberg Terminal are inoffensive. [...] A tool being used as a tool to do tool things — in many cases involving the LLM writing a little 30-line Python script! — is not a problem, though it’s also not a trillion-dollar industry that needed to steal everybody’s art and writing.

Similarly, in "The More You Buy, The More You Lose":

> Sidenote: The only truly useful use case I’ve found is on the Bloomberg Terminal’s ASKB feature, which takes natural language and turns it into BQL code to make requests of Bloomberg’s datasets. It’s genuinely useful!

You can perhaps say that he underestimates what the technology is capable of (or, conversely, that other people overestimate LLMs) - but that's a different kind of conversation.

So you’re saying the modules have a suboptimal design for non-Framework laptops.

Sure. But this does not make them proprietary, they work fine with non-Framework laptops as well.

I don’t follow - how are modules based on USB-C proprietary?

My Framework ethernet dongle works perfectly fine with a Mac that I use for work, for instance.

> If you really think that switching language is the main driver to get safe programs [...]

I didn't write that.

> [...] the you are on the list of people replaceable by LLMs.

lol, love a high quality discussion

> Memory management is just a part of the problem.

Sure, then using Rust is a step forward, because that's one less thing you have to worry about. Seat belts don't save all people, but a car equipped with seat belts is - on average - safer than a car without seat belts.

Regular expressions are not Turing-complete.

There are no comment-based directives in Rust, are there?

> [...] it catches logic errors like this

but Rust's type system did catch this error - and then author decided it's fine to panic if this error happens

> You won't see Go or Java developers making such strong claims about their preferred languages.

yess no Java developer ever said that OOP will solve world hunger

> Worrying about things like this without profiling can cause a lot of unnecessary complexity when planning abstractions in Rust.

:+1: - it was mostly about "damn, it _feels_ like there should be a better way".

> You might be able to get away with the lock approach and you may even be able to use Rc<RefCell<_>>, which would get a little speed up.

In this particular case that'd be a bit more awkward, because in the actual game the UI is driven by async fn (the rendering itself is sync, of course, but waiting for input is async, and both happen as a part of the same function).

`spawn_local()` could be a good enough solution for that, though.