HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
go-qml
qml
Go2013–2018
go-qml / qml

qml

QML support for the Go language

21Distinct people
22Mentions
1Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

QML support for the Go language

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I recommend checking out go-qml. https://github.com/niemeyer/qml It is a different approach to using Qt GUI programming in Go where you use qml to define your UIs and keep the…

georgemcbay used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:00:59 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 year22 dated mentions

Observed mentions: 2013-09-19 13:22:46 UTC to 2018-01-08 03:11:32 UTC.

02462013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 6 mentions; 2 submissions, 4 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2018

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
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC624
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC716
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC505
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101

What Hacker News says

7 sources
You've been saying that it's just about your own use cases, but your statements in that post are much more general. For example: > What does Go have that Python lacks? Performance, static typing. That's a very simplistic view. Being a long term Python developer that switched to Go as the preferred language years ago, here are some of the things I appreciate on the other side of that fence: - Performance, indeed. - Static typing, yes. - A simpler language specification (a big one for me, game changer for large code bases in large teams) - Interfaces based on structural typing ("static duck typing", as some say) - Much better control of memory layout (struct with 2 int64s takes 128 bits in memory, a list of those takes N*128bits) - Built-in micro-threads (goroutines) - A runtime that schedules (means, you can block, despite concurrency) - B
Read the rest
uffered and unbuffered channels managed by the runtime (with select, etc) - Builds native static executables, fast (maybe you don't care, many people do) - A much better organized standard library - A very good http server _and_ client package in the standard library - Good crypto packages and APIs in the standard library - Error handling without exceptions (that's a pro for me and many, feel free to disagree) - A very elegant system to define access control (private/public) on vars/funcs/types/fields/consts/etc. - All names inside files that are part of a package ("directory") are part of the same namespace (allows better organizing code than with Python's file-is-a-module style) - Code files that can see declarations out of order (improves code organization) - gofmt! godoc! Love those. - None of the Python 2 => 3 migration mess (people are being told to program in a pseudo-language that is neither Python 2 nor 3 in recent times) And so on... That's not to judge your use of Python, though. By all means stick with Python if it suits your needs. As a last point, if you're interested in Qt bindings, I've been working on this: https://github.com/go-qml/qml Some applications coming out of it: http://blog.labix.org/2014/04/25/qml-contest-results
In Things from Python I'd miss in Go
Qt has shaped up to be such an attractive, pleasant-to-use framework. QML has turned out quite convenient, too. It's a pity that Qt's foundation remains a fundamentally memory-unsafe language like C++. I'm using a lot of languages now that offer significantly more safety, both memory and type (including OCaml, Golang, and playing with Rust). Even with the very welcome additions of C++11/14, it still seems like I'm stepping back into a previous era when I write C++. I use C occasionally, but when I do I know I'm manipulating memory directly, and if I'm not careful it can bite me. C++ has adopted so many modern language features that it's easy to forget it shares many of the same attributes as C, even if most of them are now avoidable with care and attention. One nice response to this dilemma is Niemeyer's go-qml (sponsored by Ubuntu, i
Read the rest
f I'm not mistaken). go-qml allows you to create your main Qt program in Go, leaving QML for the layout only. So no C++ at all (except under the covers, of course). I look forward to seeing how go-qml evolves [1]. 1. https://github.com/go-qml/qml
In Qt 5.3 Release Candidate Available

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.