Minecraft: Java Edition now uses SDL3

Original Article ↗ Hacker News Discussion ↗

Minecraft: Java Edition’s move from GLFW to SDL3 is seen as a major infrastructure upgrade, promising better cross‑platform windowing, input handling, and Wayland support, but early snapshots show serious fullscreen stability issues on Windows and Linux. Commenters emphasize that such regressions are expected in opt‑in test builds, and use the change to compare SDL3 with SDL2/GLFW, debate exclusive vs borderless fullscreen, and reflect on Java vs Bedrock trade‑offs. Alongside the engine talk, many share practical advice on running family or community servers, from Docker and VPS setups to Realms and cross‑play via GeyserMC.

SDL3 Transition & Rationale

  • Minecraft: Java Edition has switched its window/input layer from GLFW to SDL3.
  • No official rationale is cited in the thread.
  • Speculated benefits:
    • Better, more robust cross‑platform input and window handling, especially for Wayland.
    • SDL is a more complete platform layer (windowing, input, audio, etc.) and highly portable.
    • Improved keyboard layout handling and IME support.
  • Some question whether features like SDL’s 2D/3D rendering or mobile/platform breadth are actually relevant, since Minecraft uses its own rendering pipeline (OpenGL / Vulkan).

Fullscreen Modes, Crashes & Snapshots

  • Known issues: exclusive fullscreen crashes on Windows (multi‑monitor) and Wayland.
  • Debate on whether such bugs should delay a snapshot:
    • One side: these are release‑blocking level bugs.
    • Other side: snapshots are explicitly unstable, opt‑in test builds, so shipping with serious bugs is acceptable and useful for telemetry and early feedback.
  • Discussion that many games and OSes have moved away from exclusive fullscreen toward borderless fullscreen due to compatibility and streaming/recording concerns.
  • macOS fullscreen UX is widely criticized (Spaces animations, menu bar behavior), with some blaming the OS more than the games.

SDL3 Adoption & Ecosystem

  • Other games (e.g., osu!) report latency and performance improvements after moving to SDL3.
  • On Linux, sdl2‑compat and sdl12‑compat often mean apps effectively run atop SDL3 anyway.
  • SDL3 is relatively new; some distros (e.g., Ubuntu 24.04) initially lacked it, slowing adoption.
  • Many games bundle their own SDL; others rely on system libs or packaging (AUR, Nix, Flatpak, Steam runtimes).

Java vs Bedrock Split

  • Java Edition remains dominant among “serious” PC players, modders, speedrunners, and large servers.
  • Bedrock is used on consoles, mobile, and Windows Store; offers better raw performance but fewer mods and more bugs, and is more locked down/monetized.
  • Historical context: Bedrock (C++) emerged for consoles/mobile where JVM/JIT are impractical; Java was heavily indebted and later refactored.
  • Fragmentation between editions is a major pain point for families and admins; protocol bridges like GeyserMC allow Bedrock clients on Java servers but with limitations.

Running Family Minecraft Servers (2026 Focus)

  • Many recommend Java servers plus Bedrock bridge (GeyserMC + Floodgate) so iPad/console and PC can play together.
  • A common stack: itzg’s Docker images (Java or Bedrock), sometimes behind WireGuard/Tailscale, occasionally on Kubernetes or fly.io.
  • Others prefer hosted options (Realms, Shockbyte, Pufferfish.host) for simplicity and uptime; Realms is often seen as the easiest way for kids on iPads.
  • Advice to understand edition differences (Java vs Bedrock), backups, whitelisting, and basic Linux/server management; LLMs are reported as useful remote “ops helpers.”

Performance, JVM Tuning & Server Modding

  • Strong pushback against old JVM tuning guides; modern advice centers on:
    • Use the latest JVM (17+), avoid cargo‑cult flags.
    • Prefer modern GCs (especially ZGC) for low latency.
    • Heap size recommendations vary:
      • Some suggest “as high as comfortable” with ZGC, others cap at ~8 GiB for most modpacks, others point out heavy modded servers often need 8–16 GiB+.
      • Warnings about >32 GiB heaps due to compressed‑oops and GC behavior.
  • Consensus that earlier performance issues were largely Minecraft code quality; newer versions plus optimization mods (e.g., Sodium/Lithium families, Fabric/NeoForge ecosystem) greatly improve performance.
  • Paper/Spigot/Purpur are noted as high‑performance server forks that can subtly break redstone/farms; vanilla+optimization mods are preferred for “pure” behavior.

Modding, “Minecraft as Engine,” and Education

  • Many see Minecraft increasingly as an engine or platform, especially with powerful modding APIs and bytecode‑based extensibility on Java.
  • Community projects (e.g., big modpacks, alternate servers in Rust, alternative engines like Luanti+Mineclonia, ComputerCraft/OpenComputers) are cited as extremely influential.
  • Some use Minecraft/ComputerCraft to teach programming, networking, and systems concepts in an appealing, game‑centric environment.

Miscellaneous Reactions

  • Some checked the release to ensure cross‑platform support wasn’t being reduced or logins further locked down.
  • Wayland crash being a “known issue” is jokingly framed as “pretty good for Wayland.”
  • Thread includes scattered notes on niche topics: email inside Minecraft, Nethack mail daemons, and curiosity about Python‑based Minecraft programming, though details are sparse.