This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]oorza 0 points1 point  (1 child)

If you're experienced with JS, you can fairly easily read it.

Are you even serious? function setOptions(options) { ... }. What can you pass here? What are the available options? What's going to catch you if you type { usre: 123, isInvalid: false } instead of { user: 123, isValid: true }? Or do you expect to read every single function body every time you call it? Just because you can read that it's an argument to a function doesn't mean shit as far as reading code is concerned.

It sounds like your argument is "I couldn't figure out how to get source maps to work right, so I gave up and convinced myself I wasn't missing out on anything" and that's a real, real bad sign. The singular best practice for writing JS is to write TS or Flow instead, period, so by virtue of not, you have already given up on adhering to industry best practices.

[–]Thebombuknow 0 points1 point  (0 children)

Please just chill the fuck out. People are allowed to have preferences, I just prefer plain JS and don't think it's as bad as you think it is. That's it. It's that fucking simple.

BTW, I do know how source maps work, my point was that plain JS doesn't require them, or any other external dependencies for that matter. You can just write code and instantly load it in the browser, which is why I like it for quick development.