3 ms·

> Will JavaScript take over front-end? Has it not? A more appropriate question would be "When will it step down?" > it takes 40% more development time to fini

> Will JavaScript take over front-end? Has it not? A more appropriate question would be "When will it step down?" > it takes 40% more development time to finish a project with AngularJS than without using it. And by "without using it", does it mean you write in vanilla JS? I believe you jumped into conclusions way too early. Working with any technology will take long. It's not the actual writing of code that will take long, it's the learning (if you're a total noob), setting up (if you don't have scaffolding tools), and debugging (if you don't have tools). The actual work is just a fraction of what you're actually doing. > How was your experience with React or any other If you mean React alone, then it's like Angular with directives... alone. You'll have to debate on your router, your data flow library, your server-communication layer, your build tooling, your process. It's all the same thing under the guise of a different syntax. > Should I invest more time to keep me updated with one of them? Get to know all the libraries, but never try to use them all. Choose one and get things done. > I still think, front-end should just present the information, not the whole application logic. It's like saying JS should have stayed on the browser, but wait! There's Node.js (server), Espruino (hardware), FirefoxOS (OS), PhoneGap (mobile), NW.js (desktop). If everyone was thinking the way you do, these would have never been invented.

whizzkid 11y ago
Thanks for your feedback, and I partly agree with you. > It's like saying JS should have stayed on the browser What I meant was, we don't need to re-implement the application logic in browser. Take an example of translation strings. You store them in your back-office and download the key-values to your browser and store them again so that you can parse it with Angular. I am not against JavaScript, in fact I love that we can use it on server level, build mobile applications and etc. Maybe I could be more accurate on the title.

whizzkid 11y ago

Thanks for your feedback, and I partly agree with you. > It's like saying JS should have stayed on the browser What I meant was, we don't need to re-implement the application logic in browser. Take an example of translation strings. You store them in your back-office and download the key-values to your browser and store them again so that you can parse it with Angular. I am not against JavaScript, in fact I love that we can use it on server level, build mobile applications and etc. Maybe I could be more accurate on the title.