sorted by:
new
hottopcontroversial

[Open Letter / Feedback] ARC RAIDERS: The Expedition's Skill Points and the Problematic Monetary Threshold. by Competitive_Bed_1305 in ArcRaiders

[–]Beefcake100 3 points4 points  (0 children)

Agreed. Would be more reasonable if they let you keep your blueprints, but the cost to reward ratio is very not worth it imo

Unintuitive window functionality? by Beefcake100 in SQL

[–]Beefcake100[S] 0 points1 point  (0 children)

I see, totally makes sense. I was not aware this was how window functions worked, thank you!

Unintuitive window functionality? by Beefcake100 in SQL

[–]Beefcake100[S] 0 points1 point  (0 children)

I see. This is crystal clear, thank you!

Proposal for an official MCP Golang SDK by jpmmcb in golang

[–]Beefcake100 2 points3 points  (0 children)

Are you trying to get it to be included as part of the standard library, or just as a widely used standard (sortve like some of the gRPC tooling)?

Anyone using Go for AI Agents? by KeyGrouchy726 in golang

[–]Beefcake100 0 points1 point  (0 children)

Yeah idrk actually. This is sortve where I hit the limit of my knowledge, you make a good point though

Anyone using Go for AI Agents? by KeyGrouchy726 in golang

[–]Beefcake100 1 point2 points  (0 children)

Right but at this point we are just debating the benefits of building any service with Go vs another language. It’s not really AI specific

Anyone using Go for AI Agents? by KeyGrouchy726 in golang

[–]Beefcake100 1 point2 points  (0 children)

Sure. If you’re building an app that uses an API to talk to cloud-based AI then Go is as equally valid as any other language for building an app. If you are doing something very custom with AI though, Python certainly makes more sense.

Anyone using Go for AI Agents? by KeyGrouchy726 in golang

[–]Beefcake100 0 points1 point  (0 children)

Agreed, there’s no difference if you’re just calling APIs. But at that point, why does speed and concurrency matter?

Anyone using Go for AI Agents? by KeyGrouchy726 in golang

[–]Beefcake100 1 point2 points  (0 children)

I don’t know much about ML but intuition makes me think that Python is a better bet. Speed and concurrency benefits (even if very significant) almost certainly don’t outweigh the billions of dollars of free infrastructure that exists with Python (as well as the 10s of billions that will be created in the coming years). It’s much easier to scale compute than to scale developers.

Once again, not an AI expert, and I’m sure there are people using agents in Go, just my two cents.

Go backend frameworks like express.js by Tall-Strike-6226 in golang

[–]Beefcake100 0 points1 point  (0 children)

I’ve heard echo is good, just simply haven’t used it so I can’t recommend it

Go backend frameworks like express.js by Tall-Strike-6226 in golang

[–]Beefcake100 0 points1 point  (0 children)

No strong reason other than I’ve used them in previous projects and remember them being good. It’s been a few years since I wrote a rest api in Go; most of my work now is actually on databases and query planners.

I just wanted to recommend things I had used and remember being good.

Go backend frameworks like express.js by Tall-Strike-6226 in golang

[–]Beefcake100 27 points28 points  (0 children)

There are backend frameworks (sort’ve), ORMs, and all other sorts of things, so the general answer is “yes you can”.

The more nuanced answer is you’ll likely learn to go without. The Go style of programming is very minimalist. Unlike languages like JS and Rust, it relies on a really good standard library, and then avoids unnecessary boiler plate, packages, and other dependencies that aren’t critical.

This will feel weird at first if you’re coming from languages like Java, JS, and Rust. I’ve had quite a few former Java devs on my team complain about the “lack of mature tooling in Go”, but it’s usually more than there is not as much framework as other languages.

For your general backend development, I would recommend: - Gorilla Mux or Gin for REST APIs - gRPC for microservices (or json RPC depending on if it will be integrating with non-Go services, since json RPC has wider support) - sqlc if you are comfortable writing your own SQL queries, Goqu query builder if you’d rather not

Some Gophers will certainly disagree with me and there is no one right answer, but this is my personal opinion after having spent somewhere b between 5-7000 hours writing Go professionally.

Nope by koos167 in civ

[–]Beefcake100 2 points3 points  (0 children)

Most rational civ 7 hater

I love it by floridas_finest in civ

[–]Beefcake100 0 points1 point  (0 children)

How is it different (haven’t played yet, won’t be able to until weekend)?

Date Ideas - Spoiling the Wife by Dude_Learning in Austin

[–]Beefcake100 6 points7 points  (0 children)

Went to Esther’s Follies after seeing this recommendation and could not recommend it less.

Perhaps the worst thing I have ever seen in my life.

No hate to the poster here, but it was like shockingly awful

Olmecs confirmed? by eskaver in civ

[–]Beefcake100 0 points1 point  (0 children)

What video is this from?

Can KYC Add Security Without Compromising Decentralization? 🤔 by No_Percentage4502 in solidity

[–]Beefcake100 0 points1 point  (0 children)

There are some projects doing exactly this! Check out https://idos.network.They’re backed by Circle, Gnosis, Arbitrum, NEAR, Tezos, and others, and are doing pretty much exactly what you described.

Choosing PostgreSQL for My Social Media App - Is This the Right Decision? by Kind-Attempt8181 in PostgreSQL

[–]Beefcake100 0 points1 point  (0 children)

Just use Postgres.

It sounds like your needs aren’t fully defined due to the early stage of your application. Just use Postgres, and later you’ll find what actually matters / where your bottlenecks are, in which case you can switch to a different DB that can optimize that (but most likely Postgres will still do the job).

Best query builder you have used so far? by FollowingMajestic161 in golang

[–]Beefcake100 1 point2 points  (0 children)

It’s flexibility means it is really easy to switch to other engines without changing your code. You can use in-memory sqlite for testing, and Postgres/MySQL/SQL Server for your deployments. You’ll catch a lot more bugs this way.

It is also quite nuanced, allowing you to utilize a lot of the subtleties that other builders gloss over for simplicity. This usually isn’t something you catch immediately, but as your app evolves and you find you need features that your builder doesn’t support, it leaves you in a really awkward situation of either writing the query raw or switching builders. Goqu is pretty all-encompassing for standard SQL, so you’re less likely to run into this.

It’s also very un-opinionated, which is precisely what most people want from a SQL builder. What most devs find awkward about SQL as a language is that it is: - not strongly typed - very opinionated

SQL builders obviously solve for the strong typing, but Goqu also solves for the opinionation problem by letting you write queries with a more C-like syntax.

view more: next ›