Alternatives to Viber logo

Alternatives to Viber

WhatsApp, Skype, Telegram , Duo, and Zoom are the most popular alternatives and competitors to Viber.
18
19
+ 1
8

What is Viber and what are its top alternatives?

It is a cross-platform instant messaging and voice over IP application provided as freeware for the Microsoft Windows, macOS, Linux, Android and iOS platforms.
Viber is a tool in the Phone category of a tech stack.

Top Alternatives to Viber

  • WhatsApp
    WhatsApp

    It is a cross-platform mobile messaging app for iPhone, BlackBerry, Android, Windows Phone and Nokia. It allows users to send text messages and voice messages, make voice and video calls, and share images, documents, user locations, and other media. ...

  • Skype
    Skype

    Skype’s text, voice and video make it simple to share experiences with the people that matter to you, wherever they are. ...

  • Telegram
    Telegram

    Users can send messages and exchange photos, videos, stickers, audio and files of any type. It provides instant messaging, simple, fast, secure and synced across all your devices. ...

  • Duo
    Duo

    Duo is a next-generation package manager that blends the best ideas from Component, Browserify and Go to make organizing and writing front-end code quick and painless. ...

  • Zoom
    Zoom

    Zoom unifies cloud video conferencing, simple online meetings, and cross platform group chat into one easy-to-use platform. Our solution offers the best video, audio, and screen-sharing experience across Zoom Rooms, Windows, Mac, iOS, Android, and H.323/SIP room systems. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

Viber alternatives & related posts

WhatsApp logo

WhatsApp

408
403
17
A freeware, cross-platform messaging and Voice over IP service
408
403
+ 1
17
PROS OF WHATSAPP
  • 14
    Free
  • 3
    Easy to carry on with contact
CONS OF WHATSAPP
  • 1
    No privacy
  • 1
    Centralized
  • 1
    Maximum to 8 person video call

related WhatsApp posts

Hello everyone, I plan on building a platform that supports 100s of forums out of the box, it would give the user the ability to create forums, where other users can comment, post images, and videos (the size of videos would be limited). Each forum would have the ability to trend. I have been doing a lot of research and I have arrived at Golang and Erlang as the backend languages and PostgreSQL as the DB. Erlang would be used for the routing of chats and messages, while Go would be used to manage the forums. We would also be implementing a one on one chat system like WhatsApp chat, where users can add contacts.

Please I would like to know if the languages picked are appropriate for this project. Suggestions would be appreciated.

See more
Skype logo

Skype

