Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "language flaming"
-
I hate it when I try and have a discussion with another dev and the conversation devolves into something akin to:
Me: I'm doing a thing in y language! How do I do z using y language?
Dev: WHY ARE YOU USING Y LANGUAGE?! Y LANGUAGE SUCKS AND IF YOU USE IT YOU'RE STUPID. ALL REAL DEVS USE X LANGUAGE.
I just wanted to know how to do something. Maybe I don't want to do it in another language. Maybe I have to use this language for work/study. Maybe I've just been given legacy spaghetti code and can't change the system easily.
Why do people feel the need to do this? And if they want to flame a language why can't they do it constructively?
Dev: If you are trying to do a thing in y language, why don't you try using x language? It offers an easier way for you to complete the task that you want, and it has other amazing features too!
Then you could actually respond with the appropriate response which would be thanks but no thanks because of this reason or thanks i'll check it out.
No need to be so elitist all the time.3 -
I always find it funny when people fight over certain aspects of Javascript. Like how callback hell is manageable, async functions etc
Do they forget that Javascript itself is a flaming pile of shit language to begin with? The inventor literally created the language in a week, so that should be the base line assumption on how "capable" that language will come out to be.13 -
The joys of being a multi-project, multi-language developer! You think you'll juggle a couple of balls, but suddenly you're in a full-blown circus act, with chainsaws, flaming torches, and a monkey on your back yelling "more features!"
In the morning, you're all TypeScript: "Yes, of course, types make everything more reliable!" By lunch, you're neck-deep in Python and realize types are a vague suggestion at best, leaving you guessing like some bug-squashing mystic. And then just when you’ve finally wrapped your head around that context switch, FastAPI starts demanding things that make you wonder, "Why can’t we all just get along and be JavaScript?"
Oh, and don’t even get me started on syntax. One minute it’s req.body this and express.json() that. The next, Python’s just there with a smug look, saying, "Indentation is my thing, deal with it!" And don’t look now, because meanwhile, Stripe’s trying to barge in with a million webhooks, payment statuses, and event types like “connect” and “payment,” each a subtle bomb to blow up your error logs.
Of course, every language has its "elegant" way of handling errors—which, translated, means fifty shades of “Why isn’t this working?” in different flavors! But hey, at least the machines can’t see us crying through the screen.10