Alternatives to RubyMine logo

Alternatives to RubyMine

IntelliJ IDEA, Atom, Visual Studio Code, WebStorm, and Vim are the most popular alternatives and competitors to RubyMine.
609
468
+ 1
344

What is RubyMine and what are its top alternatives?

JetBrains RubyMine IDE provides a comprehensive Ruby code editor aware of dynamic language specifics and delivers smart coding assistance, intelligent code refactoring and code analysis capabilities.
RubyMine is a tool in the Integrated Development Environment category of a tech stack.

Top Alternatives to RubyMine

  • IntelliJ IDEA
    IntelliJ IDEA

    Out of the box, IntelliJ IDEA provides a comprehensive feature set including tools and integrations with the most important modern technologies and frameworks for enterprise and web development with Java, Scala, Groovy and other languages. ...

  • Atom
    Atom

    At GitHub, we're building the text editor we've always wanted. A tool you can customize to do anything, but also use productively on the first day without ever touching a config file. Atom is modern, approachable, and hackable to the core. We can't wait to see what you build with it. ...

  • Visual Studio Code
    Visual Studio Code

    Build and debug modern web and cloud applications. Code is free and available on your favorite platform - Linux, Mac OSX, and Windows. ...

  • WebStorm
    WebStorm

    WebStorm is a lightweight and intelligent IDE for front-end development and server-side JavaScript. ...

  • Vim
    Vim

    Vim is an advanced text editor that seeks to provide the power of the de-facto Unix editor 'Vi', with a more complete feature set. Vim is a highly configurable text editor built to enable efficient text editing. It is an improved version of the vi editor distributed with most UNIX systems. Vim is distributed free as charityware. ...

  • Eclipse
    Eclipse

    Standard Eclipse package suited for Java and plug-in development plus adding new plugins; already includes Git, Marketplace Client, source code and developer documentation. Click here to file a bug against Eclipse Platform. ...

  • 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. ...

RubyMine alternatives & related posts

IntelliJ IDEA logo

IntelliJ IDEA

43.6K
1.5K
Capable and Ergonomic IDE for JVM
43.6K
1.5K
PROS OF INTELLIJ IDEA
  • 301
    Fantastically intelligent
  • 242
    Best-in-class ide
  • 190
    Many languages support
  • 158
    Java
  • 121
    Fast
  • 82
    Code analysis
  • 79
    Reliable
  • 76
    Out of the box integration with maven, git, svn
  • 64
    Plugin architecture
  • 61
    Integrated version control
  • 12
    Code refactoring support
  • 11
    Best java IDE
  • 7
    Local history
  • 6
    Code Completion
  • 6
    Kotlin
  • 6
    Integrated Database Navigator
  • 6
    Built-in terminal/run tools
  • 5
    All
  • 5
    Free for open-source development, students and teacher
  • 5
    Base for Android Studio
  • 5
    Free If you're a Student
  • 4
    ERD Diagrams
  • 4
    Free
  • 4
    Cross platform
  • 4
    IDE
  • 4
    Database/Code integration
  • 3
    Out Of The Box features
  • 3
    Column Selection Mode
  • 3
    Server and client-side debugger
  • 3
    More than enough languages for any developer
  • 3
    Typescript support
  • 3
    Multicursor support
  • 3
    Reformating Code
  • 3
    Intuitive
  • 3
    Command-line tools
  • 3
    Android Integration
  • 3
    Vim support
  • 3
    Special icons for most filetypes in project list
  • 3
    Supports many frameworks
  • 3
    Built-in web server
  • 3
    Live Templates
  • 3
    Scala support
  • 2
    Works fine with mac os catalina
  • 2
    A lot of plugin
  • 2
    Just works
  • 2
    Integrated Ssh/Ftp Managers
  • 2
    Full support
  • 2
    Task managers
  • 2
    Diff tools
  • 2
    File Watchers
  • 2
    Support for various package managers
  • 2
    Integrated Code Linting
  • 2
    Clean UI
  • 2
    Open source
  • 2
    So modernised
  • 2
    Efficient, one Stop solution
