Go for Bash Programmers – Part Ii: CLI Tools

Posted4 months agoActive4 months ago

reisinge

131 points

9 comments

github.comTechstory

supportivepositive

Debate

10/100

Go Programming LanguageCLI ToolsLearning Resources

Key topics

Go Programming Language

CLI Tools

Learning Resources

A GitHub repository provides a tutorial on Go programming for Bash programmers, with a discussion praising its step-by-step approach and highlighting additional learning opportunities.

Snapshot generated from the HN discussion

Discussion Activity

Light discussion

First comment

Peak period

24-36h

Avg / period

1.5

Key moments

01Story posted
Sep 8, 2025 at 8:26 AM EDT
4 months ago
Step 01
02First comment
Sep 9, 2025 at 1:26 PM EDT
1d after posting
Step 02
03Peak activity
3 comments in 24-36h
Hottest window of the conversation
Step 03
04Latest activity
Sep 14, 2025 at 6:20 PM EDT
4 months ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (9 comments)

Showing 9 comments

everybodyknows

4 months ago

2 replies

> We named the package hello_test instead of hello. This is possible and it allows for writing tests that use only the public API (identifiers starting with a capital letter) of the tested package as a real user would.

Would be good to highlight here that *_test packages are the sole exception from Go's standard rule of one-package-only per source directory -- special cases being always an unfortunate additional heightening of the beginner's learning curve.

ttz

4 months ago

1 reply

You can also include

package main

files in a non-main package directory (usually sed when implementing go generate)

arp242

4 months ago

1 reply

What people usually do is add a build tag to the file(s) with package main, so they're not compiled on a regular compile/test run. But you can't combine them as such (and you can do this with any package name – there's nothing special about the main package here).

ttz

4 months ago

1 reply

Yep - my point was that _test is not the only exception to the "rule"

arp242

4 months ago

1 reply

No, there is no exception for the "main" package. It's just build tag trickery. You can do this with any package names (although it doesn't make much sense to do so).

ttz

4 months ago

Ah, I see what you're objecting to. Yes, it is build tag trickery, and wouldn't work without it

reisingeAuthor

4 months ago

Thanks, done: https://github.com/go-monk/from-bash-to-go-part-ii/commit/16...

pentaphobe

4 months ago

Nice! You packed in so many things which are often drip fed, and take folk a while to find

Kudos

mrbluecoat

4 months ago

I really like this style of showing steps that would be logical for those new to Go even if they're wrong then showing why it didn't work and walking through the fix. Nice linear progression of real-world learning.

View full discussion on Hacker News

ID: 45167436Type: storyLast synced: 11/20/2025, 2:24:16 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

Open link View on HN