Alternatives to Riot logo

Alternatives to Riot

Mattermost, Discord, Slack, jQuery, and React are the most popular alternatives and competitors to Riot.
93
91
+ 1
68

What is Riot and what are its top alternatives?

Riot brings custom tags to all browsers. Think React + Polymer but with enjoyable syntax and a small learning curve.
Riot is a tool in the Javascript UI Libraries category of a tech stack.
Riot is an open source tool with 14.6K GitHub stars and 1K GitHub forks. Here’s a link to Riot's open source repository on GitHub

Top Alternatives to Riot

  • Mattermost

    Mattermost

    Mattermost is modern communication from behind your firewall.

  • Discord

    Discord

    Discord is a modern free voice & text chat app for groups of gamers. Our resilient Erlang backend running on the cloud has built in DDoS protection with automatic server failover. ...

  • Slack

    Slack

    Imagine all your team communication in one place, instantly searchable, available wherever you go. That’s Slack. All your messages. All your files. And everything from Twitter, Dropbox, Google Docs, Asana, Trello, GitHub and dozens of other services. All together. ...

  • jQuery

    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

  • React

    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • AngularJS

    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • Vue.js

    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

  • jQuery UI

    jQuery UI

    Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice. ...

Riot alternatives & related posts

Mattermost logo

Mattermost

412
501
275
Open-source, self-hosted, Slack alternative
412
501
+ 1
275
PROS OF MATTERMOST
  • 54
    Open source
  • 38
    On-premise deployment
  • 25
    Free
  • 22
    Built using golang
  • 19
    Fast and easy to use
  • 14
    Full text search
  • 13
    Docker image provided for easy setup
  • 12
    Built using react
  • 11
    Search and data archiving
  • 9
    Very professional
  • 9
    Supports multiple teams
  • 8
    Keeps us focused, effective, concise
  • 7
    Webhooks support
  • 6
    Integration with Gitlab
  • 6
    Clean and simple look
  • 5
    Well documented
  • 5
    Use #Hashtags like Twitter
  • 3
    Import Slack logs
  • 3
    Reactive community and ease of use
  • 2
    Self managed data
  • 1
    Easy webhook integration
  • 1
    On-premises Deployment
  • 1
    Secure
  • 1
    Slack-compatible integrations
  • 0
    On premise installation
CONS OF MATTERMOST
  • 1
    Not compatible with Telegram keys, which used by FSB
  • 1
    Basic permissions only in enterprise edition
  • 1
    Custom sidewide themes only in enterprise
  • 1
    Many basic features are enterprise only
  • 1
    Less integrations and plugins than slack

related Mattermost posts

Mark Nelissen