CONS OF INTELLIJ IDEA
  • 20
    Large footprint required to really enjoy (mem/disc)
  • 16
    Very slow
  • 8
    Bad for beginners
  • 7
    UI is not intuitive
  • 5
    Not nearly as many tools to integrate as vs code
  • 5
    Constant reindexing
  • 4
    Needs a lot of CPU and RAM power
  • 3
    Built in terminal is slow
  • 3
    Doesn't work that well with windows 10 edu
  • 1
    Ruby is a plug in
  • 1
    Pesky warnings increase with every release
  • 0
    AAD

related IntelliJ IDEA posts

christy craemer

UPDATE: Thanks for the great response. I am going to start with VSCode based on the open source and free version that will allow me to grow into other languages, but not cost me a license ..yet.

I have been working with software development for 12 years, but I am just beginning my journey to learn to code. I am starting with Python following the suggestion of some of my coworkers. They are split between Eclipse and IntelliJ IDEA for IDEs that they use and PyCharm is new to me. Which IDE would you suggest for a beginner that will allow expansion to Java, JavaScript, and eventually AngularJS and possibly mobile applications?

See more

I am a QA heading to a new company where they all generally use Visual Studio Code, my experience is with IntelliJ IDEA and PyCharm. The language they use is JavaScript and so I will be writing my test framework in javaScript so the devs can more easily write tests without context switching.

My 2 questions: Does VS Code have Cucumber Plugins allowing me to write behave tests? And more importantly, does VS Code have the same refactoring tools that IntelliJ IDEA has? I love that I have easy access to a range of tools that allow me to refactor and simplify my code, making code writing really easy.

See more
Atom logo

Atom

16.9K
2.5K
A hackable text editor for the 21st Century
16.9K
2.5K
PROS OF ATOM
  • 529
    Free
  • 449
    Open source
  • 343
    Modular design
  • 321
    Hackable
  • 316
    Beautiful UI
  • 147
    Backed by github
  • 119
    Built with node.js
  • 113
    Web native
  • 107
    Community
  • 35
    Packages
  • 18
    Cross platform
  • 5
    Nice UI
  • 5
    Multicursor support
  • 5
    TypeScript editor
  • 3
    Open source, lots of packages, and so configurable
  • 3
    cli start
  • 3
    Simple but powerful
  • 3
    Chrome Inspector works IN EDITOR
  • 3
    Snippets
  • 2
    Code readability
  • 2
    It's powerful
  • 2
    Awesome
  • 2
    Smart TypeScript code completion
  • 2
    Well documented
  • 1
    works with GitLab
  • 1
    "Free", "Hackable", "Open Source", The Awesomness
  • 1
    full support
  • 1
    vim support
  • 1
    Split-Tab Layout
  • 1
    Apm publish minor
  • 1
    Consistent UI on all platforms
  • 1
    User friendly
  • 1
    Hackable and Open Source
  • 0
    Publish
CONS OF ATOM
  • 19
    Slow with large files
  • 7
    Slow startup
  • 2
    Most of the time packages are hard to find.
  • 1
    No longer maintained
  • 1
    Cannot Run code with F5
  • 1
    Can be easily Modified

related Atom posts

Jerome Dalbert
Principal Backend Software Engineer at StackShare · | 13 upvotes · 935.5K views

I liked Sublime Text for its speed, simplicity and keyboard shortcuts which synergize well when working on scripting languages like Ruby and JavaScript. I extended the editor with custom Python scripts that improved keyboard navigability such as autofocusing the sidebar when no files are open, or changing tab closing behavior.

But customization can only get you so far, and there were little things that I still had to use the mouse for, such as scrolling, repositioning lines on the screen, selecting the line number of a failing test stack trace from a separate plugin pane, etc. After 3 years of wearily moving my arm and hand to perform the same repetitive tasks, I decided to switch to Vim for 3 reasons:

  • your fingers literally don’t ever need to leave the keyboard home row (I had to remap the escape key though)
  • it is a reliable tool that has been around for more than 30 years and will still be around for the next 30 years
  • I wanted to "look like a hacker" by doing everything inside my terminal and by becoming a better Unix citizen

The learning curve is very steep and it took me a year to master it, but investing time to be truly comfortable with my #TextEditor was more than worth it. To me, Vim comes close to being the perfect editor and I probably won’t need to switch ever again. It feels good to ignore new editors that come out every few years, like Atom and Visual Studio Code.