16.9K
13.2K
653
Voice calls, instant messaging, file transfer, and video conferencing
16.9K
13.2K
+ 1
653
PROS OF SKYPE
  • 258
    Free, widespread
  • 147
    Desktop and mobile apps
  • 110
    Because i have to :(
  • 57
    Low cost international calling
  • 56
    Good for international calls
  • 10
    Best call quality anywhere, generally
  • 5
    Beautiful emojis
  • 4
    Chat bots
  • 2
    Translator
  • 2
    Skype for business integration with Outlook
  • 1
    United kingdom
  • 1
    Not the Best, but get the job done
CONS OF SKYPE
  • 5
    Really high CPU utilization during video/screenshare
  • 3
    Not always reliable
  • 3
    Outdated UI
  • 3
    Birthday notifications are annoying
  • 3
    The worst indicator noises of any app ever
  • 2
    Finding/adding people isn't easy

related Skype posts

Dmitry Mukhin

Uploadcare is mostly remote team and we're using video conferencing all the time both for internal team meetings and for external sales, support, interview, etc. calls. I think we've tried every solution there is on the market before we've decided to stop with Zoom.

Tools just plainly don't work (Skype), are painful to install for external participants (Webex and other "enterprise" solutions) can't properly handle 10+ participants calls (Google Hangouts Chat).

Zoom just works. It has all required features and even handles bad connections very graciously. One of the best tool decisions we've ever made :)

See more
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
Telegram  logo

Telegram

737
623
50
A cloud-based instant messaging and voice over IP service
737
623
+ 1
50
PROS OF TELEGRAM
  • 15
    Lightweight
  • 8
    Great bot API
  • 8
    Free
  • 8
    Unlimited history
  • 4
    Can hide phone number
  • 3
    Media editor
  • 2
    Great bot
  • 2
    Delete without a trace
CONS OF TELEGRAM
  • 3
    Requires phone number
  • 3
    Notification customisation is limited
  • 2
    No video call

related Telegram posts

Django Stars
Developer at Django Stars · | 6 upvotes · 43K views
Shared insights
on
Telegram Telegram PythonPython
at

How to Create and Deploy a Telegram Bot using Python

Nuances of Telegram Bot Development When we’ve already determined reasons for creating the bot, now it’s time to think on how we plan to organize the development process and what tools we will need. Further, we will demonstrate in practice how to create your first bot and how to teach it to turn our message inside out.

In this part, we are planning how to build the application and what development tools to use. Further, we’ll show how to build your first Telegram bot on Python and will teach it to turn our message backwards. Since it is the manual for beginners, we will run the server with a single endpoint that will receive our telegram messages and will make an answer.

For that, we will use the following tools:

bottle – for our server; a simple and lightweight WSGI micro web-framework requests – for sending requests to telegram. request lib does not need to be overrepresented. It is universally used throughout the world in a variety of projects. Note: you have to install these tools on your computer. We will need them later. For that, open your bash console and install it via pip

See more

Hello, I want to implement a Telegram channel in my SAAS Application. Which API should I choose, Telegram API or Telegram Bot API??

See more
Duo logo

Duo

21
43
1
A next-generation package manager for the front end
21
43
+ 1
1
PROS OF DUO
  • 1
    Lean and efficient
CONS OF DUO
    Be the first to leave a con

    related Duo posts

    Zoom logo

    Zoom

    1.7K
    1.9K
    155
    Video Conferencing, Web Conferencing, Webinars, Screen Sharing
    1.7K
    1.9K
    + 1
    155
    PROS OF ZOOM
    • 25
      Web conferencing made easy
    • 16
      Remote control option
    • 13
      Draw on screen
    • 12
      Very reliable
    • 11
      In-meeting chat is pretty good
    • 9
      Free
    • 9
      Pair programming sessions with shared controls
    • 8
      Easy to share meeting links/invites
    • 7
      Good Sound Quality
    • 6
      Cloud recordings for meetings
    • 5
      Great mobile app
    • 4
      Virtual backgrounds
    • 4
      Recording Feature
    • 4
      Other people use it
    • 4
      User Friendly actions
    • 2
      Reactions (emoticons)
    • 2
      Auto reconnecting
    • 2
      Chrome extension is great to easily create meetings
    • 2
      While sharing screen, you can still see your video
    • 2
      Mute all participants at once
    • 2
      When ending the videocall, everybody gets kicked
    • 2
      Different options for blocking chat
    • 1
      Easily share video with audio
    • 1
      /zoom on Slack
    • 1
      Registration form
    • 1
      Meant for business and education
    • 0
      Zoom
    CONS OF ZOOM
    • 20
      Limited time if you are a basic member
    • 14
      Limited Storage
    • 11
      Hate how sharing your screen defaults to Full Screen
    • 10
      Quality isn't great (Free)
    • 9
      No cursor highlight on screenshare.
    • 8
      Potential security flaws
    • 7
      Onboarding process for new users is not intuitive
    • 5
      Virtual background quality isn't good
    • 5
      Security
    • 4
      Editing can be improved
    • 4
      Doesn't handle switching audio sources well
    • 4
      The native calendar is buggy
    • 4
      Dashboard can be improved
    • 3
      Pornographic material displayed
    • 3
      Any body can get in it
    • 3
      Not many emojis
    • 3
      Past chat history is not saved
    • 3
      Recording Feature
    • 3
      En In reality,the chat in the meet not is excelent,noo
    • 3
      Zoom lags a lot

    related Zoom posts

    Yogesh Bhondekar
    Product Manager | SaaS | Traveller · | 15 upvotes · 424.5K views

    Hi, I am building an enhanced web-conferencing app that will have a voice/video call, live chats, live notifications, live discussions, screen sharing, etc features. Ref: Zoom.

    I need advise finalizing the tech stack for this app. I am considering below tech stack:

    • Frontend: React
    • Backend: Node.js
    • Database: MongoDB
    • IAAS: #AWS
    • Containers & Orchestration: Docker / Kubernetes
    • DevOps: GitLab, Terraform
    • Brokers: Redis / RabbitMQ

    I need advice at the platform level as to what could be considered to support concurrent video streaming seamlessly.

    Also, please suggest what could be a better tech stack for my app?

    #SAAS #VideoConferencing #WebAndVideoConferencing #zoom #stack

    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
    JavaScript logo

    JavaScript

    351.5K
    267.6K
    8.1K
    Lightweight, interpreted, object-oriented language with first-class functions
    351.5K
    267.6K
    + 1
    8.1K
    PROS OF JAVASCRIPT
    • 1.7K
      Can be used on frontend/backend
    • 1.5K
      It's everywhere
    • 1.2K
      Lots of great frameworks
    • 897
      Fast
    • 745
      Light weight
    • 425
      Flexible
    • 392
      You can't get a device today that doesn't run js
    • 286
      Non-blocking i/o
    • 237
      Ubiquitousness
    • 191
      Expressive
    • 55
      Extended functionality to web pages
    • 49
      Relatively easy language
    • 46
      Executed on the client side
    • 30
      Relatively fast to the end user
    • 25
      Pure Javascript
    • 21
      Functional programming
    • 15
      Async
    • 13
      Full-stack
    • 12
      Setup is easy
    • 12
      Future Language of The Web
    • 12
      Its everywhere
    • 11
      Because I love functions
    • 11
      JavaScript is the New PHP
    • 10
      Like it or not, JS is part of the web standard
    • 9
      Expansive community
    • 9
      Everyone use it
    • 9
      Can be used in backend, frontend and DB
    • 9
      Easy
    • 8
      Most Popular Language in the World
    • 8
      Powerful
    • 8
      Can be used both as frontend and backend as well
    • 8
      For the good parts
    • 8
      No need to use PHP
    • 8
      Easy to hire developers
    • 7
      Agile, packages simple to use
    • 7
      Love-hate relationship
    • 7
      Photoshop has 3 JS runtimes built in
    • 7
      Evolution of C
    • 7
      It's fun
    • 7
      Hard not to use
    • 7
      Versitile
    • 7
      Its fun and fast
    • 7
      Nice
    • 7
      Popularized Class-Less Architecture & Lambdas
    • 7
      Supports lambdas and closures
    • 6
      It let's me use Babel & Typescript
    • 6
      Can be used on frontend/backend/Mobile/create PRO Ui
    • 6
      1.6K Can be used on frontend/backend
    • 6
      Client side JS uses the visitors CPU to save Server Res
    • 6
      Easy to make something
    • 5
      Clojurescript
    • 5
      Promise relationship
    • 5
      Stockholm Syndrome
    • 5
      Function expressions are useful for callbacks
    • 5
      Scope manipulation
    • 5
      Everywhere
    • 5
      Client processing
    • 5
      What to add
    • 4
      Because it is so simple and lightweight
    • 4
      Only Programming language on browser
    • 1
      Test
    • 1
      Hard to learn
    • 1
      Test2
    • 1
      Not the best
    • 1
      Easy to understand
    • 1
      Subskill #4
    • 1
      Easy to learn
    • 0
      Hard 彤
    CONS OF JAVASCRIPT
    • 22
      A constant moving target, too much churn
    • 20
      Horribly inconsistent
    • 15
      Javascript is the New PHP
    • 9
      No ability to monitor memory utilitization
    • 8
      Shows Zero output in case of ANY error
    • 7
      Thinks strange results are better than errors
    • 6
      Can be ugly
    • 3
      No GitHub
    • 2
      Slow

    related JavaScript posts

    Zach Holman

    Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

    But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

    But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

    Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 10.7M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Git logo

    Git

    290.4K
    174.5K
    6.6K
    Fast, scalable, distributed revision control system
    290.4K
    174.5K
    + 1
    6.6K
    PROS OF GIT
    • 1.4K
      Distributed version control system
    • 1.1K
      Efficient branching and merging
    • 959
      Fast
    • 845
      Open source
    • 726
      Better than svn
    • 368
      Great command-line application
    • 306
      Simple
    • 291
      Free
    • 232
      Easy to use
    • 222
      Does not require server
    • 27
      Distributed
    • 22
      Small & Fast
    • 18
      Feature based workflow
    • 15
      Staging Area
    • 13
      Most wide-spread VSC
    • 11
      Role-based codelines
    • 11
      Disposable Experimentation
    • 7
      Frictionless Context Switching
    • 6
      Data Assurance
    • 5
      Efficient
    • 4
      Just awesome
    • 3
      Github integration
    • 3
      Easy branching and merging
    • 2
      Compatible
    • 2
      Flexible
    • 2
      Possible to lose history and commits
    • 1
      Rebase supported natively; reflog; access to plumbing
    • 1
      Light
    • 1
      Team Integration
    • 1
      Fast, scalable, distributed revision control system
    • 1
      Easy
    • 1
      Flexible, easy, Safe, and fast
    • 1
      CLI is great, but the GUI tools are awesome
    • 1
      It's what you do
    • 0
      Phinx
    CONS OF GIT
    • 16
      Hard to learn
    • 11
      Inconsistent command line interface
    • 9
      Easy to lose uncommitted work
    • 7
      Worst documentation ever possibly made
    • 5
      Awful merge handling
    • 3
      Unexistent preventive security flows
    • 3
      Rebase hell
    • 2
      When --force is disabled, cannot rebase
    • 2
      Ironically even die-hard supporters screw up badly
    • 1
      Doesn't scale for big data

    related Git posts

    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 9.6M views

    Our whole DevOps stack consists of the following tools:

    • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
    • Respectively Git as revision control system
    • SourceTree as Git GUI
    • Visual Studio Code as IDE
    • CircleCI for continuous integration (automatize development process)
    • Prettier / TSLint / ESLint as code linter
    • SonarQube as quality gate
    • Docker as container management (incl. Docker Compose for multi-container application management)
    • VirtualBox for operating system simulation tests
    • Kubernetes as cluster management for docker containers
    • Heroku for deploying in test environments
    • nginx as web server (preferably used as facade server in production environment)
    • SSLMate (using OpenSSL) for certificate management
    • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
    • PostgreSQL as preferred database system
    • Redis as preferred in-memory database/store (great for caching)

    The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

    • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
    • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
    • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
    • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
    • Scalability: All-in-one framework for distributed systems.
    • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
    See more
    Tymoteusz Paul
    Devops guy at X20X Development LTD · | 23 upvotes · 8.6M views

    Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

    It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

    I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

    We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

    If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

    The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

    Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

    See more
    GitHub logo

    GitHub

    280K
    244.3K
    10.3K
    Powerful collaboration, review, and code management for open source and private development projects
    280K
    244.3K
    + 1
    10.3K
    PROS OF GITHUB
    • 1.8K
      Open source friendly
    • 1.5K
      Easy source control
    • 1.3K
      Nice UI
    • 1.1K
      Great for team collaboration
    • 867
      Easy setup
    • 504
      Issue tracker
    • 486
      Great community
    • 482
      Remote team collaboration
    • 451
      Great way to share
    • 442
      Pull request and features planning
    • 147
      Just works
    • 132
      Integrated in many tools
    • 121
      Free Public Repos
    • 116
      Github Gists
    • 112
      Github pages
    • 83
      Easy to find repos
    • 62
      Open source
    • 60
      It's free
    • 60
      Easy to find projects
    • 56
      Network effect
    • 49
      Extensive API
    • 43
      Organizations
    • 42
      Branching
    • 34
      Developer Profiles
    • 32
      Git Powered Wikis
    • 30
      Great for collaboration
    • 24
      It's fun
    • 23
      Clean interface and good integrations
    • 22
      Community SDK involvement
    • 20
      Learn from others source code
    • 16
      Because: Git
    • 14
      It integrates directly with Azure
    • 10
      Standard in Open Source collab
    • 10
      Newsfeed
    • 8
      It integrates directly with Hipchat
    • 8
      Fast
    • 8
      Beautiful user experience
    • 7
      Easy to discover new code libraries
    • 6
      Smooth integration
    • 6
      Cloud SCM
    • 6
      Nice API
    • 6
      Graphs
    • 6
      Integrations
    • 6
      It's awesome
    • 5
      Quick Onboarding
    • 5
      Reliable
    • 5
      Remarkable uptime
    • 5
      CI Integration
    • 5
      Hands down best online Git service available
    • 4
      Uses GIT
    • 4
      Version Control
    • 4
      Simple but powerful
    • 4
      Unlimited Public Repos at no cost
    • 4
      Free HTML hosting
    • 4
      Security options
    • 4
      Loved by developers
    • 4
      Easy to use and collaborate with others
    • 3
      Ci
    • 3
      IAM
    • 3
      Nice to use
    • 3
      Easy deployment via SSH
    • 2
      Easy to use
    • 2
      Leads the copycats
    • 2
      All in one development service
    • 2
      Free private repos
    • 2
      Free HTML hostings
    • 2
      Easy and efficient maintainance of the projects
    • 2
      Beautiful
    • 2
      Easy source control and everything is backed up
    • 2
      IAM integration
    • 2
      Very Easy to Use
    • 2
      Good tools support
    • 2
      Issues tracker
    • 2
      Never dethroned
    • 2
      Self Hosted
    • 1
      Dasf
    • 1
      Profound
    CONS OF GITHUB
    • 53
      Owned by micrcosoft
    • 37
      Expensive for lone developers that want private repos
    • 15
      Relatively slow product/feature release cadence
    • 10
      API scoping could be better
    • 8
      Only 3 collaborators for private repos
    • 3
      Limited featureset for issue management
    • 2
      GitHub Packages does not support SNAPSHOT versions
    • 2
      Does not have a graph for showing history like git lens
    • 1
      No multilingual interface
    • 1
      Takes a long time to commit
    • 1
      Expensive

    related GitHub posts

    Johnny Bell

    I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

    I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

    I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

    Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

    Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

    With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

    If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

    See more
    Russel Werner
    Lead Engineer at StackShare · | 32 upvotes · 2.5M views

    StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

    Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

    #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

    See more