HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
garrigue
lablgtk
OCaml2018–2023
garrigue / lablgtk

lablgtk

LablGTK 2 and 3: an interface to the GIMP Tool Kit

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

What to know before exploring

What it is

LablGTK 2 and 3: an interface to the GIMP Tool Kit

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 year3 dated mentions

Observed mentions: 2018-08-23 15:17:34 UTC to 2023-04-25 02:33:45 UTC.

012018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023

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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101

What Hacker News says

3 sources
Couldn't disagree more, writing apps in C is a breath of fresh air compared anything in java but especially android. I can start with a simple C file and write hello world in a few lines of C (dated examples: http://zetcode.com/gui/gtk2/firstprograms/) and run it on my desktop, IME the complexity curve remains quite flat. AFAIK mono never gained much acceptance (and was highly controversial at the time) and most of the gnome ecosystem is written in C, I'd be surprised if there was more C# code than JS and python in gnome today. > I fear this OS is destined to become like Samsung Tizen, which is riddled with security holes. Is the gnome desktop riddled with security holes? I don't know much about tizen but they seem to have written a lot more of their own stuff, the vast majority librem is battle hardened. > It's not as if we don't have ex
Read the rest
cellent libre languages, e.g. Rust and OCaml. Rust is not mature enough, especially in it's UI libs and is virtual unheard of outside the HN bubble. The most mature UI available appears to be the GTK bindings though so it's mostly the same stack that you think is a mistake. OCaml despite being older is even more unknown and from a quick google it's most mature UI library seems to also be an out of date GTK (https://github.com/garrigue/lablgtk). Betting on either of those would be the death of the project. > I applaud the open nature of this phone, but using the Gnome stack looks to me like a mistake. Gtk and Qt are the only serious options as of today without having to sink in years of dev work. If anyone really wants to avoid C then there's the GObject system that lets you write code in js/python/xml/others, but I'm hoping this turns out to be the phone ecosystem that respects users and doesn't sacrifice their time and battery for the developers convenience.
In Librem 5 Smartphone Final Specs
Speaking of problems, in my opinions the three biggest are: - Lack of automatic multicore scheduling, this is going to be solved with OCaml multicore project [1] - Lack of updated GUI libraries. There is LablGTK [2], but it stuck to GTK+ 2 version. The main developer started [3] to work on GTK+ 3 version support, but it is still at the very beginning. - Bad Windows platform support [4] (grep for "Windows" word at this page) and [5]. With upcoming opam-2.0 [6] release the support will be slightly better though. [1] https://github.com/ocamllabs/ocaml-multicore [2] https://github.com/garrigue/lablgtk [3] https://github.com/garrigue/lablgtk/issues/2 [4] https://caml.inria.fr/mantis/roadmap_page.php [5] https://github.com/ocaml/opam/issues?utf8=%E2%9C%93&q=is%3Ai... [6] http://opam.ocaml.org/blog/opam-2-0-0-repo-upgrade-roadmap/
In Introduction to Functional Programming in OCaml

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.