See more
Julian Sanchez
Lead Developer at Chore Champion · | 9 upvotes · 786.8K views

We use Visual Studio Code because it allows us to easily and quickly integrate with Git, much like Sublime Merge ,but it is integrated into the IDE. Another cool part about VS Code is the ability collaborate with each other with Visual Studio Live Share which allows our whole team to get more done together. It brings the convenience of the Google Suite to programming, offering something that works more smoothly than anything found on Atom or Sublime Text

See more
Visual Studio Code logo

Visual Studio Code

180.9K
2.3K
Build and debug modern web and cloud applications, by Microsoft
180.9K
2.3K
PROS OF VISUAL STUDIO CODE
  • 340
    Powerful multilanguage IDE
  • 308
    Fast
  • 193
    Front-end develop out of the box
  • 158
    Support TypeScript IntelliSense
  • 142
    Very basic but free
  • 126
    Git integration
  • 106
    Intellisense
  • 78
    Faster than Atom
  • 53
    Better ui, easy plugins, and nice git integration
  • 45
    Great Refactoring Tools
  • 44
    Good Plugins
  • 42
    Terminal
  • 38
    Superb markdown support
  • 36
    Open Source
  • 35
    Extensions
  • 26
    Awesome UI
  • 26
    Large & up-to-date extension community
  • 24
    Powerful and fast
  • 22
    Portable
  • 18
    Best code editor
  • 18
    Best editor
  • 17
    Easy to get started with
  • 15
    Lots of extensions
  • 15
    Good for begginers
  • 15
    Crossplatform
  • 15
    Built on Electron
  • 14
    Extensions for everything
  • 14
    Open, cross-platform, fast, monthly updates
  • 14
    All Languages Support
  • 13
    Easy to use and learn
  • 12
    "fast, stable & easy to use"
  • 12
    Extensible
  • 11
    Ui design is great
  • 11
    Totally customizable
  • 11
    Git out of the box
  • 11
    Useful for begginer
  • 11
    Faster edit for slow computer
  • 10
    SSH support
  • 10
    Great community
  • 10
    Fast Startup
  • 9
    Works With Almost EveryThing You Need
  • 9
    Great language support
  • 9
    Powerful Debugger
  • 9
    It has terminal and there are lots of shortcuts in it
  • 8
    Can compile and run .py files
  • 8
    Python extension is fast
  • 7
    Features rich
  • 7
    Great document formater
  • 6
    He is not Michael
  • 6
    Extension Echosystem
  • 6
    She is not Rachel
  • 6
    Awesome multi cursor support
  • 5
    VSCode.pro Course makes it easy to learn
  • 5
    Language server client
  • 5
    SFTP Workspace
  • 5
    Very proffesional
  • 5
    Easy azure
  • 4
    Has better support and more extentions for debugging
  • 4
    Supports lots of operating systems
  • 4
    Excellent as git difftool and mergetool
  • 4
    Virtualenv integration
  • 3
    Better autocompletes than Atom
  • 3
    Has more than enough languages for any developer
  • 3
    'batteries included'
  • 3
    More tools to integrate with vs
  • 3
    Emmet preinstalled
  • 2
    VS Code Server: Browser version of VS Code
  • 2
    CMake support with autocomplete
  • 2
    Microsoft
  • 2
    Customizable
  • 2
    Light
  • 2
    Big extension marketplace
  • 2
    Fast and ruby is built right in
  • 1
    File:///C:/Users/ydemi/Downloads/yuksel_demirkaya_webpa
CONS OF VISUAL STUDIO CODE
  • 46
    Slow startup
  • 29
    Resource hog at times
  • 20
    Poor refactoring
  • 13
    Poor UI Designer
  • 11
    Weak Ui design tools
  • 10
    Poor autocomplete
  • 8
    Super Slow
  • 8
    Huge cpu usage with few installed extension
  • 8
    Microsoft sends telemetry data
  • 7
    Poor in PHP
  • 6
    It's MicroSoft
  • 3
    Poor in Python
  • 3
    No Built in Browser Preview
  • 3
    No color Intergrator
  • 3
    Very basic for java development and buggy at times
  • 3
    No built in live Preview
  • 3
    Electron
  • 2
    Bad Plugin Architecture
  • 2
    Powered by Electron
  • 1
    Terminal does not identify path vars sometimes
  • 1
    Slow C++ Language Server

