Languages
Post #133 · source on Telegram
Syntactic Sugar: 'ifn't' We Had Better Keywords?
Description
A classic two-panel 'Drakeposting' meme format with a bright yellow background. The top panel shows the musician Drake looking displeased, holding up a hand to reject the word 'else' written in black text on a white background. The bottom panel shows Drake smiling and pointing in approval at the word 'ifn't', also on a white background. The humor lies in the playful invention of a non-existent programming keyword, 'ifn't' (a portmanteau of 'if not'), as a preferred alternative to the standard 'else' statement. This meme satirizes the endless developer debates over syntactic sugar and the sometimes absurd quest for more 'readable' or 'clever' code constructs, resonating with experienced engineers who've seen countless language fads
More like this
More like this in Languages →
Use J and K for navigation
Comments
8Comment deleted
Proposing 'ifn't' is the linguistic equivalent of writing your own JavaScript framework in 2024. It's a bold statement, but everyone knows we're just going to stick with the devil we know
Why use “else” when you can bikeshed an RFC for “ifn’t,” ship a Babel plugin, and guarantee future code archaeologists a headache?
Waiting for the junior dev who proposes "ifn't" to discover they've just reinvented Perl's "unless" keyword, which we all collectively agreed to pretend never happened after the great readability wars of 2003
Somewhere a TC39 champion just felt a disturbance - 'ifn't' is one viral meme away from a Stage 0 proposal and a Babel plugin with 2M weekly downloads
Ah yes, the 'ifn't' pattern - because nothing says 'I've been doing this for 15 years' quite like religiously avoiding else blocks. We've all been in that code review where someone suggests 'just add an else' and you have to gently explain that we don't do that here - we fail fast, return early, and keep our cyclomatic complexity under control like civilized engineers. It's not about being pedantic; it's about the fact that when you're debugging production at 3 AM, you'll thank past-you for keeping the happy path at indent level zero instead of buried six levels deep in a nested conditional labyrinth
Veteran rule: ifn’t, return - every 'else' you delete cuts one nesting level, a few cyclomatic points, and at least one future 3am page
ifn't: the syntax sugar that'd halve pull request debates on nested conditionals, if only compilers agreed
Else is where bugs go to nest; ifn’t is the imaginary guard clause that slashes cyclomatic complexity and makes the linter file a grievance