im_dario

Amazing project! The only thing I'm missing is able to list the filtered companies as a list. But then it wouldn't be a map, I know.

It looks like some borrowed Go convention, where package statements don't need to be quoted, but import statements may include URLs and, therefore, they are expected to be quoted.

I remember it took a me a bit of investigation to make Ruby call Go functions, but it wasn't really hard: https://dario.cat/en/posts/portal-between-ruby-and-go/

The argument about FFI and CGO was the most unappealing to me. If you really need to do that, it feels that at some point some decisions were made that weren't the right fit for the project.

Also, I feel that many arguments in the article are potential pitfalls for unintended side effects I've experimented in other languages, like Ruby itself. Keyword arguments are nice, but I know that they've bitten me several times.

Go forces the developer to be explicit about their intentions, that's why I also don't find something bad that your struct functions need to have the pointer receiver. It can be annoying when you forget, but that's what linters are for.

> What distinguishes a Go project from any other programming language?

My experience with Go, as user and open source maintainer, is that many libraries just work even if untouched for several years.

There is a culture around building small libraries, with minimal usage of dependencies beyond the standard library. This leads to most CVEs existing in the standard library, which combined with Go's commitment to backward compatibility, makes improving your security posture by just upgrading the toolchain.

I've been using Logseq as a work journal and it works great. Hashtags help me to track what I need to do and what I've done.

I got a 3-character domain, rio.hn, just to spell my name as an e-mail (using the @ as 'a' :)

Real estate is baby boomers and older millennials (as they inherited from their parents) "cryptocurrency" (as speculative asset). They HODL it to manufacture scarcity.

Just for reference, in a small city (40K people, 8 sq. km.) you can find 2K empty properties out of the market because it's more profitable to wait prices to raise.

I don’t know where are you located, but I’d avoid voting based on “this party won’t get a seat”.

Voting for a party is a signal for other people and for the party itself. It may not be today but next time that they get that seat.

I experimented a little with NanoVMs. I wanted to deploy them in AWS ARM64 instances to test if it was possible. It took a bit of effort, but I think it's worth it.

There is something nice about them as your mental map is reduced to the minimum amount of components, your app - amalgamated with the unikernel - and the virtualization platform of your choice.

I need to test support for volumes, and if there is interest I might do a write-up about it.

Google Wave, some of us don't forget you.

No "compiler assistance" doesn't mean no assistance at all. There is a growing set of linters based on the community-accepted analysis package [0] that prevent this and other gotchas that Go devs may be prone to.

It isn't a perfect solution, but it works at community level without needing to wait for the Go team to take care of or changing the language/toolchain.

0: https://pkg.go.dev/golang.org/x/tools/go/analysis

I wrote too (and still maintain) a SSG, it's a fun exercise: https://github.com/darccio/zas

Telemetry is opt-in [0], it shouldn't be a concern.

[0] https://research.swtch.com/telemetry-opt-in

Just asking ChatGPT to proofread a text is enough.

I’ve used for different languages and native speakers didn’t tell it was written by a non-native neither an IA.

It doesn’t really use Git, but it has Git semantics. They borrowed some basic concepts (repository, commit, etc).

It can also be fixed by notifying about the superdelegate's vote to the people delegating to them, so they can override it if desired.

Shopify's devs are working on YJIT [0], a just-in-time (JIT) implementation on top of CRuby.

0: https://shopify.engineering/yjit-faster-rubying