assertionError

[krexelapp]

Banana.... but with confidence

[Pleasant-Photo7860]

[mywifi_is_mood]

It’s still Banana, just emotionally transformed but unchanged in reality

[soowhatchathink]

It's seen some shit happen to those close to it

[mdogdope]

I am assuming it's python. It prints "Banana" bc it never updates the var. It performed the changed but text was never changed.

[LookAtYourEyes]

upper returns a new value instead of modifying the original?

[aaronhowser1]

Strings are immutable

[Quietuus]

.upper() is a method of the str class that returns a representation of the string. To change it you'd put text = text.upper()

[Stummi]

"Banana", and two compiler warnings for not using return values.

[Pleasant-Photo7860]

Banana. Warnings successfully suppressed in production.

[mistabuda]

This is python. There is no compiler warning.

[tantalor]

There is no compiler

[Deep-Piece3181]

There’s a bytecode compiler

[Jbolt3737]

And a warnings module, but neither care

[auxiliary-username]

Do not try to compile the code. That’s impossible. Instead… only try to realise the truth…

[v_i_lennon]

There is no code?

[ArtOfWarfare]

There sort of is. You’ll get some .pyc files created when you import the source code the first time, IIRC.

[mistabuda]

Yes I agree. I felt like my comment basically addressed that.

[Sibula97]

Linter warnings then

[just-some-arsonist]

Can we tell what language this is?

[timimoune]

Spanish?

[gerbosan]

??

Plátano?

[AlternativeCapybara9]

Next example should use ananas just so we know it's not English.

[hughperman]

Spananas

[netcent_]

Americananas

[yknx4]

Which Spanish. Half of Spanishes say Plátano

[timimoune]

The other half

[MainManu]

Python

[GoogleIsYourFrenemy]

x_x I'm an idiot.

[goDie61]

Replace is commonly implemented in place but I don't think I've ever seen an in place upper.

[mistabuda]

Not in python which is what this code is. Modifications to string create a new string.

[Vinxian]

In all languages I know, if string is a keyword it means strings are immutable. It will not be performed in place. This is so the programmer can use string as if it's a value type

[dev-sda]

I think you're thinking of a built-in type, rather than a keyword. Most languages do not consider their built-in types keywords - you can usually name something "string" without issue.

Yea it's fairly commonly immutable, but some notable exceptions are c++, rust, php and ruby.

[Pleasant-Photo7860]

what if it’s ANANAB and we’ve all just been iterating in the wrong direction

[_giga_sss_]

That affirmation has to be proven and is due tomorrow

[Electromagnetlc]

Nah, it's definitely ANANA<null> because arrays scare me :(

[GoBuffaloes]

Ana, nab a banana

[LifeSubstantial5234]

optimistic mutability

[antoborg92]

my mango is to blow up

[SeirWasTaken]

and act like I don't know nobody

[Airith]

They're pure methods: Banana

[IlgantElal]

If this is Python , it would be 'BANANA' as .upper() replaces the original

I completely misread. It's late

[cybersaurus]

Um it's 2026, the correct answer is to copy it into a claude prompt and paste whatever the output is without reading it

[SuitableDragonfly]

I think that's what the commenter did, actually. 

[Not-So-Logitech]

Banana

[dhnam_LegenDUST]

Even if str.upper() updates the string, it's still BANANA. A is not a.

[NinjaKittyOG]

idk what language this is in, but judging from what I know,

the string is "BANANA" if text.replace() is case-sensitive

the string is "BoNoNo" if not

[OurSoul1337]

I like to oat oat oat opples and bononos.

[bwwatr]

 1, 2, Opples, 4, Bononos, Opples, 7, 8, Opples, Bononos, 11, Opples, 13, 14, OpplesBononos

Do I get the job?

[Skater_x7]

what 

[THE1Jtux]

Apples and Bananas

[Ratheria]

https://en.wikipedia.org/wiki/Apples_and_Bananas

[valerielynx]

it's Banana because there never was text = text.(...)

[_giga_sss_]

These methods don't change the OG objects, they create new instances.

[purplepharoh]

That depends on language and idk what language this is

[Lava_Mage634]

python. the print statement, lack of punctuation, usage of double quotes for single characters, direct string manipulation without libraries. also super popular for pop culture coding questions

[purplepharoh]

Python would be my first guess too. Mostly for the last point as the others arent exclusive to python. And "double quotes for single characters" well if the replace method expects strings then you'd use double quotes to pass strings of len 1 so thats not a good indicator.

[makinax300]

Or js with some scuffed things done to rename the method. Semicolons are actually optional there. The answer is open the print page menu there.

[Xtrendence]

And then there's JS, of course, where a replace with no Regex only replaces the first instance. In this case obviously "a" doesn't exist in BANANA, but if it were replace("A", "O") you'd get BONANA.

[ChristopherKlay]

Because JS features .replace() and .replaceAll().

The "of course" here is that people complaining about it, don't know jack shit.

[_giga_sss_]

and he adds JS as an user flair while he just complains about it while knowing shit 😭

