Comment by qsort

Comment by qsort 2 days ago

6 replies

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.

      • shakna a day ago

        Ok, lets reword that. JS has breaking changes in browsers or node at least once a year.

        If the platform can continuously shift, in an ecosystem that rots faster than my veggie garden, can we not have more sensible systems in place?