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.

The comment you replied to has no mention of “hours after the shooting”. That’s what te title of the post says. I don’t know if lemmy is acting up and you intended to reply to the main post instead of a comment.

Has anyone upvoting this comment read the article?

It says so in the article.

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

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.

“in 20 years” doesn’t get as much hype as “in 3 months”

Maybe if they said “in 3 months” instead we would’ve actually have had it in 20 years. Seeing how much ai attracts money with these obviously unbelievable promises.

From the makers of “fusion energy in 20 years”, “full self driving next year” and “AI will take your job in 3 months” cones “all code will be AI in 6 months”.

Trust me, it’s for real this time. The new healthcare system is 2 weeks away.

EDIT: how could I forget “graphene is going to come out of the lab soon and we’ll have transparent flexible screens that consume 0 electricity” and “researches find new battery technology that has twice the capacity as lithium”

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.

Or you can just uninstall edge.

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

PowerShell. You can get it for both windows and Linux. And it actually works with all Ctrl+shift+arrow combinations.

Being leased for their life time is called owning.

Land can be inherited like any other property.

There is private land.

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.