HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
grz0zrg
fbg
C2018–2018
grz0zrg / fbg

fbg

Lightweight C 2D graphics API agnostic library with parallelism support

2Distinct people
2Mentions
0Explicit recommenders
540GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Lightweight C 2D graphics API agnostic library with parallelism support

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

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

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

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

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2018-06-17 23:34:52 UTC to 2018-06-18 01:28:09 UTC.

012018-06-17 23:00:00 UTC to 2018-06-18 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJun 17, 23:002018-06-18 00:00:00 UTC to 2018-06-18 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 18, 00:002018-06-18 01:00:00 UTC to 2018-06-18 02:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 18, 01:00

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
Jun 17, 23:002018-06-17 23:00:00 UTC2018-06-18 00:00:00 UTC110
Jun 18, 00:002018-06-18 00:00:00 UTC2018-06-18 01:00:00 UTC000
Jun 18, 01:002018-06-18 01:00:00 UTC2018-06-18 02:00:00 UTC101

What Hacker News says

2 sources
It looks very ineffective. For example, in fbg_draw() they have this code: https://github.com/grz0zrg/fbg/blob/master/src/fbgraphics.c#... > memcpy(fbg->buffer, fbg->disp_buffer, fbg->size); So they don't flip buffers, and don't even use video memory for them, they just copy data from buffer in main memory into a memory-mapped framebuffer. This must be slow. Also it doesn't check for vblank and therefore doesn't protect from tearing, but the description says they have "double buffering". As a side note, I remember that framebuffer was very slow on a computer I had. Without proprietary video card driver both Windows and Linux had troubles even scrolling a window, it was very laggy. Why was unaccelerated VGA (or VESA?) mode so slow, I wonder?
In FBG – Lightweight C Linux framebuffer graphics with parallelism

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.