it's unironically my favorite syntax. Supposedly this makes me autism

>>17702 syntax hate is always junior talk. the way they parrot that shit, you would think it's Uiua-level or something. now that's some proper autismo.

>>17701 I didn't. I stay with C for philosophical reasons and C++ for IRL practical ones.

>>17710 rust is much closer to C philosophically (whatever that means) than C++, or any other mainstream language for that matter (yes, even go)

>>17701 I thought rust could be a good replacement for C But in the end, rust is just an even more hellish python. Riddled with extension middlewares and littered with the corpses of a thousand projects where the dev got bored but also couldn't play nice with anyone else. The future is bleak.

>>17701 I can't code I just think it's fun how it goes snibbidy snab

>>17711 >Rust is closer to C No it's not. It has its own package manager. It has its own build system. It removes freedom from the programmer because "we know better than you what you want to do". It embeds it's own paradigms into the language. It requires static linking which in itself reintroduce classes of vulnerability that we thought were gone since the 90s. It grows and bloats more and more with every new version. The language is so complex that it only has one compiler that itself takes about 24 hours to build on a decent machine. It was made by Pozzilla because they can't code. It's made by people who can't code in C, don't understand C, therefore became C++ Devs by default, yet have the audacity to come to real C devs and tell them it's a replacement for C. You Will Never Be a C Programmer.

>>17750 >You will never be a C programmer Yeah but isn't that the point?

>rust thread without "muh trannies" spam is india rangebanned here?

>>17750 >It has its own package manager. not language >It has its own build system. not language >It removes freedom from the programmer because "we know better than you what you want to do". a language is by definition a set of rules. it can be argued that types "remove freedom from the programmer". repeat with everything else. you couldn't go three sentences without exposing yourself as a complete nocoder, and a very retarded one at that. >It embeds it's own paradigms into the language. not doing that => multi-paradigm => big language => the opposite of C another show of retardation. >It requires static linking which in itself reintroduce classes of vulnerability that we thought were gone since the 90s. it neither requires static linking, nor there are "classes of vulnerabilities" related to this. >It grows and bloats more and more with every new version. true for any language with new versions, *including C*, unless a language guardian requires "removed features >= added features", which is something that doesn't exist in the real world. >The language is so complex that it only has one compiler that itself takes about 24 hours to build on a decent machine. another comment where literally everything written is wrong. the language doesn't have one implementation (mrustc). the language is getting a second *full* implementation (gccrs). building satge0+stage1 compiler literally takes X minutes (as in, a single digit of minutes) on any half-decent desktop from the last decade. not only you are a nocoder. you never even compiled anything in your life. >It was made by Pozzilla because they can't code. more nocoder retard talk >It's made by people who can't code in C, don't understand C, therefore became C++ Devs by default, yet have the audacity to come to real C devs and tell them it's a replacement for C. more retarded nocoder talk with the predictable language-as-personal-identity give away. >You Will Never Be a C Programmer. same as above, and a perfect closing to this show of retardation. i would tell you to share c code. but that would be bullying at this point, considering a retarded llm wouldn't have been this nonsensical if it was the author lol

>>17701 I still reject rust simply because what we already have works.

rust looks cool but I don't like having bloated binaries and a package manager to build a low-level program. just that, I really don't have a manifesto about it.

>>17773 >bloated binaries binary size is not a real issue in most use-cases, including all desktop and server ones (yes, including low-speced ones). many people just don't understand the real implications. and in any case, you can have small binaries with rust. so you have the choice if you want to continue in your false beliefs: https://github.com/johnthagen/min-sized-rust people targeting *truly and relevantly* constrained environments already know what to do, and how to do it. >package manager if you're building something with dependencies, you're using a package manager (or acting as one, doubtful). the fact that it's a part of the build tool, and the whole process is streamlined, is an advantage, and a daily experienced one at that. no matter how hard some choose to pretend otherwise. and in any case, you can skip cargo and use rustc directly, or go full tard and use another build tool with rust support like meson (yes, they support building with dependencies too).

>>17767 that's a minimal requirement for the definition of "works" you're using. what language doesn't "work"?

>>17765 the vibe is infinitely better without them, isn't it? lol

>>17793 I mean the tools we have that are already written in C just work. We should be improving what we have instead of re-inventing the wheel. The only reason you'd want to rewrite something in rust is if you have ulterior motives. I see no good reason for rewriting everything in rust.

>>17829 rewriting *everything* in rust is a meme. and talking conspiratorially about a handful of "rewrite" projects reeks of tech illiterate retardation. and none of this has anything to do with the language anyway. and believe it or not, most rust code (as in >99%) is not a rewrite of something. shocking, i know. other "shocking" facts: the handful of "rewrite" projects are not done by some single "ominous" entity. * you are still allowed to improve tools written in C, or any other language. have at it. although i'm not sure what's to improve since they supposedly "just work".

>>17839 strawman, I accept your concession.

>>17765 no

>>17702 I really appreciate Rust for forcing me to confront problems my patterns have vs being ignorant of them until they cause a problem. It's not the final be-all end-all for me, I'm currently looking at Gleam and the Erlang ecosystem. I think a happy medium would be a Gleam app with low-level socket interfacing or buffer interfacing code being kept as Rust using the Rustling NIF system.

>>17750 >It requires static linking That's not even true, dynamic linking is completely possible in Rust.

>>17765 To my knowledge, yes. And Israel

>>17765 So was most of the Rust hate coming from Pajeet streetshitters who can't into Rust because of skill issues?

>>18045 /g/ or the majority of it was basically amerijeet culture. an unholy marriage between /pol/-style ameritards, and 12-22 year old "edgy" unintelligent jeets. i write that and i'm technically american.

>>17701 Is "why would I need to use that" part of an anti rust psyop, since it's not something most people would need to use most of the time? Most hobbyists just write toy programs, and in industry people will follow what's already established anyway

Hey guys, wondering if anyone can tell me what style.rs is for in rust/src/tools/tidy/src, I see it searches for problematic "magic numbers" but I'm not sure when it calls this or why.

I hate trannies and I hate the culture the language comes with. The language itself is good, but it's not an overhaul of programming and it has brought with it a culture of moralism over "memory safe languages" to the point where there's an implicit moral judgement on using C. Just look at channels like LowLevelLearning on YouTube that act like creating secure software in C is somehow impossible and revolutionary. Also, most things don't need to be written in Rust. Most networked applications should be written in Go unless you need what Rust offers since Rust just takes longer to write. Rust is a good replacement for C++, and I hope that it fully replaces C++ in the future. Fuck trannies. I still use Rust.