related Visual Studio Code posts

Yshay Yaacobi

Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.9M 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
WebStorm logo

WebStorm

13.5K
985
The smartest JavaScript IDE
13.5K
985
PROS OF WEBSTORM
  • 187
    Intelligent ide
  • 128
    Smart development environment
  • 108
    Easy js debugging
  • 97
    Code inspection
  • 95
    Support for the Latest Technologies
  • 55
    Created by jetbrains
  • 53
    Cross-platform ide
  • 36
    Integration
  • 30
    Spellchecker
  • 24
    Language Mixing/Injection
  • 11
    Debugger
  • 10
    Local History
  • 8
    Web developer can't live without this
  • 7
    Fast search
  • 7
    Git support
  • 6
    Angular.js support
  • 6
    Sass autocompletion
  • 5
    Better refactoring options
  • 5
    FTP
  • 5
    There is no need to setup plugins (all from the box)
  • 5
    Show color on the border next to hex string in CSS
  • 5
    Smart autocompletion
  • 5
    JSON Schema
  • 5
    Awesome
  • 5
    Built-in js debugger
  • 5
    Running and debugging Node.js apps remotely
  • 4
    Easy to use
  • 4
    A modern IDE stuck in the 90s
  • 4
    TypeScript support
  • 4
    Smart coding assistance for React
  • 4
    Node.js integration
  • 4
    111
  • 4
    Protractor support out of the box
  • 4
    Intelligent
  • 4
    Paid but easy to crack
  • 3
    Dart support
  • 3
    Solid intelligent features
  • 3
    Great app
  • 3
    Integrated terminal
  • 3
    Vagrant and SSH Console
  • 3
    Free for students
  • 3
    Unused imports inspection
  • 3
    Docker intergration
  • 2
    Remote Files Syncronization
  • 2
    Grate debug tools for React Apps
  • 2
    Easier to keep running than eclipse
  • 1
    Auto imports
  • 1
    Vim support
  • 1
    Rename helpers
  • 1
    Auto refactoring helpers
  • 1
    Less autocompletion
  • 1
    GIT partial commits
CONS OF WEBSTORM
  • 4
    Paid
  • 1
    Expensive

related WebStorm posts

Johnny Bell

When I switched to Visual Studio Code 12 months ago from PhpStorm I was in love, it was great. However after using VS Code for a year, I see myself switching back and forth between WebStorm and VS Code. The VS Code plugins are great however I notice Prettier, auto importing of components and linking to the definitions often break, and I have to restart VS Code multiple times a week and sometimes a day.

We use Ruby here so I do like that Visual Studio Code highlights that for me out of the box, with WebStorm I'd need to probably also install RubyMine and have 2 IDE's going at the same time.

Should I stick with Visual Studio Code, or switch to something else? #help

See more
Russel Werner
Lead Engineer at StackShare · | 7 upvotes · 591.3K views

We use Prettier because when we rebooted our front-end stack, I decided that it would be an efficient use of our time to not worry about code formatting issues and personal preferences during peer review. Prettier eliminates this concern by auto-formatting our code to a deterministic output. We use it along with ESLint and have 1st-class support in our WebStorm and Visual Studio Code editors.

See more
Vim logo

Vim

27.5K
2.4K
Highly configurable text editor built to enable efficient text editing
27.5K
2.4K
PROS OF VIM
  • 347
    Comes by default in most unix systems (remote editing)
  • 328
    Fast
  • 312
    Highly configurable
  • 297
    Less mouse dependence
  • 247
    Lightweight
  • 145
    Speed
  • 100
    Plugins
  • 97
    Hardcore
  • 82
    It's for pros
  • 65
    Vertically split windows
  • 30
    Open-source
  • 25
    Modal editing
  • 22
    No remembering shortcuts, instead "talks" to the editor
  • 21
    It stood the Test of Time
  • 16
    Unicode
  • 13
    VimPlugins
  • 13
    Everything is on the keyboard
  • 13
    Stick with terminal
  • 12
    Dotfiles
  • 11
    Flexible Indenting
  • 10
    Hands stay on the keyboard
  • 10
    Efficient and powerful
  • 10
    Programmable
  • 9
    Everywhere
  • 9
    Large number of Shortcuts
  • 8
    A chainsaw for text editing
  • 8
    Unmatched productivity
  • 7
    Developer speed
  • 7
    Super fast
  • 7
    Makes you a true bearded developer
  • 7
    Because its not Emacs
  • 7
    Modal editing changes everything
  • 6
    You cannot exit
  • 6
    Themes
  • 5
    EasyMotion
  • 5
    Most and most powerful plugins of any editor
  • 5
    Shell escapes and shell imports :!<command> and !!cmd
  • 5
    Intergrated into most editors
  • 5
    Shortcuts
  • 5
    Great on large text files
  • 5
    Habit
  • 5
    Plugin manager options. Vim-plug, Pathogen, etc
  • 4
    Intuitive, once mastered
  • 4
    Perfect command line editor
  • 1
    Not MicroSoft
