Elixir-lang.org has a new design

Original Article ↗ Hacker News Discussion ↗

Elixir’s official website has launched a new design that many welcome as faster, more polished, and better at showcasing use cases like web apps, distributed systems, and machine learning. Commenters use the change as a springboard to reflect on the Elixir/BEAM ecosystem itself: its elegant functional model, strong concurrency, emerging gradual type system, and perceived gaps such as raw performance tuning, tooling, and a small job market. Accessibility concerns (dark mode, animations, older browsers) and comparisons with Erlang, Gleam, and other languages round out a broader assessment of where Elixir stands and how it might evolve.

Overall reaction to the redesign

  • Many commenters like the new elixir-lang.org design: clearer presentation, better highlighting of use cases, ecosystem packages, and company showcase.
  • Several see it as helpful for adoption and onboarding; docs and entry points are praised as thoughtful.
  • Others are neutral on aesthetics but acknowledge that a shinier site helps marketing.

UX, performance, and accessibility feedback

  • Site is described as “blazing fast” by some, but others complain about:
    • Short yet noticeable animations that feel unnecessary.
    • Heavy reliance on JavaScript; the site breaks with JS disabled or on older Firefox versions.
    • Mixed light/dark sections, which some find visually appealing but others find hard to read or at odds with accessibility.
    • Lack of an obvious light-mode toggle on the main site (though docs do have a theme switch).
    • Excessive whitespace on smaller/older monitors and minor layout glitches in Firefox.
  • A few users report broken links (e.g., getting-started docs) and minor copy typos, which are quickly fixed.

Debate on AI/ML presence

  • Some appreciate that “AI” and “LLM” are not front-and-center on the landing page.
  • Others note there is a Machine Learning section further down and argue about whether “ML” vs “AI/LLM” are perceived as distinct by most people.
  • Discussion touches on how public and even technical communities now use “AI” as the dominant buzzword.

Broader discussion about Elixir and BEAM

  • Many express strong enthusiasm for Elixir’s elegance, Phoenix/LiveView, concurrency model, and BEAM suitability for high-concurrency and agent/multi-agent systems.
  • Some highlight Elixir/BEAM’s strengths in distributed systems, embedded/semi-embedded control, and telecom-scale messaging, with concrete anecdotes.
  • Concerns raised:
    • Raw performance of the BEAM vs other runtimes.
    • Desire for more optimization (e.g., cross-module, better boxing strategies, JIT improvements, WASM target, easier single-file executables).
    • Small job market and talent pool; debate over whether scarcity should command a premium and how much AI reduces need for language specialists.
    • Skepticism about Elixir’s type system vs static alternatives (e.g., Gleam), and whether Elixir’s syntax adds unnecessary complexity.
  • There is disagreement over how essential experienced Elixir developers are when using AI tools, and over claims of AI-written systems being audit-clean.