HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
elixir-lang
elixir
Elixir2012–2026
elixir-lang / elixir

elixir

Simple from zero to scale

87Distinct people
109Mentions
1Explicit recommenders
26.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Simple from zero to scale

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

If you haven't read the code for how Elixir handles Unicode support [0] I highly recommend doing so. At compile time it reads from several Unicode Character Database text files…

careersuicide used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

Try Gleam direct repository linkDebated

The discussion centers on whether Gleam's ergonomic design and type safety make it a superior choice for AI-assisted development compared to mainstream languages, despite its smaller ecosystem. A significant portion of the conversation is dedicated to debating the community's political activism and code of conduct, with some users citing these as deterrents while others defend them as standard anti-harassment measures.

137 readable replies · Supporting reply 1 · Supporting reply 2 · Supporting reply 3 · Supporting reply 4

Mentions over time

HN mentions by year109 dated mentions

Observed mentions: 2012-05-25 17:27:18 UTC to 2026-02-21 11:01:10 UTC.

0369122012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20122013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 7 mentions; 5 submissions, 2 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 9 mentions; 4 submissions, 5 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 12 mentions; 7 submissions, 5 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 12 mentions; 3 submissions, 9 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 10 mentions; 2 submissions, 8 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 5 submissions, 4 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 12 mentions; 5 submissions, 7 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC202
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC312
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC752
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC945
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC1275
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC1239
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC1028
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC725
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC954
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC725
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC523
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC615
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC1257
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC725
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Elixir is a programming language designed for building scalable and maintainable applications. For more about Elixir, installation and documentation, check Elixir's website. Bug reports For reporting bugs, visit our issue tracker and follow the steps for reporting a new issue. Please disclose security vulnerabilities privately in our Security page. All currently open bugs related to Elixir are listed in the issues tracker. The Elixir team uses the issues tracker to focus on actionable items, including planned enhancements in the short and medium term. We also do our best to label entries for clarity and to ease collaboration. Our actionable item policy has some important consequences, such as: Proposing new features as well as requests for support, help, and guidance must be done in their own spaces, detailed next. Issues we have identified to be outside of Elixir's scope, such as an upstream bug, will be closed (and requested to be moved elsewhere if appropriate). We actively close unrelated and non-actionable issues to keep the issues tracker tidy. If you believe we got something wrong, drop a comment and we can always reopen the issue. By keeping the overall issues tracker tidy and organized, the community can easily peek at what is coming in new releases and also get involved by commenting on existing issues and submitting pull requests. Please remember to keep the tone positive and be kind! For more information, see the Code of Conduct. Proposing new features You can submit proposals to the Elixir Core mailing list, either through the web interface or by subscribing to it at elixir-lang-core+subscribe@googlegroups.com. Remember to include a clear problem description, compare the proposed solution to existing alternatives in the Elixir ecosystem (and in other languages if possible), and consider the potential impact your changes will have on the codebase and community. For these reasons, we strongly advise you to refine ideas and gather feedback in community spaces (ElixirForum, Discord, etc) before submission. Our website includes a general outline of the language history and its current development focus. Once a proposal is accepted, it will be added to the issue tracker. Features and bug fixes that have already been merged and will be included in the next release are then "closed" and added to the changelog before release. Compiling from source For the many different ways to install Elixir, see our installation instructions on the website. However, if you want to contribute to Elixir, you will need to compile from source. First, install Erlang. After that, clone this repository to your machine, compile and test it: git clone https://github.com/elixir-lang/elixir.git cd elixir make Note: if you are running on Windows, this article includes important notes for compiling Elixir from source on Windows. In case you want to use this Elixir version as your system version, you need to add the bin directory to your PATH environment variable. When updating the repository, you may want to run make clean before recompiling. For deterministic builds, you should set the environment variable ERL_COMPILER_OPTIONS=deterministic. Contributing Contributions to Elixir are always welcome! Before you get started, please check out our CONTRIBUTING.md file. There you will find detailed guidelines on how to set up your environment, run the test suite, format your code, and submit pull requests. Note you must disclose the use of coding agents and AI written code in your contributions. See the "Using AI and coding agents" in CONTRIBUTING.md. Important links Elixir Documentation Elixir Core Mailing list (development) Code of Conduct Issues tracker Changelog Security Policy Open Source Policy License "Elixir" and the Elixir logo are registered trademarks of The Elixir Team. Elixir source code is released under Apache License 2.0. Check LICENSE file for more information.
Read the full README on GitHub

What Hacker News says

7 sources
The changelog for this particular release: https://github.com/elixir-lang/elixir/releases/tag/v0.14.0 Enhancements [ExUnit] Add on_exit/1 callbacks that are guaranteed to run once the test process exits and always in another process [Kernel] Store documentation in the abstract code to avoid loading them when the module is loaded [Kernel] Add get_in/2, put_in/3, update_in/3 and get_and_update_in/3 to handle nested data structure operations [Kernel] Add get_in/1, put_in/2, update_in/2 and get_and_update_in/2 to handle nested data structure operations via paths [Mix] Add Mix.Config to ease definition of configuration files [Mix] Add mix loadconfig task that can be called multiple times to load external configs [Mix] Support --config option on mix run [Mix] Support HTTP_PROXY and HTTPS_PROXY on Mix url commands [Mix] Support --names options i
Read the rest
n mix help which emit only names (useful for autocompletion) [Protocol] Add Protocol.consolidate/2, Protocol.consolidated?/1 and a mix compile.protocols task for protocol consolidation [Protocol] Add Protocol.derive/3 for runtime deriving of a struct [String] Add String.chunk/2 [Struct] Add support for @derive before defstruct/2 definitions Bug fixes [File] File.rm now consistently deletes read-only across operating systems [Kernel] Ensure Mix _build structure works on Windows when copying projects [Kernel] Ensure 1.0E10 (with uppercase E) is also valid syntax [Mix] Fix mix do task for Windows' powershell users [Path] Fix Path.absname("/") and Path.expand("/") to return the absolute path "/". Soft deprecations (no warnings emitted) [Kernel] size/1 is deprecated, please use byte_size/1 or tuple_size/1 instead [ExUnit] teardown/2 and teardown_all/2 are deprecated in favor of on_exit/1 callbacks Deprecations [Access] Access.access/2 is deprecated in favor of Access.get/2 [Dict] Dict.Behaviour is deprecated in favor of Dict [Kernel] Application.Behaviour, GenEvent.Behaviour, GenServer.Behaviour and Supervisor.Behaviour are deprecated in favor of Application, GenEvent, GenServer and Supervisor [Kernel] defexception/3 is deprecated in favor of defexception/1 [Kernel] raise/3 is deprecated in favor of reraise/2 [Kernel] set_elem/3 is deprecated in favor of put_elem/3 [Kernel] Passing an atom var!/1 is deprecated, variables can be built dynamically with Macro.var/2 [Mix] Exceptions that define a :mix_error field to be compatible with Mix are no longer supported. Instead please provide a :mix field and use Mix.raise/1 and Mix.raise/2 Backwards incompatible changes [Access] Kernel.access/2 no longer exists and the Access protocol now requires get/2 (instead of access/2) and get_and_update/3 to be implemented [Kernel] Retrieving docs as module.__info__(:docs) is no longer supported, please use Code.get_docs/2 instead [Kernel] Code.compiler_options/1 no longer accepts custom options, only the ones specified by Elixir (use mix config instead) [Mix] mix new no longer generates a supevision tree by default, please pass --sup instead [Task] Tasks are automatically linked to callers and a failure in the task will crash the caller directly
In Elixir v0.14.0

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.