CONS OF VIM
  • 8
    Ugly UI
  • 5
    Hard to learn

related Vim posts

Denys
Software engineer at Typeform · | 13 upvotes · 1.9M views
  • Go because it's easy and simple, facilitates collaboration , and also it's fast, scalable, powerful.
  • Visual Studio Code because it has one of the most sophisticated Go language support plugins.
  • Vim because it's Vim
  • Git because it's Git
  • Docker and Docker Compose because it's quick and easy to have reproducible builds/tests with them
  • Arch Linux because Docker for Mac/Win is a disaster for the human nervous system, and Arch is the coolest Linux distro so far
  • Stack Overflow because of Copy-Paste Driven Development
  • JavaScript and Python when a something needs to be coded for yesterday
  • PhpStorm because it saves me like 300 "Ctrl+F" key strokes a minute
  • cURL because terminal all the way
See more
Jerome Dalbert
Principal Backend Software Engineer at StackShare · | 13 upvotes · 935.5K views

I liked Sublime Text for its speed, simplicity and keyboard shortcuts which synergize well when working on scripting languages like Ruby and JavaScript. I extended the editor with custom Python scripts that improved keyboard navigability such as autofocusing the sidebar when no files are open, or changing tab closing behavior.

But customization can only get you so far, and there were little things that I still had to use the mouse for, such as scrolling, repositioning lines on the screen, selecting the line number of a failing test stack trace from a separate plugin pane, etc. After 3 years of wearily moving my arm and hand to perform the same repetitive tasks, I decided to switch to Vim for 3 reasons:

  • your fingers literally don’t ever need to leave the keyboard home row (I had to remap the escape key though)
  • it is a reliable tool that has been around for more than 30 years and will still be around for the next 30 years
  • I wanted to "look like a hacker" by doing everything inside my terminal and by becoming a better Unix citizen

The learning curve is very steep and it took me a year to master it, but investing time to be truly comfortable with my #TextEditor was more than worth it. To me, Vim comes close to being the perfect editor and I probably won’t need to switch ever again. It feels good to ignore new editors that come out every few years, like Atom and Visual Studio Code.

See more
Eclipse logo

Eclipse

2.6K
392
IDE for Java EE Developers
2.6K
392
PROS OF ECLIPSE
  • 131
    Does it all
  • 76
    Integrates with most of tools
  • 64
    Easy to use
  • 63
    Java IDE
  • 32
    Best Java IDE
  • 9
    Open source
  • 3
    Hard for newbews
  • 2
    Great gdb integration
  • 2
    Professional
  • 2
    Good Git client allowing direct stage area edit
  • 2
    True open source with huge contribution
  • 2
    Great code suggestions
  • 2
    Extensible
  • 2
    Lightweight
  • 0
    Works with php
CONS OF ECLIPSE
  • 14
    2000 Design
  • 9
    Bad performance
  • 4
    Hard to use

related Eclipse posts

christy craemer

UPDATE: Thanks for the great response. I am going to start with VSCode based on the open source and free version that will allow me to grow into other languages, but not cost me a license ..yet.

I have been working with software development for 12 years, but I am just beginning my journey to learn to code. I am starting with Python following the suggestion of some of my coworkers. They are split between Eclipse and IntelliJ IDEA for IDEs that they use and PyCharm is new to me. Which IDE would you suggest for a beginner that will allow expansion to Java, JavaScript, and eventually AngularJS and possibly mobile applications?

