Alternatives to iTerm2 logo

Alternatives to iTerm2

Hyper, Hyper Terminal, tmux, Termius, and Postman are the most popular alternatives and competitors to iTerm2.
429
288
+ 1
7

What is iTerm2 and what are its top alternatives?

A replacement for Terminal and the successor to iTerm. It works on Macs with macOS 10.12 or newer. iTerm2 brings the terminal into the modern age with features you never knew you always wanted.
iTerm2 is a tool in the Terminal Emulators category of a tech stack.
iTerm2 is an open source tool with 15.4K GitHub stars and 1.2K GitHub forks. Here’s a link to iTerm2's open source repository on GitHub

Top Alternatives to iTerm2

  • Hyper
    Hyper

    Hyper.sh is a secure container hosting service. What makes it different from AWS (Amazon Web Services) is that you don't start servers, but start docker images directly from Docker Hub or other registries. ...

  • Hyper Terminal
    Hyper Terminal

    The goal of the project is to create a beautiful and extensible experience for command-line interface users, built on open web standards. Focus will be primarily around speed and stability. ...

  • tmux
    tmux

    It enables a number of terminals to be created, accessed, and controlled from a single screen. tmux may be detached from a screen and continue running in the background, then later reattached. ...

  • Termius
    Termius

    The #1 cross-platform terminal with built-in ssh client which works as your own portable server management system in any situation. ...

  • Postman
    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Postman
    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Stack Overflow
    Stack Overflow

    Stack Overflow is a question and answer site for professional and enthusiast programmers. It's built and run by you as part of the Stack Exchange network of Q&A sites. With your help, we're working together to build a library of detailed answers to every question about programming. ...

  • Google Maps
    Google Maps

    Create rich applications and stunning visualisations of your data, leveraging the comprehensiveness, accuracy, and usability of Google Maps and a modern web platform that scales as you grow. ...

iTerm2 alternatives & related posts

Hyper logo

Hyper

