Comment by Izkata

Comment by Izkata 2 days ago

15 replies

First, [] + {} isn't an object, it's a string.

Second, {} + [] isn't a type conversion issue, it's a parsing issue. That {} isn't an object, it's a code block. Assign {} to a variable to ensure it's an object, then do var + [] and you get the same result as the first one.

When using an actual object in both of these, the type conversion makes sense: "+" acts on primitives like strings and numbers, so it has to convert them first. You're getting obj.toString() + array.toString() in either case.

I'll admit the parsing issue here is odd, but most of the time peoples' complaints about javascript type coercion is that they simply never bothered to learn how it works.

otterley 2 days ago

One can know the intricacies of how something works and still possess a valid opinion that it doesn't work all that well or defies common sense and expectations.

  • th0ma5 2 days ago

    For me the difference is that you wouldn't then feel compelled to cynically bemoan it for retweets but this schtick went on for years where people would do something out of spec and then complain it was really bizarre to me! Anyway ... Being discouraged by a bug is fine... Making everyone else laugh at the machine on your behalf seems to against understanding and knowledge even if it is fun and funny haha

    • dcow a day ago

      It’s absurd. Comedy is cognitive dissonance manifest. It can’t not be funny.

      • th0ma5 a day ago

        I don't have dissonance. The language has the features that were designed or there is a bug in what they intended and I don't know why you think adding two empty objects together should make sense anyway. That it doesn't work resolves the dissonance.

qsort 2 days ago

The complaint is that type coercion exists at all. It solves no problems and creates several out of thin air.

Or are you arguing that ceteris paribus you'd rather not have the language throw an error or just propagate undefined?

  • th0ma5 2 days ago

    In the context of the time it was created it was fine to mess with and having an enlightened view from the future can't negate that even though I understand the complaint.

    • shakna 2 days ago

      JS has had how many breaking changes since then...? They've transitioned to the future.

      Why is it still here today?

      • josephg a day ago

        > JS has had how many breaking changes since then...?

        What breaking changes has JS ever had? Its an incredibly stable language.

twelve40 2 days ago

> peoples' complaints about javascript type coercion is that they simply never bothered to learn how it works

soo.... if the pesky people keep complaining, maybe it really doesn't make any sense? i for the life of me could never figure out why a bunch of mainstream languages a couple of decades ago decided that typing is no longer necessary and should be abolished. Is there any benefit of removing type checking (and relying on bizarre implicit coercion rules when ambiguity ensues)?

dcow a day ago

You will never bother me to learn something as convoluted as {} being sometimes parsed as an object and sometimes as a code block.

[removed] a day ago
[deleted]
th0ma5 2 days ago

Thanks for posting this. People still don't seem to get that there's no mystery out to make their life difficult and that unfortunately everything can probably ultimately be understood in a deterministic system.