![]() The supremacy of graphical interfaces is reflected in the rapid adoption rate of the GUIs themselves and the tools to interact with them - for that, we have the Xerox Palo Alto Research Center and Apple (which was Apple Computer back in those times) to thank. Compared to GUIs, console commands are tedious to execute even aided by aliases, autocompletion, and history navigation, the developer is still limited by their input speed (i.e. In my personal experience, the most important benefit of mastering the terminal has to with automation. You have to wonder, though: why exactly is proficiency in command-line interfaces a skill that many beginning developers are advised to obtain? The Power to Automate and Customize ![]() This (somewhat humorous) sentiment was perfectly portrayed in numerous Hollywood blockbusters from the ‘90s: a young hacker teams up with a Schwarzenegger-esque protagonist, tries to infiltrate the bad guys’ network/system, which finally culminates in the following phrase: When you ask developers about the benefits that command-line interfaces can offer, they often tell you - reflexively - that it makes the user “feel like a hacker/wizard”. This debate reaches beyond personal preferences and creates an image of “proficiency in CLIs as a superpower”. Although we’re making this recommendation jokingly, there is some truth to that: for some reason, we often put great importance into how we interact with our devices. ![]() graphical interfaces” is a great conversation starter when you’re approaching a new group of developers - just mention that you prefer one over the other and people will tell you, in great detail, why you’re wrong. The timeless debate of “command-line interfaces vs. GUIs” debate click here to jump straight to the section about GitHub Desktop itself) The Cases For/Against Command-Line Interfaces (Disclaimer: We first delve into the “CLIs vs. GitHub, the world’s largest software development platform, just so happens to be offering a desktop app called GitHub Desktop - and in this article, we’ll explore the ins and outs of this program, highlighting its advantages and discussing the potential problems and caveats you need to know about. However, how to use it (and, by extension, services like GitHub, GitLab, and BitBucket) comes down to the developers’ preferences: Naturally, git as a technology sparked even more collaboration between the developers from all around the world - a glance at GitHub’s home page stands as a testament to that. All of a sudden, developers were granted the ability to create alternate timelines ( git branch), visualize their great deeds ( git log and gitk) ground their magic in reality ( git commit and git push), and more. Nowadays, the development process evolved into a more balanced, full-featured, and enjoyable workflow thanks to version control software. If you’re interested in hearing more ways to extend your workflow with GitHub Desktop and other GitHub apps like CLI and Mobile check out Neha Batra’s session “Putting GitHub at your fingertips” at GitHub Satellite.Git holds a special place in the development world - in the dark times before git, the typical project structure would look like this: Hopefully this reduces that context-switching so you can complete your full local workflow from GitHub Desktop. We’ve heard feedback that tagging is one of the few features remaining in your regular workflow that you have to do via the command line. GitHub Desktop also notifies you when you’ve created tags but haven’t yet pushed them, so you don’t forget to share your latest tag with the rest of the team. Now when you push to, any tags created in Desktop are automatically included. With today’s 2.5 release, you can create and view your tags directly from GitHub Desktop. As one of the most requested features in the past six months, we’re excited to deliver it. They’re most frequently used to specify the commit for a given release or for any significant milestone. As promised at GitHub Satellite, Git tags are coming to GitHub Desktop! Tags are helpful references that allow you to mark a particular point in your project’s history.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |