You can spend millions on building power lines over oceans and such. Or you could just spend that money on building your own power production. Might be more expensive (or not), but you get to control the production.

When 2 people that know a language want to talk shit about someone else that doesn’t know the language, the first thing they’ll do is speak that language.

It’s not an unreasonable fear at all.

Depending on context it might be stupid or make sense.

At my company, which has 100% Spanish employees, we can talk among ourselves in Spanish. However, in things “for the record” such as jira tickets, git commit messages, documentation pages, they have to be in English.

It makes no god damn sense. Nobody is going to read Jira ticket #6738 in 40 years when we are a multinational. It’s a ticket about fixing a typo in page 567 of the documentation. 100% of employees speak spanish, and some have dogshit English.

They may be worse than a very good programmer. But will be much faster answer. The real captcha is not to check if the answer is correct. It is to check the time it takes to answer.

Except humans that are not very good programmers will just give up and answer quite fast. Or just click away lol.

I haven’t read 90% of your comment since it is out of the topic of the discussion. The “trap” is trying to argue with mee about something I haven’t even mentioned.

I don’t know whatever that language is doing is called, but it’s not reference counting. It’s doing some kind of static code analysis, and then it falls back to reference counting.

If you call that reference counting, what stops you from calling garbage collectors reference counting too? They certainly count references! Is the stack a reference count too? It keeps track of all the data in a stack frame, some of it might be references!

I don’t know what you read on my reply. But your reply makes no sense.

Let me rephrase it if you prefer:

Claiming that Rusty’s borrow checker is reference counting is hugely misleading. Since the borrow checker was made specifically to prevent the runtime cost of garbage collection and reference counting while still being safe.

To anyone unaware, it may read as “rust uses reference counting to avoid reference counting, but they just call it borrow checking”. Which is objectively false, since rust’s solution doesn’t require counting references at runtime.

I don’t know what mutable string or any of the other rant has to do with reference counting. Looks like you’re just looking to catch a “rust evangelist” in some kind of trap. Without even reading what I said.

There is no reference counting if the count is always one.

The defining feature of reference counting is that its a runtime check. Which in turn results in a runtime performance.

If there is no in memory counter at runtime, nobody calls that reference counting.

It’s more than 10 years old. It has stable syntax, big standard library, big library ecosystem, plenty of rust programs already in production.

If by “evolving” you mean “changing”, I don’t think that is an issue at all. At most, they add features. They don’t change or remove. And with the editions system, it should be no issue.

If by “evolving” you mean “improving”, then I don’t see how that could ever be an issue.

Because it can be done for multiple lines too. And you can do else-if too. Also, “if” and “else” is more recognizable than “?” and “:”

x = if y > 5 {
    println!("Y was over 5");
    z + 5
} else if y < 0 {
    handle_negative_y(y);
    z - y
} else {
    println!("<WARN> unexpected value for y"}
    0
}

This is valid rust. I don’t know if there are more languages with this feature

Swords had phrases written on them too. This has been happening since forever.

No.

A stack overflow is a symptom, not the illness. A fork bomb is an illness.

Software coming from the mathematical point of view, assummes it has infinite resources. However, a real computer has many resources that are finite.

CPU time is finite. Memory amount is finite. There is a finite number of network ports. And so on.

A stack overflow just means: “you have run out of this resource called ‘the stack’”. The stack is a region of the memory. Each thread of each process has 1 stack, and it is not infinite in size. This program will cause a stack overflow because it is infinitely recursive, and each function call will consume a bit of the stack.

A forkbomb is not the end of a finite resource. A fork bomb is a program that uses “forking” to rapidly consume system resources. A fork bomb might cause a stack overflow. Or an out of memory issue. Slow the computer a lot. Or if the OS has a hard limit for process amount, it might reach that limit.

I do enjoy cleaning code a lot.

When I work on shitty code I’m always thinking about how shitty it is and thinking on how a different design would make it much easier.

When you clean the code, you’re implementing that perfect design you were thinking of all that time. And you know from that point on you’ll be thinking less about how shitty the code is.

If your only task is to clean code and you’re not gonna work on that codebase afterwards, it’s not as rewarding though.

When brown, they are inmigrantes anda those are ghettos. When white, they are expats in expat communities.

You think drivers from your <country/state/city> are bad? That’s because you have never driven in my <country/state/city>

Mobile firefox allows installing add-ons. Unlike mobile chrome.

Yes. Kilo means thousand. However in some contexts, a single calorie is the same as a kilocalorie. Don’t ask me why.

There are 2 calories, the small one and the big one. And the big one is exactly the same as a thousand of the small ones.

If it has three letter variables, chances are it was also written by someone that doesn’t want to code either

Ah, just kill half the humans. That will make water consumption go way down. Follow me for more resource-saving tips