207
0
On-Demand Container, Per-Second Billing
207
0
PROS OF HYPER
    Be the first to leave a pro
    CONS OF HYPER
      Be the first to leave a con

      related Hyper posts

      Hyper Terminal logo

      Hyper Terminal

      106
      0
      A terminal built on web technologies
      106
      0
      PROS OF HYPER TERMINAL
        Be the first to leave a pro
        CONS OF HYPER TERMINAL
          Be the first to leave a con

          related Hyper Terminal posts

          tmux logo

          tmux

          191
          2
          A terminal multiplexer
          191
          2
          PROS OF TMUX
          • 2
            Reliable, easy and highly customizable
          CONS OF TMUX
            Be the first to leave a con

            related tmux posts

            I have a strong familiarity with Jetbrains products, having used most of them since around 2015. However, in the past 6 months, I have started transitioning to Neovim as my primary "IDE". This is due to the extensive nature of my work, where I would typically load a different JetBrains product for each programming language I was working with. I wanted to reduce the amount of RAM I was using and have an easier time exporting my setup to weaker hardware.

            My current setup, which is still a work in progress, consists of Neovim, tmux, and a few other applications. It took me a while, but I now feel much more comfortable working with this setup than I did with Jetbrains products. In the past, I often had to change my workflow or struggle with some of the tooling provided by JetBrains.

            While I haven't worked with Java in a production environment for a few years, I have been working with TypeScript, PHP, Python, C++, and C#. Neovim works well for almost everything, but I do encounter some issues when working with .NET. In these cases, JetBrains Rider seems to be a better fit for C#, and I hope to resolve these issues. I also have an extensive ruleset setup (naming schemes and whatnot) in the JetBrains ecosystem that I have yet to find a suitable alternative of enforcement in Neovim.

            However, I am now facing the prospect of returning to a Java stack at work. I'm wondering whether I should continue with Neovim and invest more time in configuring it and researching more about its Language Server Protocol (LSP) capabilities, or if I should return to IntelliJ and not waste the effort. Can Neovim be as good as, or almost as good as, IntelliJ for Java development? Talking about Kotlin is a plus, but my focus is on Java and potentially working with the Spring ecosystem.

            I have used the JetBrains' vim plugin for about 2 years. It does not hold a candle to using nvim. Probably this shouldn't affect the question much, but: I am a Linux/Windows guy, however, I will be forced to use macOS at work.

            See more
            Termius logo

            Termius

            80
            10
            Use modern SSH for macOS, Windows and Linux to organize, access, and connect to your servers
            80
            10
            PROS OF TERMIUS
            • 3
              Free
            • 2
              Data Sharing
            • 2
              Mobile and Desktop
            • 1
              Proxy
            • 1
              Mosh
            • 1
              Jump hosts
            CONS OF TERMIUS
              Be the first to leave a con

              related Termius posts

              Postman logo

              Postman

              94.5K
              1.8K
              Only complete API development environment
              94.5K
              1.8K
              PROS OF POSTMAN
              • 490
                Easy to use
              • 369
                Great tool
              • 276
                Makes developing rest api's easy peasy
              • 156
                Easy setup, looks good
              • 144
                The best api workflow out there
              • 53
                It's the best
              • 53
                History feature
              • 44
                Adds real value to my workflow
              • 43
                Great interface that magically predicts your needs
              • 35
                The best in class app
              • 12
                Can save and share script
              • 10
                Fully featured without looking cluttered
              • 8
                Collections
              • 8
                Option to run scrips
              • 8
                Global/Environment Variables
              • 7
                Shareable Collections
              • 7
                Dead simple and useful. Excellent
              • 7
                Dark theme easy on the eyes
              • 6
                Awesome customer support
              • 6
                Great integration with newman
              • 5
                Documentation
              • 5
                Simple
              • 5
                The test script is useful
              • 4
                Saves responses
              • 4
                This has simplified my testing significantly
              • 4
                Makes testing API's as easy as 1,2,3
              • 4
                Easy as pie
              • 3
                API-network
              • 3
                I'd recommend it to everyone who works with apis
              • 3
                Mocking API calls with predefined response
              • 2
                Now supports GraphQL
              • 2
                Postman Runner CI Integration
              • 2
                Easy to setup, test and provides test storage
              • 2
                Continuous integration using newman
              • 2
                Pre-request Script and Test attributes are invaluable
              • 2
                Runner
              • 2
                Graph
              • 1
                <a href="http://fixbit.com/">useful tool</a>
              CONS OF POSTMAN
              • 10
                Stores credentials in HTTP
              • 9
                Bloated features and UI
              • 8
                Cumbersome to switch authentication tokens
              • 7
                Poor GraphQL support
              • 5
                Expensive
              • 3
                Not free after 5 users
              • 3
                Can't prompt for per-request variables
              • 1
                Import swagger
              • 1
                Support websocket
              • 1
                Import curl

              related Postman posts

              Noah Zoschke
              Engineering Manager at Segment · | 30 upvotes · 3M views

              We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

              Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

              Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

              This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

              Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

              Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

              Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

              See more
              Simon Reymann
              Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 5.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
              Postman logo

              Postman

              94.5K
              1.8K
              Only complete API development environment
              94.5K
              1.8K
              PROS OF POSTMAN
              • 490
                Easy to use
              • 369
                Great tool
              • 276
                Makes developing rest api's easy peasy
              • 156
                Easy setup, looks good
              • 144
                The best api workflow out there
              • 53
                It's the best
              • 53
                History feature
              • 44
                Adds real value to my workflow
              • 43
                Great interface that magically predicts your needs
              • 35
                The best in class app
              • 12
                Can save and share script
              • 10
                Fully featured without looking cluttered
              • 8
                Collections
              • 8
                Option to run scrips
              • 8
                Global/Environment Variables
              • 7
                Shareable Collections
              • 7
                Dead simple and useful. Excellent
              • 7
                Dark theme easy on the eyes
              • 6
                Awesome customer support
              • 6
                Great integration with newman
              • 5
                Documentation
              • 5
                Simple
              • 5
                The test script is useful
              • 4
                Saves responses
              • 4
                This has simplified my testing significantly
              • 4
                Makes testing API's as easy as 1,2,3
              • 4
                Easy as pie
              • 3
                API-network
              • 3
                I'd recommend it to everyone who works with apis
              • 3
                Mocking API calls with predefined response
              • 2
                Now supports GraphQL
              • 2
                Postman Runner CI Integration
              • 2
                Easy to setup, test and provides test storage
              • 2
                Continuous integration using newman
              • 2
                Pre-request Script and Test attributes are invaluable
              • 2
                Runner
              • 2
                Graph
              • 1
                <a href="http://fixbit.com/">useful tool</a>
              CONS OF POSTMAN
              • 10
                Stores credentials in HTTP
              • 9
                Bloated features and UI
              • 8
                Cumbersome to switch authentication tokens
              • 7
                Poor GraphQL support
              • 5
                Expensive
              • 3
                Not free after 5 users
              • 3
                Can't prompt for per-request variables
              • 1
                Import swagger
              • 1
                Support websocket
              • 1
                Import curl

              related Postman posts

              Noah Zoschke
              Engineering Manager at Segment · | 30 upvotes · 3M views

              We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

              Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

              Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

              This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

              Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

              Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

              Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

              See more
              Simon Reymann
              Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 5.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
              Stack Overflow logo

              Stack Overflow

              69K
              893
              Question and answer site for professional and enthusiast programmers
              69K
              893
              PROS OF STACK OVERFLOW
              • 257
                Scary smart community
              • 206
                Knows all
              • 142
                Voting system
              • 134
                Good questions
              • 83
                Good SEO
              • 22
                Addictive
              • 14
                Tight focus
              • 10
                Share and gain knowledge
              • 7
                Useful
              • 3
                Fast loading
              • 2
                Gamification
              • 1
                Knows everyone
              • 1
                Experts share experience and answer questions
              • 1
                Stack overflow to developers As google to net surfers
              • 1
                Questions answered quickly
              • 1
                No annoying ads
              • 1
                No spam
              • 1
                Fast community response
              • 1
                Good moderators
              • 1
                Quick answers from users
              • 1
                Good answers
              • 1
                User reputation ranking
              • 1
                Efficient answers
              • 1
                Leading developer community
              CONS OF STACK OVERFLOW
              • 3
                Not welcoming to newbies
              • 3
                Unfair downvoting
              • 3
                Unfriendly moderators
              • 3
                No opinion based questions
              • 3
                Mean users
              • 2
                Limited to types of questions it can accept

              related Stack Overflow posts

              Tom Klein

              Google Analytics is a great tool to analyze your traffic. To debug our software and ask questions, we love to use Postman and Stack Overflow. Google Drive helps our team to share documents. We're able to build our great products through the APIs by Google Maps, CloudFlare, Stripe, PayPal, Twilio, Let's Encrypt, and TensorFlow.

              See more
              Google Maps logo

              Google Maps

              41.5K
              567
              Build highly customisable maps with your own content and imagery
              41.5K
              567
              PROS OF GOOGLE MAPS
              • 253
                Free
              • 136
                Address input through maps api
              • 82
                Sharable Directions
              • 47
                Google Earth
              • 46
                Unique
              • 3
                Custom maps designing
              CONS OF GOOGLE MAPS
              • 4
                Google Attributions and logo
              • 1
                Only map allowed alongside google place autocomplete

              related Google Maps posts

              Tom Klein

              Google Analytics is a great tool to analyze your traffic. To debug our software and ask questions, we love to use Postman and Stack Overflow. Google Drive helps our team to share documents. We're able to build our great products through the APIs by Google Maps, CloudFlare, Stripe, PayPal, Twilio, Let's Encrypt, and TensorFlow.

              See more

              A huge component of our product relies on gathering public data about locations of interest. Google Places API gives us that ability in the most efficient way. Since we are primarily going to be using as google data as a source of information for our MVP, we might as well start integrating the Google Places API in our system. We have worked with Google Maps in the past and we might take some inspiration from our previous projects onto this one.

              See more