Where do they say anything like that? I’ve been following them very closely for years and they’ve always been super transparent that there isn’t one solution. They also do a lot of work to prevent trash from getting to the ocean in the first place.

deleted by creator

The flaw here is that the bots absolutely cannot do these human jobs, even right now. CEOs think they can / want them do, but that’s only because they’re greedy imbeciles.

I spent a loooong time trying to contact a human at my bank since I need to do my taxes and the form they sent me didn’t have the info I needed. I looked online and it also wasn’t there.

Their stupid AI bot could tell me basic info about where to find tax forms on their site, but when I said the one they sent me was wrong, it just kept repeating where to find the form.

It wasted hours of my life. Fuck these people.

There honestly should be a federal law saying businesses are required to put you in touch with a human if you ask them to. Taxes are required and I needed that info.

I wonder if this will push humanity to go back to books and libraries.

That hasn’t been my experience at all, and it’s been for both large refactors as well as complete rewrites.

Rust does care about some things like not having self referential structs or recursive types, but those are super easy to fix. Rust pushes you to not write code in the same way as other languages, and IMO that’s a very good thing. It’s not at all about systems stuff or memory layouts.

Rust’s ownership system is used to simply enforce correct usage of APIs. Memory safety is simply a subset of correctness. Many other languages, Java for example, don’t enforce thread safety, so you have to be really careful when parallelizing your code. In Rust, you could hire an intern fresh out of high school and I can know 100% that they’re not making mistakes with sending data across threads that isn’t thread safe.

Another example is file handles. Rust is the only mainstream language where it’s not possible to read from a file handle after it’s been closed. That has nothing to do with memory layout or systems concerns. That’s a basic invariant across all languages, and Rust stops you from making a mistake. Same with things like mutating an iterator during iteration and all kinds of other stuff.

That does mean it is more painful upfront, but that’s a good thing. You’ll run into many of the same problems in other languages, but at runtime, which is much worse.

As for graphs, I doubt the vast majority of programmers need to build custom graph structures.

You’re of course free to disagree. Just weighing in with my perspective.

Extremely hard disagree on the last statement. It certainly has tradeoffs, but they are almost all very valuable to many general applications which don’t need performance at all. I’ve been using it professionally for a very long time now and migrated multiple companies from JS, Python, Java, and C# to Rust and it brought huge advantages.

I didn’t love that article - Rust isn’t strictly a systems language. It’s general purpose, and a lot of the mechanics are very useful for general programs.

I’ve been writing async Rust professionally for 5 years and never needed to implement AsyncRead, or even Future directly. I’ve only used Pin for working with the async_stream macro. That stuff is very low level and probably would never be encountered by the vast majority of async users.

I agree with 99%, but not sure I see how async is a “fancy feature”. When you’re writing async code, async is boring and normal. I guess if you are writing programs that don’t need to be concurrent it’s fine to use sync variants of stuff.

I think they mean things like buying an electric car is much better, but it also currently means less of a range and less charging availability than gas stations.