I use Slack because it offers the best experience, even on the free tier (which we're still using). As a comparison, I have had in depth experience with HipChat, Stride, Skype, Google Chat (the new service), Google Hangouts (the old service). For self hosted, Mattermost is open source and claims to support most Slack integrations, but I have not extensively investigated this claim.

See more
rishig
Head of Product at Zulip · | 5 upvotes · 133.2K views

I use Zulip instead of Slack, Mattermost, or RocketChat because of its first class threading. One week after switching to Gmail (in 2004) I realized I was never (willingly) going to use an unthreaded email product again. I had that same experience the first time I saw Zulip.

Zulip is also fully open-source, with a well-maintained (e.g. 90+% test coverage, fully static python), easily extensible code-base. In many companies, your communication platform (chat or email) is the center of the workplace -- no one asks for a chat integration into their calendar, they ask for a calendar integration into their chat. A fully open-source codebase means you can customize Zulip to your needs, and are never at the whim of a corporate maintainer who can't or won't fix simple bugs, or who will charge you tens of thousands of dollars for making minor customizations.

See more
Discord logo

Discord

1.2K
1.2K
825
All-in-one voice and text chat for gamers that’s free, secure, and works on both your desktop and phone
1.2K
1.2K
+ 1
825
PROS OF DISCORD
  • 59
    Unlimited Users
  • 56
    Unlimited Channels
  • 52
    Easy to use
  • 48
    Voice Chat
  • 48
    Fast and easy set-ups and connections
  • 44
    Clean UI
  • 42
    Mobile Friendly
  • 40
    Free
  • 32
    Android App
  • 27
    Mention system
  • 27
    Customizable notifications on per channel basis
  • 26
    Customizable ranks/permissions
  • 22
    Good code embedding
  • 22
    IOS app
  • 20
    Vast Webhook Support
  • 17
    Dark mode
  • 15
    Roles
  • 15
    Easy context switching between work and home
  • 13
    Great Customer Support
  • 13
    Bot control
  • 13
    Easy to develop for
  • 13
    Great Communities
  • 13
    Very Resource Friendly
  • 12
    Video call meeting
  • 12
    Video Call Conference
  • 12
    Robust
  • 11
    Sharing screen layer
  • 11
    Able to hold 99 people in one call
  • 10
    Easy Server Setup and joining system
  • 10
    Cool
  • 10
    Shares screen with other member
  • 10
    Great browser experience
  • 9
    Easy
  • 8
    Lower bandwidth requirements than competitors
  • 8
    Better than Zoom
  • 8
    Easy to code bots for
  • 5
    Noice
  • 5
    Everyone look at my con (it's a pro disguised as a con)
  • 4
    Not got wierd emojis like everything made by google
  • 3
    Easily set up custom emoji
CONS OF DISCORD
  • 9
    For gamers
  • 9
    Not as many integrations as Slack
  • 4
    Limited file size
  • 4
    For everyone
  • 4
    Discord is great, what are you talking about?
  • 3
    Sends data to US Gov
  • 2
    Are u mad u ever heard of DMs???
  • 1
    Suspected Pedophiles in few servers
  • 1
    What i mean by this is someone said u cant chat lol
  • 1
    Undescriptive in global ban reasons
  • 1
    Unsupportive Support
  • 0
    Zoom is WAY better bc you can't even chat on Discord

related Discord posts

Josh Dzielak
Co-Founder & CTO at Orbit · | 19 upvotes · 360.7K views

Shortly after I joined Algolia as a developer advocate, I knew I wanted to establish a place for the community to congregate and share their projects, questions and advice. There are a ton of platforms out there that can be used to host communities, and they tend to fall into two categories - real-time sync (like chat) and async (like forums). Because the community was already large, I felt that a chat platform like Discord or Gitter might be overwhelming and opted for a forum-like solution instead (which would also create content that's searchable from Google).

I looked at paid, closed-source options like AnswerHub and ForumBee and old-school solutions like phpBB and vBulletin, but none seemed to offer the power, flexibility and developer-friendliness of Discourse. Discourse is open source, written in Rails with Ember.js on the front-end. That made me confident I could modify it to meet our exact needs. Discourse's own forum is very active which made me confident I could get help if I needed it.

It took about a month to get Discourse up-and-running and make authentication tied to algolia.com via the SSO plugin. Adding additional plugins for moderation or look-and-feel customization was fairly straightforward, and I even created a plugin to make the forum content searchable with Algolia. To stay on top of answering questions and moderation, we used the Discourse API to publish new messages into our Slack. All-in-all I would say we were happy with Discourse - the only caveat would be that it's very helpful to have technical knowledge as well as Rails knowledge in order to get the most out of it.

See more

From a StackShare Community member: “We’re about to start a chat group for our open source project (over 5K stars on GitHub) so we can let our community collaborate more closely. The obvious choice would be Slack (k8s and a ton of major projects use it), but we’ve seen Gitter (webpack uses it) for a lot of open source projects, Discord (Vue.js moved to them), and as of late I’m seeing Spectrum more and more often. Does anyone have experience with these or other alternatives? Is it even worth assessing all these options, or should we just go with Slack? Some things that are important to us: free, all the regular integrations (GitHub, Heroku, etc), mobile & desktop apps, and open source is of course a plus."

See more
Slack logo

Slack

88.1K
67.5K
6K
Bring all your communication together in one place
88.1K
67.5K
+ 1
6K
PROS OF SLACK
  • 1.2K
    Easy to integrate with
  • 877
    Excellent interface on multiple platforms
  • 848
    Free
  • 694
    Mobile friendly
  • 690
    People really enjoy using it
  • 330
    Great integrations
  • 315
    Flexible notification preferences
  • 197
    Unlimited users
  • 184
    Strong search and data archiving
  • 155
    Multi domain switching support
  • 81
    Easy to use
  • 40
    Beautiful
  • 27
    Hubot support
  • 22
    Unread/read control
  • 21
    Slackbot
  • 19
    Permalink for each messages
  • 17
    Text snippet with highlighting
  • 15
    Quote message easily
  • 14
    Per-room notification
  • 13
    Awesome integration support
  • 12
    IRC gateway
  • 12
    Star for each message / attached files
  • 11
    Good communication within a team
  • 11
    Dropbox Integration
  • 10
    Jira Integration
  • 10
    Slick, search is great
  • 9
    New Relic Integration
  • 8
    Asana Integration
  • 8
    Great communication tool
  • 8
    Combine All Services Quickly
  • 7
    XMPP gateway
  • 7
    Awesomeness
  • 7
    This tool understands developers
  • 7
    Google Drive Integration
  • 6
    Replaces email
  • 6
    Twitter Integration
  • 6
    BitBucket integration
  • 6
    Google Docs Integration
  • 5
    GREAT Customer Support / Quick Response to Feedback
  • 5
    Jenkins Integration
  • 5
    Guest and Restricted user control
  • 4
    Gathers all my communications in one place
  • 4
    GitHub integration
  • 4
    Excellent multi platform internal communication tool
  • 4
    Mention list view
  • 3
    Easy to start working with
  • 3
    Visual Studio Integration
  • 3
    Perfect implementation of chat + integrations
  • 3
    Easy
  • 3
    Easy to add a reaction
  • 3
    Clean UI
  • 3
    Timely while non intrusive
  • 3
    Great on-boarding
  • 3
    Threaded chat
  • 2
    Intuitive, easy to use, great integrations
  • 2
    Simplicity
  • 2
    Great interface
  • 2
    So much better than email
  • 2
    Great Channel Customization
  • 2
    Message Actions
  • 2
    Eases collaboration for geographically dispersed teams
  • 2
    It's basically an improved (although closed) IRC
  • 2
    Android app
  • 1
    Great API
  • 1
    Very customizable
  • 1
    API
  • 1
    Easy remote communication
  • 1
    Get less busy
  • 1
    Targetprocess integration
  • 1
    Better User Experience
  • 1
    Finally with terrible "threading"—I miss Flowdock
  • 1
    Archive Importing
  • 1
    Great Support Team
  • 1
    Complete with plenty of Electron BLOAT
  • 1
    Markdown
  • 1
    Multi work-space support
  • 1
    Flexible and Accessible
  • 1
    Travis CI integration
  • 1
    It's the coolest IM ever
  • 1
    I was 666 star :D
  • 1
    Community
  • 1
    Dev communication Made Easy
  • 1
    Integrates with just about everything
  • 0
    Easy to useL
  • 0
    Platforms
CONS OF SLACK
  • 12
    Can be distracting depending on how you use it
  • 6
    Requires some management for large teams
  • 5
    Limit messages history
  • 4
    Too expensive
  • 4
    You don't really own your messages
  • 3
    Too many notifications by default

related Slack posts

Lucas Litton
Founder & CEO at Macombey · | 24 upvotes · 122K views

Sentry has been essential to our development approach. Nobody likes errors or apps that crash. We use Sentry heavily during Node.js and React development. Our developers are able to see error reports, crashes, user's browsers, and more, all in one place. Sentry also seamlessly integrates with Asana, Slack, and GitHub.

See more
Yonas Beshawred

Using Screenhero via Slack was getting to be pretty horrible. Video and sound quality was often times pretty bad and worst of all the service just wasn't reliable. We all had high hopes when the acquisition went through but ultimately, the product just didn't live up to expectations. We ended up trying Zoom after I had heard about it from some friends at other companies. We noticed the video/sound quality was better, and more importantly it was super reliable. The Slack integration was awesome (just type /zoom and it starts a call)

You can schedule recurring calls which is helpful. There's a G Suite (Google Calendar) integration which lets you add a Zoom call (w/dial in info + link to web/mobile) with the click of a button.

Meeting recordings (video and audio) are really nice, you get recordings stored in the cloud on the higher tier plans. One of our engineers, Jerome, actually built a cool little Slack integration using the Slack API and Zoom API so that every time a recording is processed, a link gets posted to the "event-recordings" channel. The iOS app is great too!

#WebAndVideoConferencing #videochat

See more
jQuery logo

jQuery

168.4K
49.8K
6.5K
The Write Less, Do More, JavaScript Library.
168.4K
49.8K
+ 1
6.5K
PROS OF JQUERY
  • 1.3K
    Cross-browser
  • 957
    Dom manipulation
  • 805
    Power
  • 660
    Open source
  • 610
    Plugins
  • 457
    Easy
  • 395
    Popular
  • 350
    Feature-rich
  • 281
    Html5
  • 227
    Light weight
  • 91
    Simple
  • 84
    Great community
  • 79
    CSS3 Compliant
  • 69
    Mobile friendly
  • 67
    Fast
  • 43
    Intuitive
  • 42
    Swiss Army knife for webdev
  • 35
    Huge Community
  • 10
    Easy to learn
  • 3
    Clean code
  • 2
    Just awesome
  • 2
    Powerful
  • 2
    Nice
  • 2
    Because of Ajax request :)
  • 1
    Easy Setup
  • 1
    Open Source, Simple, Easy Setup
  • 1
    It Just Works
  • 1
    Improves productivity
  • 1
    Industry acceptance
  • 1
    Allows great manipulation of HTML and CSS
  • 1
    Used everywhere
  • 1
    Widely Used
  • 0
    Javascript
CONS OF JQUERY
  • 5
    Large size
  • 5
    Encourages DOM as primary data source
  • 4
    Sometimes inconsistent API
  • 2
    Live events is overly complex feature

related jQuery posts

Kir Shatrov
Engineering Lead at Shopify · | 20 upvotes · 561K views

The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

#FrameworksFullStack #Languages

See more
Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
React logo

React

113.3K
90.9K
3.8K
A JavaScript library for building user interfaces
113.3K
90.9K
+ 1
3.8K
PROS OF REACT
  • 760
    Components
  • 652
    Virtual dom
  • 563
    Performance
  • 486
    Simplicity
  • 436
    Composable
  • 175
    Data flow
  • 159
    Declarative
  • 124
    Isn't an mvc framework
  • 113
    Reactive updates
  • 111
    Explicit app state
  • 32
    JSX
  • 23
    Learn once, write everywhere
  • 19
    Uni-directional data flow
  • 16
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 10
    Great perfomance
  • 8
    Built by Facebook
  • 7
    Javascript
  • 5
    TypeScript support
  • 5
    Speed
  • 4
    Feels like the 90s
  • 4
    Scalable
  • 4
    Easy to start
  • 4
    Awesome
  • 3
    Fancy third party tools
  • 3
    Hooks
  • 3
    Functional
  • 3
    Server side views
  • 3
    Props
  • 2
    Rich ecosystem
  • 2
    Obama
  • 2
    Very gentle learning curve
  • 2
    Has functional components
  • 2
    Simple
  • 2
    Closer to standard JavaScript and HTML than others
  • 2
    Super easy
  • 2
    Has arrow functions
  • 2
    Strong Community
  • 2
    Great migration pathway for older systems
  • 2
    SSR
  • 2
    Fast evolving
  • 2
    Simple, easy to reason about and makes you productive
  • 2
    Excellent Documentation
  • 2
    Scales super well
  • 2
    Just the View of MVC
  • 2
    Server Side Rendering
  • 2
    Cross-platform
  • 1
    Fragments
  • 1
    Start simple
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Beautiful and Neat Component Management
  • 1
    Sdfsdfsdf
  • 1
    Allows creating single page applications
  • 1
    Split your UI into components with one true state
  • 1
    Sharable
CONS OF REACT
  • 35
    Requires discipline to keep architecture organized
  • 23
    No predefined way to structure your app
  • 21
    Need to be familiar with lots of third party packages
  • 8
    JSX
  • 7
    Not enterprise friendly
  • 4
    One-way binding only
  • 2
    State consistency with backend neglected
  • 2
    Bad Documentation

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.6M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Adebayo Akinlaja
Engineering Manager at Andela · | 26 upvotes · 780.9K views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more
AngularJS logo

AngularJS

45.4K
32.7K
5.2K
Superheroic JavaScript MVW Framework
45.4K
32.7K
+ 1
5.2K
PROS OF ANGULARJS
  • 887
    Quick to develop
  • 586
    Great mvc
  • 570
    Powerful
  • 521
    Restful
  • 503
    Backed by google
  • 348
    Two-way data binding
  • 343
    Javascript
  • 328
    Open source
  • 305
    Dependency injection
  • 197
    Readable
  • 75
    Fast
  • 64
    Directives
  • 63
    Great community
  • 56
    Free
  • 38
    Extend html vocabulary
  • 29
    Components
  • 26
    Easy to test
  • 24
    Easy to learn
  • 23
    Easy to templates
  • 23
    Great documentation
  • 21
    Easy to start
  • 17
    Light weight
  • 17
    Awesome
  • 14
    Angular 2.0
  • 14
    Javascript mvw framework
  • 13
    Efficient
  • 13
    Great extensions
  • 10
    Easy to prototype with
  • 8
    Coffeescript
  • 8
    High performance
  • 7
    Lots of community modules
  • 7
    Mvc
  • 7
    Two-way binding
  • 6
    Clean and keeps code readable
  • 6
    Easy to e2e
  • 5
    Easy for small applications
  • 5
    One of the best frameworks
  • 4
    Works great with jquery
  • 4
    Fast development
  • 2
    Hierarchical Data Structure
  • 2
    Community
  • 2
    The two-way Data Binding is awesome
  • 2
    Typescript
  • 2
    Dart
  • 2
    I do not touch DOM
  • 2
    Be a developer, not a plumber.
  • 2
    Declarative programming
  • 1
    Amazing community support
  • 1
    Readable code
  • 1
    Fkin awesome
  • 1
    Acoperișul
  • 1
    The powerful of binding, routing and controlling routes
  • 1
    Opinionated in the right areas
  • 1
    Supports api , easy development
  • 1
    Common Place
  • 1
    Great
  • 1
    Very very useful and fast framework for development
  • 1
    Linear learning curve
  • 1
    Scopes
  • 1
    Programming fun again
  • 0
    Acoperișul 0757604335
  • 0
    Httpș//Acoperișul 0757604335
  • 0
    Shvzjn
  • 0
    Oautho loc
  • 0
    Js
  • 0
    Angular js
  • 0
    Bot Ionescu
  • 0
    Google.com
CONS OF ANGULARJS
  • 10
    Complex
  • 3
    Dependency injection
  • 2
    Learning Curve
  • 2
    Event Listener Overload
  • 1
    Hard to learn

related AngularJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.1M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 20 upvotes · 798.5K views

Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

  • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
  • Vue Styleguidist as our style guide and pool of developed Vue.js components
  • Vuetify as Material Component Framework (for fast app development)
  • TypeScript as programming language
  • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
  • ESLint, TSLint and Prettier for coding style and code analyzes
  • Jest as testing framework
  • Google Fonts and Font Awesome for typography and icon toolkit
  • NativeScript-Vue for mobile development

The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

  • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
  • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
  • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
  • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
  • Large scaling. Vue.js can help to develop pretty large reusable templates.
  • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
See more
Vue.js logo

Vue.js

38.2K
30.2K
1.4K
A progressive framework for building user interfaces
38.2K
30.2K
+ 1
1.4K
PROS OF VUE.JS
  • 275
    Simple and easy to start with
  • 216
    Good documentation
  • 186
    Components
  • 123
    Simple the best
  • 95
    Simplified AngularJS
  • 81
    Reactive
  • 69
    Intuitive APIs
  • 48
    Javascript
  • 45
    Changed my front end coding life
  • 40
    Configuration is smooth
  • 28
    Easy to learn
  • 25
    So much fun to use
  • 20
    Progressive
  • 17
    Virtual dom
  • 13
    Faster than bulldogs on hot tarmac
  • 9
    It's magic
  • 8
    Best of Both Worlds
  • 8
    Component is template, javascript and style in one
  • 7
    Without misleading licenses
  • 7
    Perfomance
  • 7
    Application structure
  • 7
    Elegant design
  • 6
    Intuitive and easy to use
  • 5
    Light Weight
  • 4
    Easy to integrate to HTML by inline-templates
  • 4
    Good command line interface
  • 3
    Small learning curve
  • 3
    Like Angular only quicker to get started with
  • 3
    Customer Render ending eg to HTML
  • 2
    One-way data flow
  • 2
    Single file components
  • 2
    Intuitive
  • 2
    Lots of documentation
  • 2
    Component based
  • 2
    Bridge from Web Development to JS Development
  • 2
    Concise error messages
  • 2
    Logicless templates
  • 2
    Supports several template languages
  • 2
    High performance
  • 1
    GUI
CONS OF VUE.JS
  • 6
    Less Common Place
  • 3
    YXMLvsHTML Markup
  • 1
    Don't support fragments
  • 1
    Only support programatically multiple root nodes

related Vue.js posts

Johnny Bell
Shared insights
on
Vue.jsVue.jsReactReact

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.

See more
Shared insights
on
Vue.jsVue.jsReactReact

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?

See more
jQuery UI logo

jQuery UI

36.1K
9.5K
896
Curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library
36.1K
9.5K
+ 1
896
PROS OF JQUERY UI
  • 213
    Ui components
  • 155
    Cross-browser
  • 121
    Easy
  • 100
    It's jquery
  • 81
    Open source
  • 57
    Widgets
  • 48
    Plugins
  • 46
    Popular
  • 39
    Datepicker
  • 23
    Great community
  • 7
    DOM Manipulation
  • 6
    Themes
  • 0
    Some good ui components
CONS OF JQUERY UI
  • 1
    Does not contain charts or graphs

related jQuery UI posts

Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Khauth György
CTO at SalesAutopilot Kft. · | 12 upvotes · 382.8K views

I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

See more