

Generally yes, unless it’s the original source of a story.
e-celeb content and news aggregators are never the original source of a story.
Generally yes, unless it’s the original source of a story.
e-celeb content and news aggregators are never the original source of a story.
That some can and already do that on the video sites they already browse.
People like shorts too, but that doesn’t mean Lemmy should be infested with such content.
We went from spam “news sites” to spam videos. Maybe an “original source” policy should be applied by moderators!
This applies to both hare and on !rust@programming.dev
Doubly linked list is one of std’s collections. And safety in Rust is built on top of unsafely, because there is no way around that.
Did you try to actually look up literally anything before asking?! Because simply checking out std::collections
docs would have given you some answers.
Who memory-holed 2021 an why❔😉
They talk too much. But almost none of them actually code or know how to at a good level.
We have someone just like that here.
That’s exactly the communicated meaning I was concerned an oblivious reader might get. You can use an updated Rust compiler 10 years in the future while your crate is still on 2015/2018/2021 edition. Editions are NOT software versions.
I might expect the Rust ecosystem to adopt these new features.
This again points to you maybe not understanding how editions work, or maybe I’m just reading it wrong again. But you “upgrading” has no effect on your dependencies, and vise versa (except indirectly if MSRV is a factor as another user mentioned).
Just upgraded
Weird wording!
Maybe it’s just me, but this may give the impression that it’s something that is strictly needed, or will provide any immediate improvement, which is not the case, unless you’re still actively working on these projects and plan to use/depend on features/behaviors required by the new edition.
While you missed the mark here since typst has all the important stuff open (I wouldn’t use the web interface even if it was free/open source), I appreciate that you’re keeping an eye open.
If you were in r*ddit’s rust community a few years ago, you probably would have been banned, just like me😄
A blog post from M$ mentioning Rust with zero code
=> straight to the top
A news article regurgitating the same thing a week later
=> straight to the top
Another news article two weeks later regurgitating the same thing, possibly with the addition of a random tweet from some M$ dev
=> straight to the top
Anyone not sucking nu-M$'s ****
=> banished to the bottom, or worse.
Things got so silly to the point where I made this jerk post (archive link) about one of these silly posts.
I wouldn’t correct you if this was a general community where the internet gantry hangs in numbers like the multiple !linux communities, but let’s keep things more factual here in !rust.
After Wedson quit months ago, no one from the Rust-For-Linux effort has quit/resigned/whatever. No one quit who is relevant to current mainline kernel development in general, either.
There is a difference between the actual Rust-For-Linux team, and Rust proponents who may write kernel code out-of-tree, or may happen to still be listed as maintainers in a dead poor GPU driver. Confusing the two is good for drama, but let’s not do that here.
And the bad boy maintainer is entitled to his opinion (which I disagree with of course). An opinion which will always be more informed and relevant than 99.999% of whatever the internet gantry has been contributing.
True. Moronix’s comment section is always good for a good laugh. Although the novelty wears off fast due to the lack of novelty/originality.
How dare you change the click-bait title❓
I mean, it’s a moronix post. No one was expecting some serious reporting anyway🙂
Otherwise, you could have just pointed to the mailing list thread directly (preferable).
But don’t use ctrl-b
What migrant from screen didn’t start by adding this to tmux config? 😄
set-option -g prefix C-a
unbind-key "C-b"
bind-key "C-a" send-prefix
If you’re serious about creating something good/better, you should use alacritty_terminal (not to be confused with the terminal app built on top of it) for low-level (from your PoV) terminal support.
This is something zellij
didn’t do. And now they have “basic functionality” bugs like this one open for years.
I also wonder what made you pick screen as a baseline to improve on instead of tmux
.
Is there a tiling Wayland compositor out there that supports applying custom shaders to windows (similar to picom)? This has been a known limitation for many years. And I brought it up myself with a couple of compositors’ developers, and they told me that it would break direct scan-out, and I told them that I would be fine with that, and then discussions fizzled out.
I also tried an x11vnc alternative I don’t remember the name of, and besides the generally buggy experience, it completely broke when power management kicked on the sever side (turning off the monitor IIRC). So that’s another show stopper, although maybe not as relevant as custom shader support which I need for applying my custom color inversion shaders to specific windows, otherwise, my vision would go bad quickly.
So yeah, I will be sticking with my Awesome WM (+picom +x11vnc) setup for a while too.
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?
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).
In any rust project, you start with API docs, and the examples folder if one exists. Just make sure the examples belong to the current version you will depend on, not the master/main branch. The link above is from v0.13.1 for example.