Live data from Hacker News

Go + gxui: Rendering native app GUIs on any platform?

github.com

41–45 of 45 posts

Re: Go + gxui: Rendering native app GUIs on any platform?

#41
post #40
post #38

Earlier quoted context omitted.

But that's not the sense that "native GUI" has ever had. Widgets are only part of the picture, regardless -- a GUI is defined by the layout, behavior, interaction model, and widgets.

[deleted]

No, nothing at all is native. That it's rendered in GL doesn't make it native. It uses a cross-platform events layer, which is by definition non-native.

Re: Go + gxui: Rendering native app GUIs on any platform?

#42
post #41
post #40

Earlier quoted context omitted.

[deleted]

No, nothing at all is native. That it's rendered in GL doesn't make it native. It uses a cross-platform events layer, which is by definition non-native.

> cross-platform != native

Best not tell that to the Qt devs ;)

Anyway, this argument is ridiculous because all my point was, is that this project only means "native GUI" in the sense that it's a GUI that runs without an intermediate rendering engine (ie web browser). I was just trying to defend an interesting project against the hoards of negative semantic-Nazi's. I get rather sick of the poisonous attitude some have towards other peoples hard work so felt it was only fair to offer a counter argument defending it. But I did so forgetting just how vehemently opinionated many are and now really wish I hadn't bothered because this argument has spiralled well beyond the original point.

Sure, in an ideal world this project would be using vendor APIs rather than OpenGL - but this does actually work and is pretty damn cool, even if it is a bit of hack. And if we're honest, isn't hacking meant to be the point of this forums? Or is this community now just a place for intelligent people to belittle other intelligent people?

Honestly, sometimes I just sigh at the number of pot-shots people make on here and how it's now become the acceptable norm. I'm sure it wasn't like this when I first joined.

Re: Go + gxui: Rendering native app GUIs on any platform?

#43
post #31

Earlier quoted context omitted.

[deleted]

What can be done and what's actually done are two very different things. Fully replicating something as simple as a button can be very hard. Its look depends on the OS, OS version, OS theme, OS scaling setting, OS font settings, the language (left-to-right, right-to-left). It has to support all kinds of OS accessibility hooks. It has to support all kinds of input devices. It has to follow the tab-focus rules. These a…

Which is exactly the point I made as well (several times in fact). So thank you for finally agreeing with me on something.

Re: Go + gxui: Rendering native app GUIs on any platform?

#44
post #42
post #41

Earlier quoted context omitted.

No, nothing at all is native. That it's rendered in GL doesn't make it native. It uses a cross-platform events layer, which is by definition non-native.

> cross-platform != native Best not tell that to the Qt devs ;) Anyway, this argument is ridiculous because all my point was, is that this project only means "native GUI" in the sense that it's a GUI that runs without an intermediate rendering engine (ie web browser). I was just trying to defend an interesting project against the hoards of negative semantic-Nazi's. I get rather sick of the poisonous attitude some hav…

I'm sorry you felt that the responses were hostile, that certainly wasn't my intent. Mood is awfully tough to get right on a bulletin board.

Speaking only for myself, I feel that words are very powerful, and that it's important for us to be precise in usage. I certainly didn't mean to denigrate this project, or the talented folks behind it.

Re: Go + gxui: Rendering native app GUIs on any platform?

#45
post #44
post #42

Earlier quoted context omitted.

> cross-platform != native Best not tell that to the Qt devs ;) Anyway, this argument is ridiculous because all my point was, is that this project only means "native GUI" in the sense that it's a GUI that runs without an intermediate rendering engine (ie web browser). I was just trying to defend an interesting project against the hoards of negative semantic-Nazi's. I get rather sick of the poisonous attitude some hav…

I'm sorry you felt that the responses were hostile, that certainly wasn't my intent. Mood is awfully tough to get right on a bulletin board. Speaking only for myself, I feel that words are very powerful, and that it's important for us to be precise in usage. I certainly didn't mean to denigrate this project, or the talented folks behind it.

To be honest, I think a lot of my frustration is that I don't actually disagree with most of the points being raised, but I'd back myself into the position of playing devils advocate. I mean, I do think they way this submission was described as "native app GUI" is acceptable because it's also pretty clear that it's in the context of using OpenGL in place of HTML and thus it's just a concise / terse / lazy / whatever way of saying "renders natively on device" (summarising git repositories and titling them can be a deceptively hard job after all). But I can also understand why people would nitpick the semantics of that title; and had the context not been clearer (ie the project was a little more opaque about it's usage of OpenGL) then I likely wouldn't have defended it's usage.
Post reply on HN