I really feel like quitting IT, and going back to University.
If student loans are interest-free in your country, a second field of expertise is a decent idea since most STEM fields pair well with programming.
yeah python and javascript are incredibly
thankfully we also talk about normal languages (c and lisp) a lot
Since I have designed and implemented a bunch of my own programming languages, I have come to appreciate the syntactic design of python far more than I did previously. I am no longer a python hater because of it. I feel a similar way with lisp, but that is more related to my renewed appreciation of lambda calculus.
C is still incredibly cursed, blows my mind that we just let that exist unchecked for so many decades. Rust should have existed in 1990.
So is Rust astroturfed and if so, why do you think that is? I don't understand why Rust has so much buzz around it from the top but the only people I have seen be interested in using it personally are doing it to virtue signal and they're always wanting to rewrite something that already exists. I haven't seen people use it as their preferred language for writing their own programs, usually that's C++, C#, Java, or Python anecdotally. It's peculiar.
I use it for all of my personal programming and most of my professional programming, and I have for years. It's simply unparalleled in usability and expressiveness, I'm able to lean on the tooling and standard library to move faster using rust than anything else, and be confident that my programs won't exhibit unexpected behaviour that violates the memory model and shared resource access of an OS thread. I am very rarely held back by the compiler, and when I am, I'm glad I was. Previously, I used C++ full time for everything. I have found subtle memory corruption bugs in my old C++ programs when I re-wrote them in rust years ago, just like uutils has found within the GNU C coreutils as a result of their efforts in producing identical output to the GNU C coreutil counterparts. It would be much better to be GPL than MIT.
Most of the bugs and exploits are bad memory management in big projects, and you gotta ask why is it like that? I'd say it's laziness or over crunched workers, that's mostly why.
Fundamentally, a software bug is a discrepancy between the expectation of software's behaviour and software's actual behaviour. When you are programming complex software systems, even if you are a highly skilled programmer and super duper careful, it's still hard to reason about the lifetimes of allocated memory*, so eventually even the best programmers will write code under the expectation of certain memory conditions, where unexpected conditions can still occur, and that leads to memory corruption bugs.
John Carmack's related opinion (
source):
John Carmack said:
And I reached the conclusion that anything that can be syntactically allowed in your language, it's gonna show up eventually in a large enough codebase, good intentions aren't going to keep it from happening. You need automated tools and guardrails for things. And those start with things like static types and even type hints in the more dynamic languages.
But the people that rebel against that basically say, "that slows me down doing that". There's something to that I get that I've written, I've cobbled things together in a notebook. I'm like, "Wow, this is great that it just happened," but yeah, that's kind of sketchy, but it's working fine. I don't care. It does come back to that value analysis where sometimes it's right to not care, but when you do care, if it's going to be something that's going to live for years and it's gonna have other people working on it and it's gonna be deployed to millions of people, then you want to use all of these tools you want to be told: "No, you've screwed up here, here and here." And that does require kind of an ego check about things where you have to be open to the fact that everything that you're doing is just littered with flaws.
++ on the ego point.
The reason memory corruption bugs are particularly bad is because the code execution machine can be manipulated into executing code outside of the behavioural intentions of the written code, completely through precise overwriting of memory addresses and code within existing data structures in the buggy program, and when a program allows itself to be re-programmed at runtime like this, that generally leads to very bad security problems, especially when said program can be re-programmed by inputs sourced from over a network.
The root cause is that memory lifetimes and shared resource accesses are just hard to reason about in complex software projects that don't employ radical memory management techniques or other fixes like GC. Even relatively simple software projects suffer from the curse of expectation vs implemented reality + changing requirements, constraints, expectations, and adjacent code.
Rust is exceptional because it eliminates the class of bugs that is the worst offender regarding software security, while allowing programmers to still operate at the level that C can operate at, and as a bonus it is possible to easily express high level concepts in it, which get compiled down to tight and optimised machine code. where C++ equivalents are clunky (iterators, lambdas, smart pointers) or are inconsistent, or optional. So understandably, the hype from the people who actually use it is natural because it is genuinely a technical improvement to. Online it's a political weapon, and the 1-dimensional troon psyop has convinced tech chuds that it's actually useless and shit and just git gud at programming C++ like a real programmer, when even the best programmers in the world agree that it's an impossible task because of the fundamental design of said "based and redpilled" programming languages.
*unless you employ radical memory management techniques such as strict arena allocation, where the lifetimes and bounds of allocations are specifically made stupidly easy to reason about through fundamental restructuring of code to what is traditionally taught and/or learned in the classic ad-hoc fashion.
it's the hot new language that's going to solve all the problems in computing caused by those stinky old languages nobody likes, ever since they stopped being the hot new language
Except rust actually is solving the problem of memory corruption bugs caused by C and C++, and I can't help but admit the programming language imperialism is kind of based for a troon op.
Maybe I'm retarded, but I'm 100% sure he's talking about the Rust lobby, not Rust. The argument for Rust's existence is pretty clear, even if the execution is naff. Faggots lobbying for it to the government doesn't make a lick of sense considering it's not even standardized yet.
Rust standard just dropped, it's official:
https://rust-lang.github.io/rust-project-goals/2025h1/spec-fls-publish.html
I’m in early stage of a (real) engineering career and I’ve been learning C++ to fulfil a childhood aspiration. It seems like something I wouldn’t hate working in, so wondering in idle curiosity if it’s (financially) worth the hassle of trying to switch considering I don’t have a relevant degree or experience and the job market seems to have changed with all the Indians + AI.
If your existing career path is already paying well, going into programming generally won't be worth it. If you can find a niche combo with your existing career path and programming, there could be good earning potential since most programmers are not experts in programming AND something else. Like, if you're a physicist and you become an expert at C++ programming (doesn't require a degree), you're gonna be in front of all the fools with CS degrees if you apply to be a programmer in the aerospace industry. Same shit in biomed, engineering etc, you automatically beat the CSfags because your skills are simply worth more than theirs, all you need is proof that you have programming chops and that you can operate version control software without too much training. Good luck, null's broken penis.
idk dude, sounds like you have a serious vril issue to me
Name one programing language specific package manager that is not dogshit.
Cargo
Here's the two best package managers that work with any language:
1. git clone
2. wget + unzip
Take the vendoring pill.
Cargo supports these. --git and --path flags for cargo add. Yw.
Solved problem:
https://github.com/crev-dev/cargo-crev + SBOM
Sorry zhang/vlad, you're fired because your refusal to use rust makes you and your work a national security threat. You are being replaced by a zoomer rust programmer and your accidental backdoors are being patched out in the rust rewrite.
