Someone explain the Rustacean failing to support MacOS.
Programmer Humor
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
ocaml and haskell and erlang power like... a shitton of industry production code. If erlang software disappeared, internet dies for a bit until people replace all the broken routers.
Isn't functional stuff closely related to type theory & type systems in all langs? In that sense, it's prevented whole classes of bugs from ever getting to prod in the first place.
Responsible for 0% of code in production
Best code is no code at all
Depends very much on the language you're using. Haskell and ocaml do fall into that category, whereas erlang and scheme are also functional languages with fairly weak typing.
If there is one thing that connects functional programming as a whole, it is that in FP, program flow is managed mostly through function application, instead of if statements and for/while loops.
Proud imperative stoneager here 🦍
Cavepeople together strong!
The OOP boilerplater is the only one with a job.
Imperative stonager works there too. You've just never seen him because he hasen't accepted a meeting invite is 14 years.
You've just never seen him because he hasen't accepted a meeting invite is 14 years.
And counting!
I've been shifting around, but never to the OOP boilerplater. I despise Java.
More like mix and match your path lmao.
Watches Computerphile, thinks it's actual programming
What is this even supposed to imply
Yeah, I'm kinda confused by that one too—Computerphile is CS theory, not software engineering.
I think, the point is Haskell is more CS theoretical than practical language and anyone who uses it (or any other FP) has never written a single line of production code (the last statement is even in the meme)
Personally, I love that series. I guess whoever made this meme thinks people who watch the show are trying to implement their code examples in production.
history | grep -E '(sed|grep|awk|perl)' | wc -l
107
Dang. That's out of 1000. I need to up my game. Also three of those seds are part of something with a -basedir and don't count.
So yeah, about 10% of my commands are iterating shell pipe things for poops and giggles, I guess.
... and this got me going down the rabbit hole of writing a filter for my history to pull out the first command on the line. This is non-trivial because of potential preceding variable assignments. Most used commands are currently apt and man and ls. I think apt is a Spiders Georg situation because the system is fairly fresh and I keep finding things that I haven't installed yet. Also I went through a patch of trying to parse its output.
... oh, er... unga bunga.
I just use nushell’s builtins instead of wrangling with IFS and bash idiosyncrasies. It's been years since I've corrupted data by parsing text wrong.
But even if someone doesn't want that: apart from using it in legacy scripts, grep is just a strictly less useful ripgrep these days, no?
$ history | grep -E '(sed|grep|awk|perl)' | wc -l
50
$ history | wc -l
500
Checks out perfectly.
Uses neovim with gruvbox theme on arch
Damn, why are you calling me out personally? Though I use it to write python scripts and LaTeX, not rust...
I feel like the author is a MacBook user.
Imperative stoneagers getting an old MacBook from somewhere and going "huh, I guess its UNIX" is probably true though

I was triggered at every panel, it's unacceptable!
I hope no one got left unoffended
The imperative stoneager feels like the most favored one, there are no real negatives listed there. All that’s listed are things they usually pride themselves on.
I don't belong to any of the above. Am I even a programmer at this point?
I belong to all of them. Same question.
Just finished an assignment for uni: Memory safety in Rust: Mechanisms and limits - a comparison to C/C++.
Fuck.
Great overview of Rust's weaknesses and strengths:
Li et al. 2024 Rust for Linux: Understanding the Security Impact of Rust in the Linux Kernel
OOP boilerplater except for the Windows bit; trying to slowly move off proprietary software and choose open source when I can
Jetbrains though :(
also a JetBrains enjoyer :( one day I'll teach myself to like VSCode as much as I like JetBrains
Hear me out:
Mixing OOP and functional code to abstract the shit out of everything making 5k loc in around 500 loc in java. You can do magic using this trick.
Yes, you can make money and electricity magically disappear !
Functional programming in Java is kind of an afterthought and it shows. That's one of the reasons why Scala was created!
I mean Yeah it is an afterthought in the Sense of that Java was Originally an oop Language but fp in Java was added on very sensibly imo. I use functional Programming in Java a Lot and try to make Everything immutable where I can and honestly coding like that feels clean and very practical.
Oh, I guess I'm a stoneager with a penchant for functional elitism then.
Though I will admit OOP is valid for involved data modelling, everything else should be functional though.
I've also trained myself out of most short variable names for maintainability reasons
Outside of the for loop counters i and j, short variable names are awful. Coming back to old code written with abr var nams is like talking to someone in the military who just constantly throws out jargon and acronyms that they know you don't know.
But so are Java style ObserverFactoryManagerTemplateMachinistTemplater names.
There's a sweet middle ground of short, but actually descriptive name. Sometimes it's not possible but that's usually a code organization / language / framework smell.
Too short variable names is usually a sign that you need to use a proper ide, with auto complete, or that you need to use a proper build process that will minify your code after the fact.
Too long names are usually a sign that your module of code (function, class, namespace, etc) is too large, or that your language/framework naming conventions are too strict, or the language doesn't encapsulate scope properly.
That's such a way to dismiss the theory and academia