super_flanker

What is "linting efficiency", never heard of this term before?

> long before LLMs

I thought this thread was about an ideal language for LLMs, no?

Why would you think so? Rust provide better type system and abstraction mechanisms compared to Go, hence equivalent system should have less lines of code, at least in from my experience.

This must be a sarcasm, right?

> I was referring to mandate to use it at big companies.

I've worked in almost all of big tech, and these companies don't create mandate just because "Trust me bro" or to gain some "political achievements". Their are teams who champion new technology/languages, they create proof of what new technology will bring to the table which cannot be filled with existing ones. I left amazon 7 years ago so don't know about recent development. However at Meta/Google teams are encouraged to choose from the mandate languages and if they can't they need to request for exemption and justify the exception.

> It might be counterintuitive, but garbage collectors in multithreaded code can be very efficient.

What has garbage collector to do with multithreaded code? Once you have two or more threads which needs to share data, they need to sync and you'd end up using some kind of lock, which will affect the performance. GC doesn't make anything efficient or less efficient here. It might make the code simpler as you don't have to worry about allocation/deallocation, but I don't see how it's magically going to remove the lock.

No, you don't. All you need is to create a folder `bin` and any file with `main` fn in it will create a binary.

And tell me how that pointer semantics would do * a very strict type checking * Pattern matching * Algeberic data type

Plenty of people don't write Rust for additional memory safety, they write Rust because the features provided by it is overall very balanced & encourages developer to write code which handles almost all edge cases.

This, from my limited experience working on AOSP at Google, only the newer code were being written in Rust, not the existing code. But that was 2 years ago.

I agree with simplicity and ease of learning Go.

> 3 years working with I might have had at most 3 times nil pointer crashes in prod

I've been running a rust app for my personal trading app and a small service at a very large FAANG company for more than 3 years, and guess what I'm yet to see a nil crash.

> Their goal is by end of year.

It's like what 6-7 years since the goal was "end of the year".

What exactly? I work at Instagram.

Gotcha, yeah you got me there with so many `&`. Good one.

It indeed doesn't look elegant, however I've never in my experience seen a usage like this. Do you have any reference where you might have seen this kind of usage.

What's wrong with using 3rd party library?

Can golang stop you from using a channel when it's consumed/closed?