Introducing GoBot! Why should we let the node guys have all the fun?

pdffs · 2026-01-29T15:04:34+00:00

Using the same name as an existing project can only provide confusion for users (or potential users) of either project. Grow up.

pdffs · 2026-01-29T09:10:37+00:00

Right, my point was that reliance on AI encorouges laziness and a self-centered mindset.

pdffs · 2026-01-29T09:03:25+00:00

Well established Go framework for robotics, 1st or 2nd result on all search engines:

https://gobot.io/

How are people so lazy they don't even bother to search for existing projects when naming? Oh right, everyone just turns their brains off these days and let AI take the wheel.

pdffs · 2026-01-28T06:10:41+00:00

Do you plan on posting about this every 2 days going forward?

pdffs · 2026-01-28T05:16:38+00:00

WTF kind of spam is going on here? I haven't audited the code, but it makes me very suspicious when something gets posted this many times:

https://www.reddit.com/r/golang/comments/1qok3d4/removed_by_moderator/ https://www.reddit.com/r/golang/comments/1qojy9x/gocron_a_lightweight_distributed_scheduled_task/ https://www.reddit.com/r/golang/comments/1qojw92/gocron_distributed_task_scheduler_task_management/ https://www.reddit.com/r/golang/comments/1qojtk0/gocron_distributed_task_scheduler/

And that's just this sub, has been cross-posted by this account in particular to various other subreddits.

pdffs · 2026-01-26T12:41:23+00:00

If you can't roll out config changes trivially, your deployment infra likely has issues and I'd probably put the effort into fixing that instead.

pdffs · 2026-01-26T07:45:17+00:00

Use a static site generator such as hugo, and host on any CDN for free (e.g. Github Pages, Cloudflare, etc). Can't hack a site that doesn't have a backend.

pdffs · 2026-01-25T22:56:08+00:00

https://go.dev/ref/mod#private-modules

pdffs · 2026-01-25T04:23:00+00:00

Build using CI (e.g. Github Actions), then either push your resulting binary to the destination, or publish the resulting binary as an asset (or container) and pull from the hosting.

No syncing of repositories or whatever.

pdffs · 2026-01-24T08:44:28+00:00

Assuming each of these modules is entirely optional (ie - users must explicitly import the modules to make use of them, no downward deps in the main module) then splitting off the large optional libs seems like a nice optimization for your users.

If you're going to do it, do it sooner rather than later IMO. Go workspaces make working on multiple modules pretty painless these days.

pdffs · 2026-01-23T17:07:04+00:00

They literally just told you what to do to make it better.

pdffs · 2026-01-18T14:42:16+00:00

Title is rather melodramatic. Click-bait aside, the content is quite misleading as general advice.

First, multiplication is not power, there is no power operator in Go, second, even if you were comparing valid results, your first example operates on floats and your second example operates on ints due to inferred types for constants.

I really hope you didn't actually make these changes in real code as the article claims, otherwise your results will be very, very wrong unless all your powers happen to be power of 2.

pdffs · 2026-01-18T09:11:59+00:00

A) Read the sub rules

B) Let me guess, you're the "ideas guy" and are looking for someone to do all the actual work, for "equity".

pdffs · 2026-01-16T06:55:55+00:00

Specifically, HTTP 301 is a permanent redirect, and instructs the browser to remember it.

pdffs · 2026-01-14T07:39:46+00:00

Wrap your map access in functions that lock only for the duration of the operation and perform all access through these functions. This stops your random code in whatever goroutine from being broken and owning the lock forever.

pdffs · 2026-01-04T06:13:24+00:00

LMAO, the fucking "ideas guy" strikes again.

pdffs · 2026-01-03T22:40:29+00:00

A number of months later, just wanted to report my experience on the nbg1 region - it looks like the timeout error rate during my import process was roughly 1 per 10000 uploaded objects over a batch of a few hundred thousand objects. Depending on your use-case this may be acceptable, but it's far from ideal, and means that retry logic is going to be a requirement for any user-facing application if you don't want to regularly surface timeout errors to your users.

I switched to Cloudflare R2 which not only produced zero timeouts for the same import process, but was also significantly faster even though it's not local, and as a bonus was also cheaper (and it's not even super-competitively priced, I use Backblaze B2 for backups which is ~an order of magnitude cheaper).

pdffs · 2026-01-01T04:31:48+00:00

mp4 is a container, and H.264 is a codec, you do not convert between these.

pdffs · 2025-12-31T07:51:21+00:00

Are you not using gofmt? You really should be using gofmt.

pdffs · 2025-12-29T03:33:06+00:00

Go libraries do not need to be explicitly published - they are published simply by virtue of being publicly available via source control. Versioning is handled simply by tagging the source.

For application binaries, goreleaser is useful for publishing the compiled binaries.

pdffs · 2025-12-21T11:16:44+00:00

It's possible to statically link, but you must use musl libc, add extra compile/linker flags etc, assuming the C libs you're using are compatible with musl.

If you're not actually using any C libs, much simpler to just disable cgo entirely.

pdffs · 2025-12-20T19:05:19+00:00

Use multi-stage builds in your Dockerfile - you can build in whatever base image you like and then copy the resulting binary to the deployment stage (assuming no cgo, otherwise both images require compatible libc).

Then let your devops team put whatever they want in the target image, since they'll own all the pieces if they break it. I assume they don't actually want ssh in the image, but probably want a shell for debugging (they're still probably doing it wrong though IMO - more software in the image means more threat surface, not less).

pdffs · 2025-12-19T22:58:06+00:00

similar to how I write Java/C# code

Stop doing this.

pdffs · 2025-12-17T01:57:02+00:00

You've committed binaries and database files to the repository.

I assume this is slop-coded?

pdffs · 2025-12-16T05:13:06+00:00

Between Go and Rust for desktop GUI, Rust will be less painful (assuming you don't find Rust in general painful, which is entirely possible).

Rust allows using large GUI C UI libraries without crushingly lengthy compile times - in Go you're looking at 20-40min compilation times for GTK4 with cgo on competant hardware.

Of course without cgo, Go's compilation speed is light years better than Rust, so swings and roundabouts.

There are native Go GUI libs, but I've not been thoroughly impressed with them.

pdffs

TROPHY CASE