363 karma · joined December 28, 2009
If someone were to make you an offer to build a complex web app right now using current tooling vs traveling back in time to 2010 and building it using 2010 tooling, would you actually choose to go back to 2010?
I would also argue that in the front end world frameworks have vastly improved code quality and developer experience. 10 years ago every team had their own homegrown build system, there were no libraries for type checking, you had write code or conditionals for the lowest version browser you support. Oh and app structure? Every team did something different.
Compare that to now: We have a handful of large open source build systems, so if you jump teams/projects there is consistency. We have things like TypeScript and Flow. We have Babel, which can transpile modern JavaScript in to older versions of the language, so you can support older browsers without even thinking about it. Finally, we have frameworks like React and Vue, which enforce a component based architecture. This is great because you can jump between different projects and for the most part will find code organized in the same way. All of this is amazing.
I also have this added bug where sometimes (once every 6 months or so) the Sync system gets stuck on when I turn off my car and open the door. The screen goes off and the radio keeps playing. Only way to resolve it is to disconnect the battery.
This is false. I've been developing with React for over a year and a half and have never used the React dev tools. I've only ever used the browser's web inspector and it's fine. We don't write CSS in JS, so this could play in to that, but when we were evaluating those solutions it wasn't impossible to figure out what was going on, even if you had hashes for class names.