A technical vision for the Haskell ecosystem

Re:A technical vision for the Haskell ecosystem by the__alchemist on Friday November 13, 2026 @11:33AM (#50485929)

It sounds like it needs foundational libraries? Or is it something else. For example, almost everything I write requires one or more of:

  - Embedded toolchain and/or HAL/register map for my MCU family or CPU arhitecture
  - A GUI library and/or basic I/O interaction library (keyboard/mouse to start)
  - A GPU interaction library
  - A web framework (Not going to roll my own DB interface, auth, user system, router, template system etc)

(Etc). I.e., some core library which handles the drudgery I can build my application on. If this is what you're getting at, this suggests a plan of attack!

[ Parent | on HN ]

Re:A technical vision for the Haskell ecosystem by chriswarbo on Friday November 13, 2026 @12:26PM (#50486707)

Pretty sure those all exist; e.g. at work we use Yesod and Servant, which are a couple of Haskell web frameworks.

[ Parent | on HN ]

Re:A technical vision for the Haskell ecosystem by jose_zap on Friday November 13, 2026 @02:31PM (#50488545)

Embedded toolchain and/or HAL/register map:

- Copilot (by NASA)

- MicroHs — for running Haskell on an MCU

GUI library and/or basic keyboard/mouse I/O:

- Monomer

- sdl2

- gi-gtk4

GPU interaction library

- OpenGL bindings

- vulkan bindnigs

- Accelerate — numerical GPU computation with an NVIDIA backend.

Web framework with database access, auth, users, routing, and templates:

- IHP

- Yesod

[ Parent | on HN ]