Null Coalescing vs Walrus Operator: One-Line Power
PHP's ?? operator vs Python's := walrus operator. Which language gives you more one-line superpowers? Mind = blown!
#php #python #phpvspython #nullcoalescing #walrusoperator #operators #oneliner #programmingcomparison #phptricks #pythontricks #codecomparison #syntaxcomparison #viralcoding
Optional Chaining vs Null Coalescing: Null Safety Battle
JavaScript's ?. operator vs PHP's ?? operator. Which language handles null/undefined more elegantly? This comparison is INSANE!
#javascript #php #javascriptvsphp #optionalchaining #nullcoalescing #nullsafety #programmingcomparison #codecomparison #javascripttricks #phptricks #syntaxcomparison #viralcoding
Null Coalescing vs Optional Chaining: Null Safety War
PHP's ?? operator vs JavaScript's ?. operator. Which language handles null/undefined more elegantly? This comparison is INSANE!
#php #javascript #phpvsjavascript #nullcoalescing #optionalchaining #nullsafety #programmingcomparison #codecomparison #phptricks #javascripttricks #syntaxcomparison #viralcoding
Optional Chaining ?. vs Null Coalescing ??: GAME CHANGER!
JavaScript's ?. operator vs PHP's ?? operator - which saves more lines of code? INSANE!
#javascript #php #jsvsphp #optionalchaining #nullcoalescing #nullsafeoperator #php8 #es2020 #viralcoding #modernjavascript #syntaxcomparison #mindblown
Null Coalescing: Python's 'or' GOTCHA vs PHP's ??
Python's 'or' operator has a TRAP! PHP's ?? is safer! See why 0 and empty string break Python's approach. Mind = BLOWN!
#python #php #pythonvsphp #nullcoalescing #defaultvalues #nullhandling #codecomparison #programmingcomparison #pythongotchas #phptricks #programmingdebate #codingtips #pythonoroperator #phpnullcoalescing #bestpractices
After thought (thought I didn’t plan to put into it), I don’t think "NULL coalescing" and "NULL chaining" needs to be built in to the #ProgrammingLanguage, and here’s why:
* If you’re getting just one thing, the getter can take an optional default result value. #Python works like this in `getattr`, `.get`, and things of that nature. Having an operator for this is fine, but it seems obvious you don’t **need** the language to do it for you.
* If you’re walking down a long uncertain chain, I have two arguments:
* Knowing the path that leads down into the object to the specific thing you want kinda sounds like an #Encapsulation violation. Why do you know so much about the internals of this object. If this deep property is important, maybe it’s part of the interface of the top-level thing. Maybe this is just bad design.
* Diving deeply involves lots of possibilities: possible defaults, actual methods of finding the named thing (allow inheritance? Is it an attribute? Is it an element of an array? Etc), did you want to just stop or raise an exception?Does saying what you want really come out to a simple, clean, understandable, one-line, expression?
Maybe I’m biased because I don’t have these operators in my day-to-day language; and also can’t remember hitting this situation. And I can certainly see such operators could be helpful. I’m not a language designer. But from my actual experience, in this case, the juice just isn’t worth the squeeze.
Turbo Learn PHP
JavaScriptBuzz
Python Peak
Wolf
TechKeysX