You are obviously biased about all this, so why bother continuing the discussion.
Everyone is biased. The sentence you quoted is a fact - you can search it on your own.
We can't ignore that JavaScript is flawed. You just can't design a good language in 10 days, no matter how great your skills are or what tools you have at your disposal. I'm not saying we should ditch JS completely, just that we should be more objective. So no, it's not that I don't accept JS and don't move on - I'm working primarily in JS on my job, both on front-end and back-end, and that's why I think I have the right to discuss about these things.
Is JS better today? Yes, it's much better. And with TypeScript, it's possible to remove lot of baggage from your code base.
Tests are useful, but not most of the tests i see people that are like "did this page load? return true"....because that kinda test writing is an utterly useless waste of time.
All i know is, i work on my project until my code runs cross-browser and responsive and the logic is sound. Whether you write tests or not, the end result is what matters.
I don't know where you saw such tests but it's not proper testing. Whenever I'm working on a front-end code base I'm testing rendering of the components, not the whole pages (except if it's a purely static site with no framework at all). There is a reason we check for thing to be rendered - sometimes we may have some error in the component which can cause it to not be rendered on the page and that would seriously impact UX.
Whether you write tests or not, the end result is what matters.
Tests are not written for the sake of writing them. You write tests to ensure that your logic still works. Imagine that you're working on a huge website with bunch of different things happening all over the place. How would you ensure that everything still works as it should? You would always spend minutes and hours testing whole application again and again?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Everyone is biased. The sentence you quoted is a fact - you can search it on your own.
We can't ignore that JavaScript is flawed. You just can't design a good language in 10 days, no matter how great your skills are or what tools you have at your disposal. I'm not saying we should ditch JS completely, just that we should be more objective. So no, it's not that I don't accept JS and don't move on - I'm working primarily in JS on my job, both on front-end and back-end, and that's why I think I have the right to discuss about these things.
Is JS better today? Yes, it's much better. And with TypeScript, it's possible to remove lot of baggage from your code base.
I don't know where you saw such tests but it's not proper testing. Whenever I'm working on a front-end code base I'm testing rendering of the components, not the whole pages (except if it's a purely static site with no framework at all). There is a reason we check for thing to be rendered - sometimes we may have some error in the component which can cause it to not be rendered on the page and that would seriously impact UX.
Tests are not written for the sake of writing them. You write tests to ensure that your logic still works. Imagine that you're working on a huge website with bunch of different things happening all over the place. How would you ensure that everything still works as it should? You would always spend minutes and hours testing whole application again and again?