Bait or not, I’m not sure why you’re getting such a negative reaction. People are getting too sensitive!

Btw, do sanitizers hurt your brain too?

It has some. Related Lemmy Issue. I actually remembered wrong. Should have wrote “NOT implemented client-side”.

I’m too busy to double-check, but it is possible that Lemmy is ready for this now.

Because besides the jerking style, PCJ is a “no backlinking” community.

This was blocked by lack of some features in Lemmy.

I lost track of what got implemented over time and what didn’t.

Some/All of these features would be needed:

• Option for a community posts to not appear in local/global feeds.
• Option for a community posts to not appear as cross-posts.
• Option for a community to not appear in instance sidebar recommendations.
• (possible overkill) option to not appear in community search (by name, without !).

First two are the most relevant. I think the first at least got implemented client-side (not sure).

Releasing a v1 would be misleading anyway, even if the language itself is ready for it (it isn’t)… because they use zig in their standard library 😉

There is nothing neat about anything xdg.

I’m glad you figured it out.

I don’t know what is it with new rustaceans and binary size, but many of them seem to be incessant on wasting time uselessly optimizing it, usually without actually understanding what they’re doing, without gaining any relevant benefit, and possibly even causing relevant harm (e.g. degrading run-time performance for no good reason).

making points that aren’t even particularly that new.

(putting my Rust historian hat on)

Even the name stdx[1][2] is not original.

It was one of multiple attempts to officially or semi-officially present a curated a list of crates. Thankfully, all these attempts failed, as the larger community pushed against them, and more relevantly, as the swarm refused to circle around any of them.

This reminds of a little-known and long-forgotten demo tool named cargo-esr[1][2]. But it’s not the tool, but the events it was supposedly created as a response to that is worth a historical mention, namely these blog posts[1][2], and the commotion that followed them[1][2][3][4].

For those who were not around back then, there was an obscure crate named mio, created by an obscure developer named Carl Lerche, that was like the libevent/libuv equivalent for Rust. mio was so obscure I actually knew it existed before Rust even hit v1.0. Carl continued to do more obscure things like tokio, whatever that is.

So, the argument was that there was absolutely no way whatsoever that one could figure out they needed to depend on mio for a good event loop interface. It was totally an insurmountable task!

That was the circus, and “no clown left behind” was the mindset, that gave birth to all these std-extending attempts.

So, let’s fast forward a bit. NTPsec didn’t actually get (re)written in go, and ended up being a trimming, hardening, and improving job on the original C impl. The security improvements were a huge success! Just the odd vulnerability here and there. You know, stuff like NULL dereferences, buffer over-reads, out-of-bounds writes, the kind of semantic errors Rust famously doesn’t protect from 🙂

To be fair, I’m not aware of any big NTP implementations written in Rust popping up around that time either. But we do finally have the now-funded ntpd-rs effort progressing nicely.

And on the crates objective metrics front, kornel of lib.rs fame, started and continues to collect A LOT of them for his service. Although, he and lib.rs are self-admittedly NOT opinion-free.

DISCLAIMER: I didn’t even visit OP’s link.

how does that help when I’m searching a non-Rust project via the GitHub web search interface

Fair.
But you are writing a comment under a topic regarding a Rust-flavored IDE, posted to a Rust community. With neither the IDE nor Rust involved, your quoted problem statement is 100% off-topic.

There is a YouTube video in Servo’s homepage.
The first minutes of that video answer your question.

I for one am happy we’re getting an alternative to the Chrome/Firefox duality we’re stuck with.

Anyone serious about that would be sending their money towards Servo, which resumed active development since the start of 2023, and is making good progress every month.

I would say nothing but “Good Luck” to other from-scratch efforts, but It’s hard not to see them as memes with small cultist followings living on hope and hype.

Not sure how what I write is this confusing to you.

• Tests don’t necessarily live in paths containing test.
• Code in paths containing test is not necessarily all tests.
• cargo expand gives you options for correctly and coherently expanding Rust code, and doesn’t expand tests by default.
• rg was half a joke since it’s Rust’s grep. You can just pipe cargo expand [OPTIONS] [ITEM] output to vim '+set ft=rust' - or bat --filename t.rs and search from there.

What part are you struggling with?
The ripgrep (rg) part, or the cargo expand part?

You two bring shame to the programming community.
Just ripgrep cargo expanded output for f**** sake.

I thought I saw this weeks ago.

May 21, 2024

yep

Anyway, neovim+rust-analyzer+ra-multiplex is all I need.

Not to minimize their work, which is actually amazing!

you wouldn’t know because…

Still based on GNOME.

you don’t have a single clue about what they are actually doing.

that’s not what I’m looking for when I’m looking at a backtrace. I don’t mind plain unwraps or assertions without messages.

You’re assuming the PoV of a developer in an at least partially controlled environment.

Don’t underestimate the power of (preferably specific/unique) text. Text a user (who is more likely to be experiencing a partially broken environment) can put in a search engine after copying it or memorizing it. The backtrace itself at this point is maybe gone because the user didn’t care, or couldn’t copy it anyway.

Don’t get angry with me my friend. We are more in agreement than not re panics (not .unwrap(), another comment coming).

Maybe I’m wrong, but I understood ‘literally’ in ‘literally never’ in the way young people use it, which doesn’t really mean ‘literally’, and is just used to convey exaggeration.

But why can’t we fight to make Rust better and be that “good enough” tool for the next generation of plasma physicists, biotech researchers, and AI engineers?

Because to best realize and appreciate Rust’s added value, one has to to be aware, and hindered by, the problems Rust tries to fix.

Because Rust expects good software engineering practices to be put front and center, while in some fields, they are a footnote at best.

Because the idea of a uni-language (uni- anything really) is unattainable, not because the blasé egalitarian “best tool for the job” mantra is true, but because “best tool” from a productive PoV is primarily a question of who’s going to use it, not the job itself.

Even if a uni-language was the best at everything, that doesn’t mean every person who will theoretically use it will be fit, now or ever, to maximize its potential. If a person is able to do more with an assumed worse tool than he does with a better one, that doesn’t necessarily invalidate the assumption, nor is it necessarily the fault of the assumed better tool.

Rust’s success is not a technical feat, but rather a social one

fighting the urge to close tab

Projects like Rust-Analyzer, rustfmt, cargo, miri, rustdoc, mdbook, etc are all social byproduct’s of Rust’s success.

fighting much harder

LogLog’s post makes it clear we need to start pushing the language forward.

One man’s pushing the language forward is another man’s pushing the language backward.

A quick table of contents

Stopped here after all the marketing talk inserted in the middle.
May come back later.

Side Note: I don’t know what part of the webshit stack may have caused this, but selecting text (e.g. by triple-clicking on a paragraph) after the page is loaded for a while is broken for me on Firefox. A lot of errors getting printed in the JS console too. Doesn’t happen in a Blink^twice browser.

From my experience, when people say “don’t unwrap in production code” they really mean “don’t call panic! in production code.” And that’s a bad take.

What should be a non-absolutest mantra can be bad if applied absolutely. Yes.

Annotating unreachable branches with a panic is the right thing to do; mucking up your interfaces to propagate errors that can’t actually happen is the wrong thing to do.

What should be a non-absolutest mantra can be bad if applied absolutely.