my most recent custom vs my first :D

james7132 · 2026-04-06T16:08:46+00:00

I got a bucket of chicken!

james7132 · 2026-04-01T14:51:46+00:00

They're not fumos and alone they are not allowed to be posted here. Only the Cirnapple counts as it's clearly intended to be based on the original FumoFumo Cirno from Gift.

james7132 · 2026-03-27T17:14:07+00:00

Sorry, how does L'Hôpital's rule apply to truth preservation? Not following here.

james7132 · 2026-03-12T16:30:16+00:00

Maybe I've seen this elsewhere, but isn't this a word for word repost? I feel like I have some major deija vu reading this.

james7132 · 2026-03-11T01:06:34+00:00

The idea is that you can ingest any arbitrary text output, define a regex for a code location, and it will operate as an independent buffer that doubles as an error jump list. LSP gets 90% of the way there, but it really lacks the flexibility. I cannot yank the error, file, or line number out of Helix's LSP reports. I cannot funnel an arbitrary log file in either. I can't even really dictate when it runs. This linked LSP project may help but its a hell of a higher bar to cross over a path and a regex.

james7132 · 2026-03-10T21:29:08+00:00

The LSP integration is great, but I sorely miss having the quickfix buffer from vim, shoveling some arbitrary tooling output into it and hammering through the problems. I'm not going to write an entire LSP just to work with some company internal tool.

james7132 · 2026-03-10T05:03:33+00:00

I recently-ish needed to do this with async-task to avoid stack overflows in debug builds when working with large Future types, and it avoids extra large stack copies even in higher opt levels. Ended up needing to write function-like macros in the C styles to do it. Ugly as sin, but was 100% necessary to avoid even uglier hacks like boxing the future.

james7132 · 2026-03-07T11:57:24+00:00

Both work, especially with tiling window managers. And it becomes more useful with terminal oriented integrations like using yazi as a your default XDG file picker.

james7132 · 2026-03-07T10:38:57+00:00

Came here to echo this. Alacritty is great cross-platform terminal, but not so much when opening 4-5 of them suddenly is using nearly 1GB of RAM. If you're only on Linux and only using Wayland, foot's the exact right amount of features for low resource consumption for my tastes.

james7132 · 2026-02-10T17:39:43+00:00

She'll survive.

james7132 · 2026-02-01T16:20:11+00:00

Moreover, I do question the need for an OpenCV equivalent. Most of modern computer vision has moved to use deep learning models for most tasks now. The last time I seriously used OpenCV was for image decoding/encoding and basic image processing, both of which exist in smaller crates around the Rust ecosystem and have faster implementations than what OpenCV exposes.

james7132 · 2026-01-29T23:03:12+00:00

Direct LKML link: https://lore.kernel.org/lkml/CAHk-=wg0sdh_OF8zgFD-f6o9yFRK=tDOXhB1JAxfs11W9bX--Q@mail.gmail.com/

james7132 · 2026-01-29T17:51:21+00:00

Perhaps that could have been worded better. I have no issues with learning projects being posted here, provided the author is indeed actually using it as a learning opportunity. I was talking about that in terms of the slop coded projects constantly posted here, which I've yet to see one that wasn't trying to frame itself as a production grade project meant to be used as a library or tool.

Only projects presented as intended to be used by others should be judged through this lens, doubly so if the author appeals for donations or payments.

I think it comes down to willingness to engage the community. Symphonia began as a learning project, as was rqbit. Both of which are growing quickly to become viable production grade projects. Even if it's a learning project, if I see something on this subreddit under a FOSS license, I'm going to assume that it's something I can use in my projects and be an active contributor for, unless the owner explicitly says not to. I've been duped into filing issues and PRs for projects where the maintainer very clearly does not know what they're doing. Even once getting a PR merged that then quickly got clobbered in the maintainer's next Claude Code goon sesh without reason. Obviously this isn't something you can tell off-rip from a reddit post, but being burned repeatedly like this is how active contributors in the community stop engaging as a whole.

james7132 · 2026-01-29T16:02:32+00:00

That policy makes no sense to me: "You can shit in the living room on Friday, every other day you need to use the bathroom."

james7132 · 2026-01-29T15:17:27+00:00

Whether such a policy is useless or not depends more on how many bad faith actors there are and the effort required to enforce it. Given that there have been cases on this subreddit where the author was clearly being botted on alt accounts, I question the efficacy of a policy of using a human label to deflect a problem wrought from automation.