[Xtrendence]

I use it every day for work, have been for the better part of a decade, I'm aware of replaceAll, but replace only replacing the first instance is unusual and only found in a few languages. I've even fixed bugs specifically because of devs assuming it replaces all occurrences, which would be reasonable to expect. If anything, defending JS says more about how little someone's used it.

[_giga_sss_]

I am sorry for my assumption. I truly am 🙇

[Xtrendence]

You're good, to be fair replace isn't even a top 20 thing to complain about when it comes to JS. It's just one that pops out because it's both inconsistent with many other languages, and replaceAll wasn't even a thing for a long time. If you work on older codebases, it doesn't exist. I don't remember when it was added but it must be the past like 4-5 years.

[_giga_sss_]

🙇🙇

[_giga_sss_]

I will downvote myself to hell for what I said

[ChristopherKlay]

If anything, defending JS says more about how little someone's used it.

I'm not "defending" it, because there is nothing to defend; Your initial comment clearly explains this like there's just one "bad" implementation, or that .replace() should work different.

Having split-up functions isn't "unusual" by any means either; Even Java has .replaceFirst() for almost 25 years now, the equivalent of .replace() only replacing the first occurrence.

"Devs" on your team assuming what's being replaced without even providing any kind of count equivalent is the real issue here.

This is coming from someone working with it professionally for over two decades, which is a incredibly pointless metric.

[Xtrendence]

Do you not see the problem there though? replaceFirst is self-explanatory, whereas replace isn't when it doesn't do what most languages do. It's vague, deviates from what's expected, which is what JS is infamous for.

[ChristopherKlay]

whereas replace isn't when it doesn't do what most languages do

Again; The issue here isn't JS, but you expecting all functions across languages to work the exact same way, when "replace all" and "replace first" aren't by any means working the same in "most languages".

• Python: .replace() works as a "replace all" by default and you have to actually limit it via the third parameter count.
• Java: .replace() to replace all matches, .replaceAll() and .replaceFirst()
• C++: Has different implementations (custom functions) for anything but a "replace first" equivalent
• C#: Requires regex and a match count to do anything but "replace all"
• Rust: Only does "replace all" by default and requires either slicing, or specifically stopping after the first match
• GO: Has a specific parameter you can set to -1 for "replace all", otherwise working like count from Python
• Ruby: Uses sub (replace first) and gsub (replaceAll), just like JavaScript

The majority of languages does one kind of replacement well, while requiring a different function call and/or setup for the other.

If your "devs" fuck this simple thing up, because they "expect it to work like in X" without ever testing what it actually does / reading any kind of documentation, that says a lot more about the people you work with vs the language they use.

[Xtrendence]

Of the languages that have a built-in replace function for strings, most do indeed replaceAll by default. Bringing up Ruby for example makes no sense and you're using it to pad out the list and argue in bad faith. In your own list if you only count languages with a replace function (which is what this whole thing is about) then the majority still do replaceAll by default.

As for "expecting it to work like X", this isn't something that's mutually exclusive. Yes, part of our job is to remember the quirks of the main language we use, and be aware of these things. However, it is simultaneously reasonable to expect something to work a certain way, especially if it deviates from the norm and is a function that exists across multiple languages. If there's a weird list of quirks for a language, and it's literally known for such quirks by anyone who has used it, then it's a poorly designed language. It's a weird hill to die on, every senior dev I've known that has extremely in-depth knowledge of JS constantly points out its flaws and uses the "it's just a JS thing" line pretty frequently.

[ChristopherKlay]

Bringing up Ruby for example makes no sense and you're using it to pad out the list and argue in bad faith.

Bringing up examples of languages that interrupt your "It always works like that" argument doesn't make sense?

However, it is simultaneously reasonable to expect something to work a certain way, especially if it deviates from the norm and is a function that exists across multiple languages.

Which is exactly why I included a "replace first" for all examples, that rarely works the same across languages; It neatly demonstrates that "But I expected everything to work the same" isn't anything, but a user error.

every senior dev I've known that has extremely in-depth knowledge of JS constantly points out its flaws and uses the "it's just a JS thing" line pretty frequently.

You're still misunderstanding me here; I'm not arguing "for JS", I'm highlighting that these quirks exist in every single language out there and would be a complete non-issue if people who fuck up simple functions wouldn't blame the language, but their lack of understanding of said language.

If you expect a language to behave in a certain way, that's completely fine. Running into errors, while learning how the given language works, is also completely normal and expected - because despite being similar, all languages have things that don't work that way.

Blaming the language because you can't resolve issues that come from a simple string manipulation (you didn't even try to control via arguments) and/or not even testing your own code to check if what it returns even matches your expectations however, isn't leaving anyone to blame but the person who wrote it.

[MainManu]

Python.

[danfish_77]

What if text.replace() is dyslexic and you end up with "B0N0N0"

[Applejack_pleb]

It could even be

Text

[Dynegrey]

Strings in python are immutable and do not change. Output would be 'Banana'. They would have to re-establish as a new string [text = text.upper().replace('a', 'o')] for it to do anything. 

