5 ms·
I also wanted to make an additional comment expressing my frustration with the consistently negative comments on posts like this about JS Frameworks. These com
by lsalvatore 8y ago
I also wanted to make an additional comment expressing my frustration with the consistently negative comments on posts like this about JS Frameworks.
These commenters, those who see React as "just another JS Framework" and whom see JavaScript developers as people who would change JS Frameworks as if they were ordering a new drink at Starbucks: These people are the epitome of amateur.
Building web apps has been my career for nearly a decade. If you think entire teams would just up and switch to a new JS framework tomorrow because of a Medium article, or because of Github stars, you don't understand how the industry works at all.
React is not a fashion statement, it's an evolved paradigm shift in the web. Vue is not, it looks like Angular and Handlebars, the way apps were built 5 years ago, it adds nothing to the industry but more bloat and distracting people from using React.
- mythrwy 8y agoThus spoke the priest of the inquisition confronting heretics distracting from the one true way:) I personally had a lot of trouble with React, I didn't care for it, it was too foreign, too invasive. Vue on the other hand just clicked nicely and appeared a thing of simplicity and beauty. But admittedly I'm a wanton sinner. Who also don't care for Facebook products no matter how great and open and popular they are.
- lsalvatore 8y agoReact was created by Jordan Walke, a software engineer at Facebook. Facebook had a good reputation at the time, and so we forgive Jordan's divine genius for that slight error in career choice.
- brightball 8y agoPersonally, I view it as a case of right-tool-for-the-job vs the-one-true-way. The core of the matter boils down to one thing...everything on the web doesn't need to be an SPA because most things are open, check, close experiences. For the things that don't need to be an SPA, where a server side app serving HTML is a significantly faster user experience and dropping in a small bit of JS here and there is the right approach...Vue makes sense. This is the same place that jQuery makes sense because it makes the goal simple. For the places where you do need an SPA because the user is going to be opening your site/app and working within it for a while...absolutely...use React. If that's going to translate to a native application, even more so...use React. The concern is that Single Page Apps with React are gaining the hammer-and-everything-is-a-nail experience...when really only a few things are nails and most things are actually screws. Just pick the right tool for the job without all of the zealotry, like suggesting anything that is not react distracts people from using react.
- tomc1985 8y agoIt's grand pronouncements like that that epitomize amateurishness. I am so sick of seeing people complain about how things are being X years ago, as if old techniques somehow magically become invalid. Maybe they seem so bad because the practitioner sucked at that time. React doesn't really respect separation of concerns, and it's rare to find an SPA (and now, desktop apps -- thanks Electron!) that isn't complete garbage. Disciplined approach with battle-tested techniques creates much higher-quality software, every time. Also, "paradigm shift" is nonsense. The web is a platform -- fetishizing specific tools and techniques is foolish. There are many ways to skin a cat.
- lsalvatore 8y agoYou're right! I'm sure there's plenty of high-grade apps still out there that are built on jQuery plugin spaghetti code. No problem with that at all. No reason to criticize that either in any way shape or form. jQuery spaghetti is still a perfectly delicious way to enjoy a web app. Who doesn't love spaghetti?
- tomc1985 8y agoDude if your jQuery is spaghetti that's on you