Solutions? Where we're going, we don't need solutions.

Every programming language has it's place.

JavaScript's place is in hell.

Latex: Problem --> \def\please@#1#2#3#4{\e@kill#2#3{\me#1}#4@now} -->

PHP: Problem -> real_solution_for_real_this_time() (real_solution_i_swear() is unsafe and deprecated)

missing 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"

Perl:

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.

C: "Segmentation fault."

Where?

C: 🤷🏻

python is like that. someone waay smarter than you have already done this 10 years ago.

C# Solution -> .sln

(brought to you by .net gang)

OK rust made me laugh

C --> segfault --> new problem

The line between problem and solution for C should be 30 miles long.

i feel like javascript could also be

Problem -> solution -> 3 days pass -> all dependencies had breaking changes made -> problem

Python 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')

for the ones missing the marvelous HTML, I gotchu bro:

<problem />

Actual C: Problem → Segmentation fault

Didn't see any mention yet, so... Useless use of cat!

C:

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)) )

It'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.

JS is basically the Hydra from the Greek Mythology.

Though PHP is literally the problem had me lol.

Java:

Problem -> NullPointerException.

python -> Import solver (C) -> Solution

If you're catting a file into a grep, you can go.

Someone do java hahaha

Racket: problem - > #lang solution

PHP -> 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.

I 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

Language — person doesn’t know how to properly code in that language — problem.

Permanently Deleted

Should have been grep or awk or sed in shell.

C could just be a blank and you have to bit blit the arrow on yourself.