Live data from Hacker News

Go fonts

blog.golang.org

171–180 of 182 posts

Re: Go fonts

#171
post #97

> What options for native UI does IDEA provide? It's mostly a Swing app. You're right; it's typical bullshit by JetBrains shills. Eclipse has SWT with native UI widgets and IntelliJ is and will always be a sloggy Swing application.

You can't make baseless accusations of shillage here. We detached this flagged subthread from https://news.ycombinator.com/item?id=12975014.

Re: Go fonts

#172

I just got this set up on a Linux system and I think these fonts are absolutely fantastic. This is the only "programmer's font" I've tried that was ever any good.

I like them but they won't be replacing PragmataPro which has ligature support and works in everything I use, is nicely condensed without feeling cramped and is just beautiful to look at. Screenshots: http://imgur.com/a/tiE76 first image is Pragmata second Go font, no contest for me.

I used to use Pragmata, but have since switched to Iosevka. It's similar in width and also supports ligatures.

Re: Go fonts

#173

This reminds me of Java applications that you can immediately tell are Java because of the weird font. I don't see an advantage over using native system fonts. As far as I know you don't need a license to use fonts installed on the system running the application. Why does the font need to be bundled? The wide spread adoption of this is going to make go programs stick out like a sore thumb.

I don't respect the self-imposed "x-platform native UI experience" constraint anymore. Even windows slowly rebuilt its user interface and experience over the years. It isn't a user demand, it doesn't put any pressure on support, frankly I have no idea what these people who spread all this custom drawn vs native control polemic were thinking. Also, if you are making money, who cares if you drew some of your controls o…

Because then you will have an interface that has been goaded into acting and drawing like you want it to, instead of having an interface which looks and acts in ways which feel normal and familiar to users of the target platform.

Maybe you want that, as an app developer, but as a user I'd really like it if you'd stop, and I'm happy when the platform makes this sort of thing difficult.

Re: Go fonts

#174

This reminds me of Java applications that you can immediately tell are Java because of the weird font. I don't see an advantage over using native system fonts. As far as I know you don't need a license to use fonts installed on the system running the application. Why does the font need to be bundled? The wide spread adoption of this is going to make go programs stick out like a sore thumb.

You must notice they are building a new UI toolkit with opengl es backend. They apparently don't care about native system.

Re: Go fonts

#175

Earlier quoted context omitted.

I don't respect the self-imposed "x-platform native UI experience" constraint anymore. Even windows slowly rebuilt its user interface and experience over the years. It isn't a user demand, it doesn't put any pressure on support, frankly I have no idea what these people who spread all this custom drawn vs native control polemic were thinking. Also, if you are making money, who cares if you drew some of your controls o…

Because then you will have an interface that has been goaded into acting and drawing like you want it to, instead of having an interface which looks and acts in ways which feel normal and familiar to users of the target platform. Maybe you want that, as an app developer, but as a user I'd really like it if you'd stop, and I'm happy when the platform makes this sort of thing difficult.

What really changed my mind was the MLOC delphi application I maintain as part of my dayjob. People don't think "oh wow I wish this was a ctrl-v instead of shift-ins and what am I ever gonna do if this file dialog looks kinda weird and unfamiliar? and oh no, the context menu in this grid is actually a window with a handle and not the default menu that was originally intended by the win32 api gods? Give me cancer or give me death"

No, they just busily work X hours and go home. They only care about getting their job done and if that means getting used to the interface they do so. We actually have users who've been around for about 20 years and you should see how fast they can enter some of the stuff.

Re: Go fonts

#176

Earlier quoted context omitted.

Because then you will have an interface that has been goaded into acting and drawing like you want it to, instead of having an interface which looks and acts in ways which feel normal and familiar to users of the target platform. Maybe you want that, as an app developer, but as a user I'd really like it if you'd stop, and I'm happy when the platform makes this sort of thing difficult.

What really changed my mind was the MLOC delphi application I maintain as part of my dayjob. People don't think "oh wow I wish this was a ctrl-v instead of shift-ins and what am I ever gonna do if this file dialog looks kinda weird and unfamiliar? and oh no, the context menu in this grid is actually a window with a handle and not the default menu that was originally intended by the win32 api gods? Give me cancer or g…

Well, sure, employers are free to waste their employees' time and make their lives complicated in all sorts of ways; that's what the paycheck is for. So what? It's still a crappy way to design apps, and I'm not going to respect it just because people successfully get away with it.

Re: Go fonts

#177
post #81

Earlier quoted context omitted.

> I don't see an advantage over using native system fonts As touched on in the article, you need a standardized font you have control over for automated testing, to make sure you're getting reproducible results. OS fonts are too inconsistent for that. Now, why they couldn't use any of the literally hundreds of other open-source fonts instead that Google made…

> As touched on in the article, you need a standardized font you have control over for automated testing Why? Just standardize the font when running in test mode. I expect system applications to use my system fonts.

Yeah, that's the part where it stops making sense. System fonts are good enough for human consumption.

Re: Go fonts

#178
post #91
post #82

Earlier quoted context omitted.

Let's hope it won't be as ugly as the Java crap. Or Tk.

Do you mean the old Java crap, like https://netbeans.org/images_www/screenshots/platform/jmonkey... https://netbeans.org/images_www/screenshots/platform/nbAWSAd... https://netbeans.org/images_www/screenshots/platform/lg_soft... https://netbeans.org/images_www/screenshots/platform/GGSSEph... https://netbeans.org/images_www/screenshots/platform/platypu... https://netbeans.org/images_www/screenshots/platform/blueMar...…

Yes. Both look ugly and not even close to native.

Re: Go fonts

#179
post #91

Earlier quoted context omitted.

Do you mean the old Java crap, like https://netbeans.org/images_www/screenshots/platform/jmonkey... https://netbeans.org/images_www/screenshots/platform/nbAWSAd... https://netbeans.org/images_www/screenshots/platform/lg_soft... https://netbeans.org/images_www/screenshots/platform/GGSSEph... https://netbeans.org/images_www/screenshots/platform/platypu... https://netbeans.org/images_www/screenshots/platform/blueMar...…

Yes. Both look ugly and not even close to native.

On my Mac they look as close to native as any other app, which is to say that applications no longer have a uniform look anymore anyway. Chrome, Firefox, Twitter, my email client and all of my editors look no more "native" than modern Java apps like NetBeans or IntelliJ.
Post reply on HN