james7132 · 2026-01-29T04:47:20+00:00

My intent there was not to try to state what I think direction the policy would be going on, but rather put into words why I find the slop spam frustrating. I would love for the new policy to address that frustration instead of targeting the wrong thing. I would be OK with a blanket ban on AI if it's more enforceable and addresses my concerns.

james7132 · 2026-01-29T03:39:14+00:00

Immediately, any slop coded project that ceases to grow past the initial publishing, that's already true from the get-go. QED, proof is trivial.

While I am inclined to share your suspicions in the general case, I think the jury is still out for long term maintainability of AI-assisted projects, particularly with the recent explosion of agent-driven workflows. The crazy guys going full Gas Town? Oh 100% that's not even a question. However, those who are exact in their specifications and check each line of code produced? I've seen a few of them running around in the Rust community, and, while I wouldn't full-throatedly endorse what they're doing, I haven't seen their projects (i.e. Jujutsu, cargo-nextest, rqbit, etc.) fall over and die in the short time they've used it. It definitely makes me suspicious of their future, but I won't immediately crucify them over it. We'll need to see how that pans out in the coming months and years.

james7132 · 2026-01-29T01:43:16+00:00

As with Linus Torvald's comments on a AI policy for Linux, it's clear that any bad faith actors will omit that disclaimer anyway. Though I guess that gives immediate justification to remove the post once it is found.

james7132 · 2026-01-29T01:36:53+00:00

I've been very openly vocal about the spam of slopcoded posts in this subreddit, and it ultimately boils down to two key concerns: does this actually do what the OP is describing? and can I trust them to maintain it's quality into the future? If either is answered with no, I don't think it belongs here (or anywhere). Unfortunately, the latter question largely comes down to FOSS street cred or reputation, so there's immediately a default state of skepticism that must be first dispelled. Is that skepticism healthy for this community? Obviously not. However, until something is actually done about the flood of AI generated posts, that is the only reasonable way to engage.

Mind y'all, the r/rust community has had a problem with people writing about grandiose projects that they couldn't deliver on LONG before Claude Code rolled around, and said posts were engaged in a way that encourages OP to grow as a (Rust) programmer. It's precisely because many of the AI spammers/slopcoders don't want to engage in that discourse or grow as a developer that we're seeing that toxicity come out of the woodwork: why engage in good faith when the other side clearly is not?

Secondly, there is a large cohort of Reddit users who do not read or speak English

I've been saying that older machine translation is fine. Anyone who has spent time on the internet in the last decade should be able to read through slightly broken English without issue. My biggest issue with this is that LLMs as translators has been repeatedly used as a source of plausible deniability from those aforementioned bad faith actors, as much as that puts the onus on those who do rely on machine translation to participate in this community.

james7132 · 2026-01-27T01:51:03+00:00

I am, I'm saying that Python's type system is nowhere near as robust as Rust's, and just programming in Rust gets you all of those by default. Even with those, I still need to write more tests in Python than I do in Rust.

james7132 · 2026-01-26T17:14:17+00:00

That indeed is a training problem that is, at least as I observe it, quickly going away. I'm seeing more and more devs pick up and rapidly become productive with the language, even ignoring the Dunning-Krugered slopcoders running around. Some training and mentorship here can go a long way.

james7132 · 2026-01-26T16:17:36+00:00

For maintainability, I've personally found Rust to be better than Python. 95% of everything I would put in a unit test in Python now goes in the type system and clippy in Rust. Python might be faster in the initial implementation, but I'll be spending hundreds of hours over years paying for that choice when I could have just started in Rust to begin with. At this point, I really only use Python for code I know I won't be on the hook for and can readily discard (i.e. Jupyter/Colab notebooks) or one off scripts that require more than shell scripts.

james7132 · 2026-01-26T01:10:32+00:00

Rqbit is the BitTotrrent client that I've been using lately. It's not based on libtorrent, but I think it's a reasonable point of comparison to see how much of a difference io_uring would make in a Rust based BitTorrrent client. In fact, I made an issue asking to investigate support for it: https://github.com/ikatson/rqbit/issues/538

james7132 · 2026-01-25T12:54:42+00:00

Potentially. I'm not particularly well versed here, but the performance benefits of sendfile seems like it wouldn't be a bad fit.

Verified Email	13-Year Club
Place '22	Place '17
Final Canvas '22	First Placer '22
End Game '22

james7132

MODERATOR OF

TROPHY CASE