News for hackers. Stuff that matters.

A comment on Lessons from migrating a large codebase to React 16. Parent comment

Re:Lessons from migrating a large codebase to React 16 by weego on Tuesday November 07, 2017 @05:37AM (#15642286)
It's also incredibly frustrating that every step that is rediscovered that other languages just have is then subject to endless fragmentation over trivial differences that are put forward as core philosophical concerns. I know this is not unique to the JS ecosystem but it's definitely a lot worse than I've seen in the past.
[ Parent | on HN ]
Re:Lessons from migrating a large codebase to React 16 by bromuro on Tuesday November 07, 2017 @07:48AM (#15642891)
Which past are you talking about? Before the last years progresses, to make your javascript working on multiple browser your only choice was to lock you learning huge frameworks and toolkits like jquery and dojo, or spend hours during your weekends to get a project working on multiple platforms.

Those times were painful, now it’s much much better.

[ Parent | on HN ]
Re:Lessons from migrating a large codebase to React 16 by skeeterbug on Tuesday November 07, 2017 @09:50AM (#15643770)
Yeah, I don't think these people worked on code that targeted IE6-8. Horrible times.
[ Parent | on HN ]
Re:Lessons from migrating a large codebase to React 16 by weego on Tuesday November 07, 2017 @11:28AM (#15644727)
I've been writing production JavaScript since 1999. Writing compatible JS used to be a horrible pain, now everything about writing and maintaining your JS is the pain and browsers by comparison are highly forgiving.
[ Parent | on HN ]
Re:Lessons from migrating a large codebase to React 16 by chairmanwow on Thursday November 09, 2017 @07:44AM (#15661904)
Thanks for sharing! This is a viewpoint that I've never encountered before as only having entered the game in the last 3 years.
[ Parent | on HN ]
Re:Lessons from migrating a large codebase to React 16 by weego on Tuesday November 07, 2017 @11:30AM (#15644744)
I'm talking more ecosystem than core language changes. Though of course, core language changes are part of the build and tooling ecosystem because of everyone constantly wanting to write code that is years ahead of what browsers are actually supporting. Build and package management tooling, frameworks etc.
[ Parent | on HN ]