5 ms·
My only complaint is the global scope pollution with the top-level variables and lack of ‘var’ for those. But other than that, I agree.
by finaliteration 8y ago
My only complaint is the global scope pollution with the top-level variables and lack of ‘var’ for those. But other than that, I agree.
- etatoby 8y agoThat's a complaint about the JS language itself, that variables are global unless otherwise specified.
- finaliteration 8y agoI do agree it’s a complaint about the language. However, I think it does ultimately fall on the developer to know how to work with the language including the bad/ugly/awful parts. I also think not polluting the global scope is a pretty foundational thing to know or be aware of. It’s really easy to shoot yourself in the foot or have naming collisions/overwrites happen if you aren’t careful. Another example would be memory allocation/freeing in a non-GC language. Sure, it’s a pain that I have to deal with it, but it’s still on me to make sure my application works in the language I’ve chosen and doesn’t leak memory all over the place.
- deleted 8y ago[deleted]
- klyrs 8y ago> However, I think it does ultimately fall on the developer to know... This person has been programming for a week. I think we can let this slide
- nicoburns 8y agoFeedback is pretty useful for new programmers though. It's how they learn!
- ngcc_hk 8y agoGreat comment. Great comment.
- test1235 8y agoWell, no - not if everyone's raving on about how great the code is. Code quality is objective, not dependant on experience. I don't get to write crap code at my work if I'm inexperienced, I have to learn to write good code.
- finaliteration 8y agoI’m not at all saying they should be an expert after a week. But learning those things is part of being a software developer/programmer and I don’t think, “Well the language sucks” is a valid argument.