Githut Alternatives

Similar projects and alternatives to githut

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better githut alternative or higher similarity.

githut reviews and mentions

Posts with mentions or reviews of githut. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-29.
  • Ask HN: Why Did Python Win?
    3 projects | | 29 Aug 2023
    fad - an intense and widely shared enthusiasm for something, especially one that is short-lived and without basis in the object's qualities; a craze.


    I don't think Ruby is a fad. The drop off Ruby had since early 2010s is dramatic, but it stabilized around 5% of all PRs on GH in the last few years:

    It's still one of the most popular languages for web development.

  • Ten Years of “Go: The Good, the Bad, and the Meh
    5 projects | | 18 Jul 2023
    I would beg to differ.

    On Github[0], Go currently sits at #3 for pull request volume (C# is at 10), #3 for stars (C# is at 8), #6 for pushes (C# is at 10) and #6 for stars (C# is at 9). By each of those metrics, Go has a much more vibrant ecosystem than C#.


  • Steel Bank Common Lisp
    9 projects | | 30 Jun 2023
    One measure is git pushes on GitHub. By that measure[0], in Q1 2023, we have Emacs Lisp (2995 pushes) > Clojure (2135) > Scheme (1350) > Common Lisp (236) > Racket (below detection; latest in Q1 2022: 102).


  • Sigils are an underappreciated programming technology
    2 projects | | 29 May 2023
    > 20 years ago I might've agreed with you. But I do not think that PHP, BASIC and shell scripting are popular beginner languages in 2023.

    PHP and shell scripting are still massively used in 2023 (eg You have a point about BASIC but it was the de facto standard for computers at a time when people didn't have the web to quickly look up problems and thus learning to code was much harder. Yet we (in fact I) managed just fine.

    > Quotation marks and especially parentheses after function calls don't fit TFA's definition of a sigil because they aren't at the beginning of the word and (arguably only in the latter case) don't communicate meta-information about the word.

    I didn't say they are sigils. I said they're tokens. My point was that removing sigils doesn't remove meta-information encoded in magic characters:

    - You have `foobar()` where the braces denote (call the function rather than pass the function reference

    - "" == string which allows escaping and/or infixing vs '' which doesn't (other languages have different tokens for denoting string literals, like `` in Go)

    - # in C and C++ is a marco

    - // is a line comment in some languages. Others use #, or --

    - Some languages use any of the following for multi-line comments: ```, /* /, and even {} is used. Whereas it's an execution block in some other languages

    My point is you have to learn what all of these tokens mean regardless of whether they sit as a prefix or not. The that that they're a sigil doesn't change anything.

    The real complaint people are making here is about specific languages, like Perl, overloading sigils to do magical things. That is a valid complaint but, in my opinion, it's a complaint against overloading tokens rather than sigils specifically. Much like a complaint about operator overloading doesn't lead to the natural conclusion that all operators are bad.

    > don't communicate meta-information about the word.

    We need to be careful about our assumption about whether a token effectively communicates meta-information because while I do agree that some tokens are more intuitive than others, there is also a hell of a lot of learned behaviour involved as well. And it's really* hard to separate what is easier to understand from what we've just gotten so use to that we no longer give a second thought about.

    This is a massive problem whenever topics about code readability comes up :)

    > I'll agree with you that the line between sigils and general syntax/punctuation is a bit of a blurry one - where do you stop?

    shrugs...somewhere...? You can't really say there should be a hard line that a language designer shouldn't cross because it really depends on the purpose of that language. For example the language I'm currently working on makes heavy use of sigils but it also makes heavy use of barewords because it's primary use is in interactive shells. So stricter C-like strings and function braces would be painful in a read once write many environment (and I know this because that was my original language design -- and I hated using the shell with those constraints).

    In a REPL environment with heavy use of barewords, sigils add a lot to the readability of the code (and hence why Perl originally adopted sigils. Why AWK, Bash, Powershell, etc all use them, etc).

    However in lower level languages, those tokens can add noise. So they're generally only used to differentiate between passing values vs references.

    But this is a decision each language needs to make on a case by case basis and for each sigil.

    There also needs to be care not to overload sigils (like Perl does) because that can get super confusing super quick. If you cannot describe a sigil in one sentence, then it is probably worth reconsidering whether that sigil is adding more noise than legibility.

    > sing my definition above, I think wrapping strings in quotation marks is a clear win because it fits our widely-held shared understanding that quotation marks demarcate and group a sequence of words. Single and double quotes behaving differently is unintuitive for the same reason while not conferring a corresponding benefit on experts.

    Here lies the next problem for programming languages. For them to be useful, they need to be flexible. And as languages grow in age, experts in those languages keep asking for more and more features. Python is a great example of this:

    - ''

    - ""

    - ''' '''

    - """ """

    - f""

    ...and lots of Python developers cannot even agree on when to use single and double quotes!

    I tried to keep quoting simple in my own language but I ended up with three different ways to quote:

    - '' (string literals)

    - "" (strings with support for escaping and infixing)

    - %() (string nesting. For when you need a string within a string within a string. Doesn't come up often but useful for dynamic code. A contrived example might look like: `tmux -c %(sh -c %(echo %(hello world)))` (there are certainly better ways you could write that specific code but you get the kind of edge case I'm hinting at).

    As much as languages do need to be easy to learn, they shouldn't sacrifice usability in the process. So it is a constant balancing act trying to make something easy to learn, yet also powerful enough to actually have a practical use. Not to mention the constant push and pull between verbosity where some claim fewer characters (eg `fn` as a function keyword) improves readability because it declutters the screen from boilerplate, while others say terms like `function` are more readable because it is closer to executable pseudo-code. Ultimately you cannot please all of the people all of the time.

  • PYTHON vs OCTAVE for Matlab alternative
    3 projects | /r/math | 22 May 2023
    The official julia user developer survey for 2022 lists GitHub as the largest platform of people using julia which intuitively also seems fitting to me as it seems like the community is very pro "open code, open science". But checking the GitHub language trends (via and you can see that Julia has been rather stagnant since 2019 w.r.t. some measures and only slowly growing w.r.t. others.
  • The RedMonk Programming Language Rankings: January 2023
    2 projects | | 16 May 2023
    It seems to me they made the same mistake that I did in my GitHub archive queries, they do not filter bot accounts. JavaScript, without filter, is on top 1 because of dependabot. If you filter all bots then Python is number 1, see:
  • How to Sell Elixir Again (2023)
    7 projects | | 13 May 2023
  • por qua a galera não gosta de Java?
    2 projects | /r/brdev | 11 Mar 2023
  • Why Python keeps growing, explained
    7 projects | | 3 Mar 2023
    And yet, GitHub seems to be in no rush to support Python in GitHub Packages This has been TBD status for years. Frustrating for anyone needing to manage private libraries and tools. And baffling, since Python is now the most popular language on their platform by most metrics
  • Elixir for Humans Who Know Python
    6 projects | | 25 Feb 2023
    I guess it really depends on your definition of make it. :)

    Elixir today is used by several startups, unicorns, fortune 500, and at least two of the FAANG (for whatever it is worth). It is used for web apps, embedded, distributed systems, data processing, and making inroads on AI and machine learning. It has a vibrant community with events around the world, several dozens books, and more.

    It is on the [top quadrant of Redmonk]( and [top 25 on most GitHub language stats]( while being the second youngest language there (only older than Swift which was created by Apple).

    Considering it is a language standing on the shoulder of giants but started by a 30 person company, I would say we definitely made it (although I am obviously biased!). Of course there is a lot to improve, but we will be here for quite a while.

  • A note from our sponsor - SurveyJS | 23 Sep 2023
    SurveyJS JavaScript libraries allow you to easily set up a robust form management system fully integrated into your IT infrastructure where users can create and edit multiple dynamic JSON-based forms in a no-code form builder. Learn more now. Learn more →


Basic githut repo stats
2 months ago

madnight/githut is an open source project licensed under GNU Affero General Public License v3.0 which is an OSI approved license.

The primary programming language of githut is JavaScript.

Write Clean JavaScript Code. Always.
Sonar helps you commit clean code every time. With over 300 unique rules to find JavaScript bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.