To truly appreciate our languages, we must know their faults. So what's your pet peeves and biggest pains in you side about your favorite language you use everyday?
For further actions, you may consider blocking this person and/or reporting abuse
To truly appreciate our languages, we must know their faults. So what's your pet peeves and biggest pains in you side about your favorite language you use everyday?
For further actions, you may consider blocking this person and/or reporting abuse
Top comments (23)
In Python, if you write multiple strings adjacent to each other, Python concatenates them. For me, this often leads to annoying bugs like
Ouch! Haha yeah I can see how that hide it self well!
You can thank ISO C for that one:
Not that python directly inherits the behavior, but they probably decided to go with that behavior based on how C does it.
When you see that one article saying that "this language X is so dead!" and it makes you doubt your life choices.
In Java and Kotlin, I usually create literal arrays with each item on a new line and all columns lined up nicely. To add a new item, I can then just copy any line and change what I need. To edit all items at once I just add a carat at the beginning of each line and off I go.
EXCEPT FOR THE LAST LINE WHICH DOESN'T HAVE A COMMA.
For me I would say in ruby how easy it is for
nilto passed around which then causescan't do #x for niland then you're like, "why is it nil?" it's even worse when you getnilin weird strange places.In Ruby, the fact that the normally-named
filterfunction is namedselectorfind_allis really annoyingAnd oh gosh way too many methods for the objects that is insane. You can easilly cut it down to 2 times less because there is a lot of aliases too
Golang is one of my favorite languages and the thing I find the most frustrating is the lack of architecture standards.
Up until recently, it's been a wild west as far as package management and project setup. Where do you put your code? How do you structure your folders? What web frameworks are actually worth investing into?
Basically same issues Node had early on. It's getting MUCH better but I feel like it's still a problem.
I feel like you just dont need a framework in Go, also hasn't the location of where the code should go been in the documentation since release?
javascript "weak typing", not dynamic typing.
Golangs lack of enum support is easily the most annoying thing about the language for me.
Currently I have a ruby script that has an enum schema and it prints out golang code for each enum it has all of the constants, an array of all the values, and a function to test if a given object is one of the enum values.
That's easy: there are no types in JavaScript (and it will be like that for a long while).
Diphthongs!