guess the language! 

unnecessary indirection,
unnecessary allocation,
unnecessary bound checks,
runtime type information,
overuse of abstractions,
global state in libraries,
long names.
repeated half-assed reference counting,
repeated half-assed implementations of common data structures/algorithms,
tons of fragile platform specific code.

@clacke Hmmm... I though I would miss every garbage collected language with that one, but everyone (you and one other person) seems to offer Java up...

@namark Ah. Gotcha. 😀

Yeah, as far as I know there is no RC in Java. The rest just seemed so very closely targeted that I thought maybe I had missed something. 😀

Is it C++?

@clacke noooo, not my favorite language, plzzz!... but close =)

Follow

@clacke It probably deserves it, but not what I had in mind... only thing I know about it is that either function definition or function call syntax is terrible.

· · SubwayTooter · 1 · 0 · 0

@clacke Think of it this way: it's not that a bad programmer can do all of those things in that language, it's that a good programmer can't avoid any of those thing.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.