惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
罗磊的独立博客
博客园 - 【当耐特】
M
MIT News - Artificial intelligence
月光博客
月光博客
博客园_首页
博客园 - 叶小钗
T
Tailwind CSS Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
I
InfoQ
量子位
小众软件
小众软件
爱范儿
爱范儿
The GitHub Blog
The GitHub Blog
IT之家
IT之家
Jina AI
Jina AI
阮一峰的网络日志
阮一峰的网络日志
G
Google Developers Blog
WordPress大学
WordPress大学
人人都是产品经理
人人都是产品经理
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
J
Java Code Geeks
云风的 BLOG
云风的 BLOG
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
First Release of LDL 0.1 — A Small Library with a Big Sou...
Evgeniy · 2026-05-05 · via DEV Community

Evgeniy

First Release of LDL 0.1 — A Small Library with a Big Soul. One API for 30 Years of Computer History


Hello, developers!

I'm excited to announce the first public release of the LDL library.


What is LDL?

LDL (Little Directmedia Layer) is more than just a cross-platform library — it's a bridge between different eras of software development. It lets you write code that runs just as well on Windows 95 as it does on Windows 11, on ancient Linux kernels as well as modern distributions, on FreeBSD 3.0 and the latest releases.

The library is written in pure C89 (ANSI C), ensuring maximum portability — even to the most exotic compilers and platforms.


The Journey: From C++98 to C89

I originally wrote LDL in C++98, which already provided good portability. But over time, I reconsidered my approach:

  1. I switched entirely to C89 — this gives maximum compatibility with old compilers and platforms, including DOS, Windows 95, Solaris, and even PlayStation 1.

  2. I abandoned the idea of releasing a full-featured 1.0 all at once — now releases are iterative:

    • First: windows, events, graphics ✅
    • Next: 2D renderer 🔜
    • Then: audio and fonts 🔜

This way, the project doesn't stall offline for years but grows gradually in front of the community.


Backends: Not a Replacement, but a Bridge

LDL doesn't try to replace SDL, SFML, or GLFW — it becomes a layer on top of them. Planned backends include:

  • SDL 1.2
  • SDL 2.x
  • SDL 3.x
  • SFML
  • GLFW

This means you can build an LDL application on top of any of these libraries without changing a single line of code. The API stays the same; underneath, you can plug in any supported windowing and input system.

Why is this useful?

  • If native support for a platform isn't ready yet, you can temporarily use a backend through an existing library.
  • Developers already familiar with SDL or GLFW can try LDL without completely replacing their toolchain.
  • You can leverage features from these libraries (like audio or fonts in SDL) earlier than they're implemented natively in LDL.

Minimal Window Example

/*
 * -----------------------------------------------------------------------------
 * This example is in the public domain (CC0 1.0 Universal).
 * You can copy, modify, use, and distribute it for any purpose.
 * -----------------------------------------------------------------------------
 */

#include <LDL/LDL.h>

int main(void)
{
    LDL_Result*  result;
    LDL_Context* context;
    LDL_Window*  window;
    LDL_Event    event;

    result  = LDL_ResultNew();
    context = LDL_ContextNew(LDL_ContextOpenGL1);
    window  = LDL_WindowNew(result, context, 
                            LDL_GetVec2i(0, 0), 
                            LDL_GetVec2i(800, 600), 
                            "LDL - Simple Window", 
                            LDL_WindowModeResized);

    if (LDL_ResultIsOk(result))
    {
        while (LDL_WindowIsRunning(window))
        {
            while (LDL_WindowGetEvent(window, &event))
            {
                if (event.Type == LDL_EventIsQuit || 
                    LDL_EventIsKeyPressed(&event, LDL_KeyEscape))
                {
                    LDL_WindowStopEvent(window);
                }
            }

            LDL_WindowPresent(window);
            LDL_Delay(16);
        }

        LDL_WindowFree(window);
        LDL_ContextFree(context);
        LDL_ResultFree(result);
    }

    if (LDL_ResultIsFail(result))
    {
        printf("Error: %s\n", LDL_ResultGetMessage(result));
    }

    return 0;
}

Enter fullscreen mode Exit fullscreen mode


Features in Current Version (0.1)

Feature Support
Windowing ✅ Create, resize, close
Events ✅ Keyboard, mouse, resize, focus
Keyboard ✅ Full key mapping
Mouse ✅ Movement, clicks, scroll wheel
OpenGL 1.0–4.6 ✅ From immediate mode to compute shaders

Supported Platforms

OS Versions
Windows 95, 98, ME, 2000, XP, Vista, 7, 8, 10, 11
Linux Kernel 2.0 – 6.x (1996–present)
FreeBSD 3.0 – 14.x (1998–present)

Build & Install

# Install dependencies (Debian/Ubuntu)
sudo apt-get install libx11-dev libgl1-mesa-dev

# Clone and build
git clone https://github.com/JordanCpp/LDL.git
cd LDL
cmake -B build
cmake --build build

Enter fullscreen mode Exit fullscreen mode


Roadmap: Version 0.2

The next major goal is adding a unified 2D renderer — a single interface for drawing sprites, lines, rectangles, and text that works identically on any hardware.

The developer doesn't need to think about what's under the hood: modern Vulkan, legacy OpenGL, or just a CPU with no GPU. LDL automatically selects the optimal backend.

  • On modern systems → Vulkan or OpenGL with hardware acceleration
  • On retro hardware → software rasterizer

Same code. Same visual result. Everywhere.

Planned 2D API Features:

  • Sprite loading and drawing
  • Position, rotation, scale
  • Color effects and transparency
  • Line and rectangle drawing
  • Text rendering with fonts

Goal: Code written with LDL should live for decades — from '90s consoles and retro PCs to ultra-modern workstations — without rewrites or surprises.


Philosophy: The Charm of Old Hardware

"We stand on the shoulders of giants whose names we often forget, but whose work continues to shape our world every day."

LDL is an attempt to preserve the connection between generations of developers. It doesn't try to replace existing solutions (like SDL or GLFW) — it complements them, providing a unified API for platforms that usually get left behind.

LDL isn't just a library. It's an attempt to preserve that special feeling of working with technology from the past:

  • The flicker of a CRT monitor
  • The warmth of a fanless CPU working hard on every clock cycle
  • How '90s engineers squeezed the impossible out of kilobytes of memory and megahertz of clock speed

Today we have terabytes and teraflops, but we've lost something important — the art of doing more with less. LDL brings that approach back. Every line of the library is written with the thought that it might run on a Pentium 66 MHz with 8 MB of RAM.

Why Does This Matter?

Because modern software lives 3–5 years. We throw away working hardware not because it's broken, but because software has become too heavy and lazy.

LDL is a protest against planned obsolescence. It's code that doesn't require hardware upgrades every three years.

One codebase. Thirty years of computer history. And the charm felt by those who remember when programming was a true art of survival within constraints.


Screenshots

OpenGL 1.2 Examples

3D Atom Model Animated 3D Terrain Rotate
3D Atom Model Animated 3D Terrain Rotate
Terrain Flight Water Wave Simulation
Terrain Flight Water Wave Simulation

OpenGL 2.1 Examples

Textured Terrain Solar System
Textured Terrain Solar System

OpenGL 3.3 Examples

Animated Water Surface Rotating Cube Textured Sphere
Animated Water Surface Rotating Cube Textured Sphere

License

Component License
LDL Library LGPLv3
Example Code CC0 1.0 (Public Domain)

GitHub: github.com/JordanCpp/LDL

One API. One Codebase. Thirty Years of Computing History. 🚀