I think the “controversy” is just tribalism. I’ve never once witnessed a case of any of the negative adjectives thrown at the Rust community. They’ve always taken exceedingly fair and good-faith approaches to discussing any critique of the language.

Their snark is reserved for the weird “anti-woke” crowd that hates Rust for some reason.

I just use nushell’s builtins instead of wrangling with IFS and bash idiosyncrasies. It’s been years since I’ve corrupted data by parsing text wrong.

But even if someone doesn’t want that: apart from using it in legacy scripts, grep is just a strictly less useful ripgrep these days, no?

My people!

Nushell is pretty nice. It’s the good parts of “what Microsoft is doing”, i.e. real structured data in a shell-like language and real error handling.

Since you mentioned LocalSend: https://syncthing.net/. It’s a way to sync files between devices. And since I bring my phone wherever I go, that means it works seamlessly for me.

All you said also applies to Linux!

• Qt “cute” (the UI framework)
• QT “cutie” (QuickTime the Apple media framework)

Because they just have their own brain chemistry as the basis of it whereas the above comment clearly states:

Rust has proven empirically that the tradeoff between performance and safety doesn’t need to exist.

Which is truth. And it’s much easier to base a coherent argument on truth rather than vibes.

Wow you’re insane. “I know, I’ll discredit the woman who just pointed out that it’s hard to get credit in her field as a woman ”

Python is just glorified shell scripting

Absolutely not, python is an actual programming language with sane error handling and arbitrarily nestable data structures.

I don’t like the indentation crap

Don’t be so superficial. When learning something, go with the flow and try to work with the design choices, not against them.

Python simply writes a bit differently: you do e.g. more function definitions and list comprehensions.

Not only is there a UInt8Array, there’s also a bunch of others: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray#typedarray_objects

Great point, but this part of the quote is still dumb as rocks:

Coding is just kind of like the language that we talk to computers. It’s not necessarily the skill in and of itself. The skill in and of itself is like, how do I innovate? How do I go build something that’s interesting for my end users to use?

Sure, if you have a big workforce hand-coding UI, you might replace some of them by better tools. But things like that are a fraction of a fraction of the responsibilities developers have

Yeah, the motivation here is “please panic-buy our GPUs/please panic-buy into our cloud GPU infrastructure ”

Huh, I really like code like that. Having a multi-step process split up into sections like that is amazing to reason about actual dependencies of the individual sections. Granted, that only applies if the individual steps are kinda independently meaningful

To adapt your example to what I mean:

Baz do_stuff(int count, boolean cond) {
	Foo part1 = function1(count);
	Bar part2 = function2(cond);
	return function3(part1, part2);
}

This allows you to immediately see that part1 and part2 are independently calculated, and what goes into calculating them.

There are several benefits, e.g.:

1. if there is a problem, you can more easily narrow down where it is (e.g. if part2 calculates as expected and part1 doesn’t, the problem is probably in function1, not function2 or function3). If you have to understand the whole do_stuff before you can effectively debug it, you waste time.
2. if the function needs to be optimized, you know immediately that function1 and function 2 can probably run in parallel, and even if you don’t want to do that, the slow part will show up in a flame graph.

dbg!() for Rust users

He works on Linux where he controls the whole stack down to the metal and I love that for him, but other people have to call library code, and them debug that if it doesn’t work as they thought it would.

You’re right, of you have compete freedom, do that. If the place you want or need to go to is most comfortably reachable via rattlesnake road, bring boots.

In other words, if you don’t think the wasm landscape is mature enough to build a web thing with it, you are stuck with JavaScript, but you don’t have to rawdog it. I haven’t run in a single weird thing like this in years of writing typescript with the help of its type system, ESLint and a formatter.

[citation needed]

Just use a formatter. It’ll show you that the second one is two statements:

1. {} (the empty block)
2. +[] coerce an empty array to a number: new Number(new Array())

I haven’t read anything this cursed in a while