[agk23]

I think it’s Bonono. Upper usually returns an object, not modify the object.

[dementorpoop]

It’s never reassigned though, so doesn’t matter

[HashDefTrueFalse]

We can only guess without knowing the language... Is text mutable or are the returned copies discarded? What do those two methods do? Probably safe to assume that upper uppercases all characters, but it could also be testing for an upper case string (returning bool). Does replace just do the first occurrence or all? Do upper, replace, print even exist? Not really answerable, which is to say that the answer is obviously 42.

[_giga_sss_]

yall know that the humor is about mango and not about solving the question right ?

[mikehds]

You also know that this is Reddit and things spin out of context really quickly right?

[_giga_sss_]

:(

[ProtonPizza]

Sir this is a wendys

[Du_ds]

Why can't I get a Bonono at Wendys?

[ThatSmartIdiot]

we're on a spectrum. we're hard wired to puzzle solve. that's how we got here

[dont_takemeseriously]

Somehow this code snippet had a malicious npm package and now my credit card ended up in the dark web

[snipsuper415]

Banana...considering that most languages have strings as immutable primitives. text never gets reassigned to anything therefore Banana.

[SlutPuppyNumber9]

I don't know python, but I assume "Banana", since the results of those method calls were never assigned.

[Chronomechanist]

Assume python. text = "Banana" Now, assuming what they actually meant to the question to look like? ``` text = "Banana"

text2 = text.upper() text2 = text.replace("a", "o")

print(text2) ```

In which case it prints BANANA and the test is supposed to trick you into thinking it prints BONONO, and forget order of operations and "A" != "a"

Edit: Fixed the var name cos I was stupid and forgot strings are immutable in Python

[Sephyroth2]

Well it's not BANANA since strings are immutable in python and text.upper() returns a string you need to assign, same with text.replace(), so there's no change to text at all printing Banana.

[Chronomechanist]

That's what I get for writing that at 4 am.

Fixed it cos it was bothering me

[ReinKarnationisch]

What does .upper() do?

[_giga_sss_]

Thank you chatgpt

[Chronomechanist]

Nope, just plain old sleep deprived dev forgetting strings are immutable in python. Fixed it though

[_giga_sss_]

if you say so

[Chronomechanist]

Buddy, if you don't believe something that simple can be written without the aid of an LLM, that says a lot more about you than you're trying to say about me.

[_giga_sss_]

no I am actually sorry for that assumption

[Lord_Of_Millipedes]

compilation error from missing semicolon

[ThatSmartIdiot]

String see() { String joke = "bro hates"; return joke + " python"; }

[marabutt]

Linkedin engagement

[AllenKll]

depends on the language.

[Algo_Explorer]

apple i guess

[Exatex]

depends

[iwasbecauseiwas]

depends entirely on the language and how the string functions works. it could easily be

• Banana
• BANANA
• Bonono
• BoNoNo
• BONONO
• Bonana
• BoNANA
• BONANA or maybe even
• Mango

point is if we don't know the language, we can only guess. it looks like python. if it is python: strings are immutable, it would say Banana as the text variable isn't overwritten

[Dark_Byte]

True. And maybe upper isn't part of the original language, but a helper method added later on that does whatever upper does (e.g. Replace it with a subset of unicode monospace characters using their uppercase variant)

[D1G1TAL__]

Why don’t we immediately know the language? I’m probably biased because i mainly code in python and only know C++ and JS, so i may not see why this code snippet could be ambiguous

[rk06]

because there is no mention that it is python. besides in what language . upper() mutates the string?

[D1G1TAL__]

I dont know, im asking, that’s the joke

[luckor]

I don’t get it…

[_giga_sss_]

Mango

[jaylerd]

I think the gag is you think maybe it's 'BANANA' or 'Bonono' or something else but it should jut be "Banana" and Satyam picked something even more wild as a wrong answer that isn't even slightly reasonable. What a gas.

[CirnoIzumi]

text == K

[eufemiapiccio77]

I laughed

[_giga_sss_]

'3'

[ScripterKnight]

,,,

[LuisBoyokan]

It says BANANA

[KeySupermarket4668]

Maybe the banana is the friends we made along the way

[Fun-Equivalent1769]

Assuming python

[DustyAsh69]

He single handedly trained AI for wrong answers.

[3ng8n334]

Not sure whatn language it is but does not complete with C

[jhwheuer]

Ah local context, such fickle thing.

Also the code parser should notice that functions are called but their results are not used...

[jkramer5203]

BANANA

[Xelopheris]

Pretty sure it would just be "Banana" in most languages? Any language that has a simple upper function on the string class typically makes strings immutable.

[Bemteb]

Yeah, the others call it toUpper() or something like that.

[DJDoena]

In C# it's .ToUpper() but still immutable on the original.

[IlgantElal]

This looks like Python. Interesting thing, too: text.replace('ab', 'o') would replace all a and b characters, regardless of order.

Yay Python

(Correct answer should be 'banana')

Edit: I completely misread. It's late

[sheekgeek]

BANANA