Movatterモバイル変換


[0]ホーム

URL:


Skip to main content
r/golang iconr/golang icon

r/golang

members
online
Best
Open sort options
Change post view

Community highlights

  • Who's Hiring - October 2025

    Jobs
    votes • comments
  • Small Projects - September 30, 2025

    Small Projects
    votes • comments
  • Frequently Asked Questions

    FAQ
    votes • comments

  • What's the best tool to build cross platform GUI in Go?
    What's the best tool to build cross platform GUI in Go?

    Hey folks, in your opinion what's the best tool to build GUI in Go?

    My current choice is Wails and it works well 99% of the time, but now that Topaz Labs decide to shift their products from one time payment to subscription, I decided to create an open source version of their products, starting with Topaz Photo AI (I know it's ambitious, but I think it can be done).

    However, AI apps are usually resource intensive and would like my app to have a more native look, instead of a web look. Is there anything you would recommend in this case?


    u/getsentry avataru/getsentry
    OfficialPromoted
    Nobody wants to be the developer known for causing production to break. Sentry AI Code Review is officially here.
    Nobody wants to be the developer known for causing production to break. Sentry AI Code Review is officially here.

    sentry.io
    Learn More

    my work colleagues use generics everywhere for everything
    my work colleagues use generics everywhere for everything

    god i hate this. every config, every helper must be generic. "what if we'll use it for–" no mate: 1. you won't 2. you've made a simple type implement a redundant interface so that you can call a helper function inside another helper function and 3. this function you've written doesn't even need to use the interface as a constraint, it could just take an interface directly.

    i keep having to review shit code where they write a 6 line helper to avoid anif err != nil (now the call site's 4 lines, good riddance god help). it's three against one and i'm losing control and i'm pulling my hair out trying to understand wtf they want to do and the only way to convince them we can do without is if i rewrite what they did from scratch and let them see for themselves it's just better without the shit load of abstraction and generic abuse.

    don't even get me started on the accompanying AI slop that comes with that.

    how can i convince my colleagues to design minimal composable abstractions which actually fit in the current codebase and not dump their overly engineered yet barely thought out ideas into each file as if it was an append only log? i'm tired of rewriting whatever they do in 30-50% less lines of code and achieving the same thing with more clarity and extensibility. i wish numbers were hyperbolic. in fact, they're underestimating.


    Ebitengine v2.9.0 Released (A 2D game engine for Go)
    Created Nov 11, 2009
    Public

    Anyone can view, post, and comment to this community

    144K1.4K

    r/golang Rules

  • 1

    Be friendly and welcoming.

  • Post is not in keeping with an inclusive and friendly technical atmosphere.

  • 2

    Be patient.

  • Remember that people have varying communication styles and that not everyone is using their native language. (Meaning and tone can be lost in translation.)

  • 3

    Be thoughtful.

  • 4

    Be respectful.

  • In particular, respect differences of opinion.

    Do not include "engagement hooks", like exhortations to subscribe to some channel or redundantly asking what others think.

  • 5

    Be charitable.

  • Interpret the arguments of others in good faith, do not seek to disagree. When we do disagree, try to understand why.

  • 6

    Be constructive.

  • Avoid derailing: stay on topic; if you want to talk about something else, start a new conversation. Avoid unconstructive criticism: don't merely decry the current state of affairs; offer - or at least solicit - suggestions as to how things may be improved. Avoid snarking (pithy, unproductive, sniping comments) Avoid discussing potentially offensive or sensitive issues; this all too often leads to unnecessary conflict. Avoid microaggressions Do not post "Ask an AI"

  • 7

    Be responsible.

  • What you say and do matters. Take responsibility for your words and actions, including their consequences, whether intended or otherwise.

  • 8

    Follow the Go Code of Conduct

  • As a part of the Go community, this subreddit and those who post on it should follow the tenets laid out in the Go Code of Conduct:https://golang.org/conduct

    Treat everyone with respect and kindness. Be thoughtful in how you communicate. Don’t be destructive or inflammatory.

  • 9

    Must be Go Related

  • Posts must be of interest to Go developers and related to the Go language.

    This includes:

    • Articles about the language itself

    • Announcements & articles about open source Go libraries or applications

    • Dev tools (open source or not) specifically targeted at Go developers

    We ask that you not post about closed-source / paid software that is not specifically aimed at Go developers in particular (as opposed to all developers), even if it is written in Go.

  • 10

    Do Not Post Pirated Material

  • Do not post links to or instructions on how to get pirated copies of copyrighted material.

  • 11

    Job Listings Go in the Who's Hiring? Post

  • We have a monthly "Who's Hiring?" post that will stay pinned to the top of the subreddit. To avoid too much noise from companies, please post job openings there. Please keep in mind, this is for 1st party postings only. No 3rd party recruiters.

  • 12

    AI Policy

  • No GPT or other AI-generated content is allowed as posts, post targets, or comments. This is only for the content itself; posts about GPT or AI related to Go are fine.

    Posts of projects havedifferent rules.

    As it is not easy to determine what is and is not AI, posts will be removed based on their appearence.


    Moderators

    View all moderators

    [8]
    ページ先頭

    ©2009-2025 Movatter.jp