What is Inferno?
What is jQuery?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Inferno?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
I'm building a new process management tool. I decided to build with Rails as my backend, using Sidekiq for background jobs. I chose to work with these tools because I've worked with them before and know that they're able to get the job done. They may not be the sexiest tools, but they work and are reliable, which is what I was optimizing for. For data stores, I opted for PostgreSQL and Redis. Because I'm planning on offering dashboards, I wanted a SQL database instead of something like MongoDB that might work early on, but be difficult to use as soon as I want to facilitate aggregate queries.
I use jQuery because like other frameworks/libraries it handles significant amounts of boilerplate and heavy lifting compared to crafting your own UI tooling. Certainly more modern options such as Angular/Vue/React overcome some of the challenges in large jQuery based applications, but if you just need some straightforward DOM manipulation on a small scope, why not jQuery?
If jQuery or vanilla are the only two options available, then use the library that's available when its features will avoid having to reinvent wheels. Look at what jQuery offers, and look at the things you want to do. If a handmade solution doesn't require a lot of extra effort, then don't bother.
Most jQuery methods can be replaced with native code. I rather use a dedicated library for any exceptions. For example, axios.get is much better than $.get. Also, you can pick any number of animation libraries that are better than jQuery.
However, I don't mind using it in a team environment where communication & maintainability > code size. jQuery can help in those cases because most team members will know jQuery.
We are phasing out jQuery and jQuery UI in favour or Vue.js and @Vue-cli so we can support building a modern, well-architectured frontend.
I use Vue.js because I find the resulting code cleaner, more concise and easier to read.
However if you are looking for the broader community and wider corporate level adoption, go for react. Both work well and I have used both successfully. For me the preference for vue is a matter of personal taste with regards to code aesthetics.
I use Vue.js because it allows me to keep dev momentum. Vue includes many things out of the box that React doesn't include while remaining "lighter" than angular. For example: - Vue single file components include template, logic and styling out of the box. It also allows you to use language parsers such as Pug to write your component template and SCSS for styling. - Vue uses a simple Object to initialize an instance - Vue has support for transitions out of the box (say, for example, a fade in-out between component swaps, or adding an element to a list) - Vue has observers and two way binding like angular - Vue can conditionally render content in templates via template conditional tags
It really depends on your needs. Vue is most popular on Github but React has a huge demand in hiring (Mostly to convert existing angular or legacy applications to React). React is backed by Facebook and has more highly skilled contributors than Vue, though not to detract a single bit from Vue's own skilled contributors. If you're looking for developers, it's much easier to find seasoned react devs, at least as of Jul 2019. If you're a marketing or news agency that has deadlines, Vue's efficiencies may be the best, however, a large corporation may favour React since it has more support and is more of an "open slate" so to speak.
This is my stack in Application & Data
My Utilities Tools
Google Analytics Postman Elasticsearch
My Devops Tools
Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack
My Business Tools
I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?
I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.
It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.
Having developed in both Vue.js and React, I agree with your assessment of Vue. It does feel light and easier to understand and therefore learn. Seeing that Vue has some genetic roots with React, I would say start your friend out on Vue. If they need to learn React later, that should give them a good foundation. If you have a Pluralsight subscription, look for my course on Vue.js and feel free to use the demo project as a starting point.
I chose to use Vue.js a few years ago mainly for the easy learning curve. I have no experience with React, so I won't make any comparison here. Regarding available components, I never felt locked in because of Vue when looking for components. It happens that a component I wish to use is not available as a Vue component (and nobody published any Vue wrapper for it), but in such cases I was able to quickly hack a Vue wrapper component. In the end I don't think a decision to choose one framework over another should be made solely because of the number of components available. (And not all components in either framework is maintained, bug free, documented or easy to use)
I want to create a video sharing service like Youtube, which users can use to upload and watch videos. I prefer to use Vue.js for front-end. What do you suggest for the back-end? Node.js or Laravel ( PHP ) I need a good performance with high speed, and the most important thing is the ability to handle user's requests if the site's traffic increases. I want to create an algorithm that users who watch others videos earn points (randomly but in clear context) If you have anything else to improve, please let me know. For eg: If you prefer React to Vue.js. Thanks in advance
jQuery has been the basis of our front end JS for a number of years. The key part for us was that the amount of code saved by using jQuery methods, as opposed to writing out cross-browser compatible alternatives made it a no brainer. In recent years we've had to be clever in how we deliver jQuery on the websites, to ensure it's not render blocking and improve client-side performance but it's still a vital library.
In process of Learning Technics. Cross-browser Compatibility: handles a lot of infuriating cross-browser issues . used to make some widgets and effects: jQuery plugin repository.
jQuery allows to easily do DOM scripting (i.e. HTML elements manipulation and event handling). using jquery under MVC webapps. Studing to know more
We think VueJS is great. It's the main tool used to generate the client-side UI of our updated admin system, as well as being used in other smaller projects. The possibilities that VueJS brings to the table, means that we can quickly create rich and app-like interfaces and experiences.
jQuery is only used in small amounts, primarily for animations and UIs, but it is included in the WSC, so we felt like not including it here would be kind of cheating. jQuery also almost makes ajax-requests a pleasure to work with, so ... you got that point, jQuery.
Vue.js is my front-end framework of choice. It's light, fast, and extensible. Its simplicity and reactivity system make it an absolute pleasure to use and it has a wonderful, ever-growing community.
New and very popular. Less legacy to deal with compared to React. Great documentation. Easy to get started.