See more
Dean Stringer

Have been a Visual Studio Code user since just after launch to the general public, having used the likes of Eclipse and Atom previously. Was amazed how mature it seemed off the bat and was super intrigued by the bootstrapped nature of it having been written/based on Electron/TypeScript, and of course being an open-source app from Microsoft. The features, plugin ecosystem and release frequency are very impressive. I do dev work on both Mac and Windows and don't use anything else now as far as IDEs go.

See more
Git logo

Git

298.8K
6.6K
Fast, scalable, distributed revision control system
298.8K
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
  • 28
    Distributed
  • 23
    Small & Fast
  • 18
    Feature based workflow
  • 15
    Staging Area
  • 13
    Most wide-spread VSC
  • 11
    Disposable Experimentation
  • 11
    Role-based codelines
  • 7
    Frictionless Context Switching
  • 6
    Data Assurance
  • 5
    Efficient
  • 4
    Just awesome
  • 3
    Easy branching and merging
  • 3
    Github integration
  • 2
    Compatible
  • 2
    Possible to lose history and commits
  • 2
    Flexible
  • 1
    Team Integration
  • 1
    Easy
  • 1
    Light
  • 1
    Fast, scalable, distributed revision control system
  • 1
    Rebase supported natively; reflog; access to plumbing
  • 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
  • 8
    Worst documentation ever possibly made
  • 5
    Awful merge handling
  • 3
    Unexistent preventive security flows
  • 3
    Rebase hell
  • 2
    Ironically even die-hard supporters screw up badly
  • 2
    When --force is disabled, cannot rebase
  • 1
    Doesn't scale for big data

related Git posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.9M 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 · 10.1M 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

287.8K
10.3K
Powerful collaboration, review, and code management for open source and private development projects
287.8K
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
  • 868
    Easy setup
  • 504
    Issue tracker
  • 487
    Great community
  • 483
    Remote team collaboration
  • 449
    Great way to share
  • 442
    Pull request and features planning
  • 147
    Just works
  • 132
    Integrated in many tools
  • 122
    Free Public Repos
  • 116
    Github Gists
  • 113
    Github pages
  • 83
    Easy to find repos
  • 62
    Open source
  • 60
    Easy to find projects
  • 60
    It's free
  • 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
    Fast
  • 8
    Beautiful user experience
  • 8
    It integrates directly with Hipchat
  • 7
    Easy to discover new code libraries
  • 6
    It's awesome
  • 6
    Smooth integration
  • 6
    Cloud SCM
  • 6
    Nice API
  • 6
    Graphs
  • 6
    Integrations
  • 5
    Hands down best online Git service available
  • 5
    Reliable
  • 5
    Quick Onboarding
  • 5
    CI Integration
  • 5
    Remarkable uptime
  • 4
    Security options
  • 4
    Loved by developers
  • 4
    Uses GIT
  • 4
    Free HTML hosting
  • 4
    Easy to use and collaborate with others
  • 4
    Version Control
  • 4
    Simple but powerful
  • 4
    Unlimited Public Repos at no cost
  • 3
    Nice to use
  • 3
    IAM
  • 3
    Ci
  • 3
    Easy deployment via SSH
  • 2
    Free private repos
  • 2
    Good tools support
  • 2
    All in one development service
  • 2
    Never dethroned
  • 2
    Easy source control and everything is backed up
  • 2
    Issues tracker
  • 2
    Self Hosted
  • 2
    IAM integration
  • 2
    Very Easy to Use
  • 2
    Easy to use
  • 2
    Leads the copycats
  • 2
    Free HTML hostings
  • 2
    Easy and efficient maintainance of the projects
  • 2
    Beautiful
  • 1
    Dasf
  • 1
    Profound
CONS OF GITHUB
  • 55
    Owned by micrcosoft
  • 38
    Expensive for lone developers that want private repos
  • 15
    Relatively slow product/feature release cadence
  • 10
    API scoping could be better
  • 9
    Only 3 collaborators for private repos
  • 4
    Limited featureset for issue management
  • 3
    Does not have a graph for showing history like git lens
  • 2
    GitHub Packages does not support SNAPSHOT versions
  • 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

Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

Check Out My Architecture: CLICK ME

Check out the GitHub repo attached

See more