Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implicit type coercion (as per 3.B.everything) #192

Open
bmarkovic opened this issue Jul 7, 2015 · 0 comments
Open

Implicit type coercion (as per 3.B.everything) #192

bmarkovic opened this issue Jul 7, 2015 · 0 comments

Comments

@bmarkovic
Copy link

I might be a newbie, but I am pretty amazed that this amount (and "cleverness" level) of implicit type coercion is considered good style in JavaScript. Given how String(), Number(), Boolean() and whatnot are much more readable, I'd suggest that these would be the preferred style to implicit coercion of the +variable type, primarily for readability reasons, as I'm not really that versed into side-effects of either of the two coercion approaches.

I do understand there are performance implications, so I'd understand if these were advised as performance hacks for code where profiling has shown critical perfomance issues.

However, if brief history of software teaches us anything it's that only speed that really matters in the end is the speed that the development team moves toward a product that finally has paying customers. Make it work, make it pretty, make it fast, wasn't it something like that?

I'm not trying to start a flame (my ninja level is certainly not in the ballpark) but I am curious if there are real reasons behind these choices that are not known to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant