Solutions? Where we're going, we don't need solutions.
Solutions? Where we're going, we don't need solutions.
Please dont take this seriously guys its just a dumb meme I haven't written a single line of code in half of these languages
Every programming language has it's place.
JavaScript's place is in hell.
140ReplyLatex: Problem -->
\def\please@#1#2#3#4{\e@kill#2#3{\me#1}#4@now}
--> 113ReplyPHP: Problem ->
real_solution_for_real_this_time()
(real_solution_i_swear()
is unsafe and deprecated) 109Replymissing the stage of C where it's all incomprehensible bitfucking with comments like "this works, i do not know why it works, do not touch this"
105ReplyPerl:
Problem -> $ @ % <=> <> =()= => ; qw() ])} select(undef, undef, undef, 0.25) =~ tr/.?\w\sREg3xfr0mhe|l/foo/g; $|++ &homebrewedFunction(%$ref, $_ , @_ ) -> solution
Source: I mainly code in perl. I like it, but I'll be the first to admit that it's not a beautiful language.
I was about to make an entry for lisp here, but I don't have enough parentheses to draw the path to the solution.
92ReplyC: "Segmentation fault."
Where?
C: 🤷🏻
87Reply 75Replypython is like that. someone waay smarter than you have already done this 10 years ago.
63ReplyC# Solution -> .sln
(brought to you by .net gang)
60ReplyOK rust made me laugh
59ReplyC --> segfault --> new problem
52ReplyThe line between problem and solution for C should be 30 miles long.
51Replyi feel like javascript could also be
Problem -> solution -> 3 days pass -> all dependencies had breaking changes made -> problem
48ReplyPython one is accurate. Most of our problems are solved by importing a library and writing the line, librarySolver.importedFunction.SolveMyProblem()
def main(): Print('thanks librarySolver')
42Replyfor the ones missing the marvelous HTML, I gotchu bro:
<problem />
40ReplyActual C: Problem → Segmentation fault
36ReplyDidn't see any mention yet, so... Useless use of
cat
! 29ReplyC:
Problem
→return Solution;
C++:
Problem
→const [auto]&& (Problem&& problem) noexcept(noexcept( Solution<Problem>{}(std::forward<Problem>(problem)) )) { return Solution<Problem>{}(std::forward<Problem>(problem)); } -> decltype( Solution<Problem>{}(std::forward<Problem>(problem)) )
24ReplyIt's ironic that the illustration for JavaScript is probably the most realistic and best solution IRL. In the sense that a lot of what problem solving is (which is a big part of software engineer) is breaking a big problem into smaller problems. And you continue doing this until each problem is solvable in a short period of time.
JavaScript sucks though as a language.
20ReplyJS is basically the Hydra from the Greek Mythology.
Though PHP is literally the problem had me lol.
19ReplyJava:
Problem -> NullPointerException.
17Replypython -> Import solver (C) -> Solution
11ReplyIf you're catting a file into a grep, you can go.
10ReplySomeone do java hahaha
8ReplyRacket: problem - > #lang solution
6ReplyPHP -> Problem -> Replace the developer -> Solution.
Yes PHP was bad in 5.x, in 8.x if things go bad it's just the developer who's bad.
6ReplyI never understood this logic:
“I know nothing about this subject, I’m gonna post a meme (a funny graphic usually about a specific topic, this one outlining the differences between languages) but I know nothing about the subject and will ask that nobody correct me or try to apply rationale here because I choose to be ignorant and have no interest in expanding my knowledge of the world and people around me, I just want people to tell me I’m funny and give me internet points”
To each their own ig
5ReplyPermanently Deleted
4ReplyLanguage — person doesn’t know how to properly code in that language — problem.
4ReplyShould have been grep or awk or sed in shell.
3ReplyC could just be a blank and you have to bit blit the arrow on yourself.
2Reply