>351 dependencies for a simple trading bot using the official sdk crate >1GB target directory Is Rust becoming NodeJS?
Anonymous · 2026-07-11 14:54 [#7380][report] Don't worry about it
Anonymous · 2026-07-11 15:11 [#7410][report] >>22781 imagine the potential for supply chain attacks
>Compiling notavirus v0.3.894
Anonymous · 2026-07-11 15:15 [#7413][report] >>22783 downloading anything places from npm, pypi, luarocks, cpan, packagist, crates, aur is like sucking AIDS cock
Anonymous · 2026-07-11 15:22 [#7420][report] >>22781 Rust's package ecosystem has always been Node-like.
Anonymous · 2026-07-11 15:51 [#7454][report] >>22781 >modularization considered harmful ironically, the number of crate owners from your picrel could fit in two hands (or one). which gives me an idea for a tool... but back to the topic at hand, the number of "total randos" in the rust ecosystem is actually lower than you think. and it is the crate owners that you need to trust, and no one else. in fact, `Cargo.lock` allows for layered trust, as in the tool developer(s) you're trusting to use know(s) exactly the dependencies' code you will build. if you compare this to the distro model, where you have some rando upstream devs, a lot of rando distro maintainers, and an unknown combo of built dependencies, often outdated and/or randomly patched by distro randos, and three layers of infrastructure to trust instead of one (upstream -> distro, distro -> mirror, mirror -> you), if you had all that in mind, you will quickly realize that the "muh supply chain" arguments against "crates.io" in particular were always retarded. and i didn't even need to mention the track record of fat ZERO actual chain attacks on record (fake malicious crates with zero dependants don't constitute a chain).
Anonymous · 2026-07-11 15:54 [#7457][report] >>22781 always was
Anonymous · 2026-07-11 20:57 [#7786][report] >>22781 >use golang >everything I need is in standard library
Anonymous · 2026-07-11 23:20 [#7999][report] >>22781 >trading bot How are there actual adults out there who believe this shit works? just go to a casino if you want to gamble
Anonymous · 2026-07-11 23:51 [#8028][report] >>22781 Haskell is like this too. Install pandoc and hledger, every time I update its like 200+ haskell packages
Anonymous · 2026-07-12 00:23 [#8062][report] Genuinely fuck rust It's THE programming language for troons
Anonymous · 2026-07-12 00:42 [#8090][report] >1GB target directory Did you compile in release mode and use link time optimization?
Anonymous · 2026-07-12 09:07 [#8367][report] >>22784 >>22783 >my goodness, how scandalous, just imagine what COULD happen crates.io has existed since 2015, where are the attacks?
Anonymous · 2026-07-12 09:10 [#8369][report] >>22781 Use case for trading SDKs?
Anonymous · 2026-07-12 16:31 [#8510][report] >>22796 No usecase
Anonymous · 2026-07-12 18:49 [#8564][report] >>22792 It's because Haskell has a garbage standard library that lacks the most basic utilities for practical programming. It's the anti-Python. Even C's standard library is more complete.
Anonymous · 2026-07-12 21:03 [#8685][report] Why does it seem like Rust attracted all the mediocre Node.js devs despite being targeted at systems programming? It's weird how the Node culture is getting replicated there.
Anonymous · 2026-07-12 21:13 [#8689][report] >>22799 For a language, not coming up with "batteries included" is good for le job security or something
Anonymous · 2026-07-12 22:56 [#8716][report] >>22799 AI caused all the nodetards to think they can also handle backend, so a lot of these dumbasses switched to rust to code their own backends. I heard on a standup that "rust is the best language because memory safety is all that matters in microservice environments" and wanted to hang myself
Anonymous · 2026-07-13 07:05 [#8844][report] >>22799 because you're susceptible to peer pressure, and your knowledge/criticism of node doesn't go past "a lot of packages"
Anonymous · 2026-07-13 08:31 [#8853][report] >>22801 putting your imagined trend aside (people have been saying this way before vibecoding even became a thing), webshits are not a monolith. i would imagine a person who really understands typescript's type system (which is probably a small minority) to grasp a lot of components in rust's type system much easier than, let's say, a gotard. and that has nothing to do with your "hurr durr rust only gives you memory safety" retardation.
Anonymous · 2026-07-13 08:42 [#8858][report] >>22781 I hate this shit. I've tried to build some program I cloned from github. It told me to use Cargo. It was a slow and painful process and it bloated CACHE on 30 gigs.
Anonymous · 2026-07-13 10:57 [#8879][report] >>22799 What makes you think all programming languages aren't like this? Run mvn compile, go build, insert-fotm-python-tool, or in your derogatory example, npm install. They're all the same shit. Even C++ codebases will download code at setup and compile time. Are you people just clueless or something? What's next? Buildroot is node culture because your massive makefile spaghetti downloads 100s of pieces of code with gigabytes of intermediate outputs? Like how clueless are you?
Anonymous · 2026-07-13 11:26 [#8881][report] >>22805 Go and Python don't have pathetic std libs that are somehow worse than C's. Rust forces you to download crates for basic shit like imaginary numbers and random numbers. By its nature rust encourages more dependencies than other languages.
Anonymous · 2026-07-13 19:04 [#8942][report] >>22795 happened to me several times at an auth company
Anonymous · 2026-07-13 23:08 [#9008][report] >>22805 I don't think you would make such a poor comparison if you knew any languages beyond Rust and JavaScript/TypeScript. Internet-connected package managers are of course common, but only in the Rust and Node communities is it considered normal for a small-medium project to have a transitive dependency count in the high hundreds. Besides, Rust and Node cultures are similar in many ways: * An utter disregard for integration with the surrounding software ecosystem, e.g. traditional distro packaging. * Depending on very recent or even unstable versions. Bumping requirements unusually fast. * An appetite for buzzwords. Webscale! Async secret sauce! Blazingly fast! Rocket emoji! * A fondness for excessive terminal bling. * A preference for assembling programs out of a ton of tiny independent libraries, then churning most of these libraries every few years to chase minor improvements. If you're exposed to many programming cultures, the similarities are hard to miss.
>>22801 >AI caused all the nodetards to think they can also handle backend, so a lot of these dumbasses switched to rust to code their own backends. I'm not sure I believe this explanation, I noticed this phenomenon years before the LLM popularity explosion. Encounter a Rust fanatic, find their GitHub profile, turns out it's a JavaScript dev who has never used a systems lanugage before they got into Rust.