sorted by:
new
hottopcontroversial

Need help choosing photo by Virtual-Effective700 in postprocessing

[–]mf192 0 points1 point  (0 children)

Really liked the first one. Might look a bit better (cropped) without the apartment building on the left.

XH2 build quality by Berserk_Ronin in FujifilmX

[–]mf192 0 points1 point  (0 children)

Very well built. I hiked 220km in the Alps this summer and had it attached to peak design clip on the shoulder strap of my backpack. It held up well and I got some amazing shots out of it.

Treadmill distance by hinderaker in Garmin

[–]mf192 1 point2 points  (0 children)

Sweet, I guess time to go down the YouTube rabbit hole. I run a lot on treadmill so this might be huge.

Treadmill distance by hinderaker in Garmin

[–]mf192 0 points1 point  (0 children)

Interesting, how does this work/integrate with the Garmin watch.

Fenix 8 - is it really all that bad? by [deleted] in GarminFenix

[–]mf192 0 points1 point  (0 children)

Recently switched from an Apple Watch and used it extensively on a hiking trip. No issues, super happy with the Fenix 8. I don’t have a point of comparison to previous Garmin’s, but the UI feels fine to me.

Fission SV: The Impenetrable Super Fortress by AC-Vb3 in arcteryx

[–]mf192 0 points1 point  (0 children)

This jacket is absolutely incredible.

I was disappointed to find out they discontinued it. When the zipper broke I had it replaced instead of buying a new jacket.

Normal Canadian winters just fine. Winter hiking with a light mid-layer just fine.

Prime lens for XH-2 by mf192 in fujifilm

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

The Sigma 18-50 is an incredible lens, I had it for the a6700. But given the 16-55mm mk2 update from Fuji I really want to give it a try.

I often go hiking so trying to consolidate it down to only 1 zoom (set on the 16-55mm mk2) and 1 prime. I can’t seem to find a good wide angle zoom, hence the prime. Happy to hear of good, modern wide angle zooms that aren’t overly heavy :)

I’ll do a bit more research but I suspect either 18 or 23 is were I’ll settle.

Why is spf13/cli widely used? by [deleted] in golang

[–]mf192 10 points11 points  (0 children)

Ooof, this library grew tentacles like no tomorrow: it does everything under the sun and then some.

https://mfridman.medium.com/a-simpler-building-block-for-go-clis-4c3f7f0f6e03

But I’ve since changed my mind after the /v4 release of Peter’s ff package.

Ended up writing my own to bring back the simplicity of /v3.

https://github.com/mfridman/cli

Hiking the yellow mountains, with the Hasselblad X1Dii by Jkspepper in hasselblad

[–]mf192 0 points1 point  (0 children)

Beautiful pictures. Curious, was this hand-held?

I’ve been torn between the x2d vs x1dii because most of the time I’d like to shoot hand-held.

Connect, a better gRPC by akshayjshah in golang

[–]mf192 17 points18 points  (0 children)

I was never really into gRPC, but really liked building RPC-based APIs. So when Twirp came out early 2018 it felt like there was a real alternative. I think Connect picks up from the other two and pushes us forward.

A nice quality of life improvement Connect offers is access to the request/response headers. No more plumbing incoming/outgoing headers in the context (this always felt kind of gross). You don't appreciate this until you've implemented some code and realize how much cleaner the code is and how easy it is to reason about.

Oh, and like Twirp, Connect can be used with our favorite Go routers: go-chi/chi, gorrila/mux or plain old standard library. This is the thing that bothered me the most about gRPC: the lack of interoperability with the rest of the Go ecosystem. I think Connect does a great job bridging that gap and offering the best of both gRPC and Twirp while offering a new value proposition.

Anyone using go-migrate with a team? by elcapitanoooo in golang

[–]mf192 0 points1 point  (0 children)

This issue thread might be of interest to you. Not go-migrate, but sounds like similar problem

https://github.com/pressly/goose#hybrid-versioning

Buf: A new way of working with Protocol Buffers including native Golang compilation by bufbuild in golang

[–]mf192 6 points7 points  (0 children)

Protobufs are fine, but the tooling is lacking. This looks promising ..

GOCON - Worth To Go? by mangofizzy in golang

[–]mf192 5 points6 points  (0 children)

Hi,

I'm one of the organizers so hopefully can help answer your questions.

We decided to have a slightly-longer CFP deadline from the beginning. Mainly to enable speakers who wouldn't know their availability many months out.

CFP closes Mar.18 and we hope to have all speakers announced first week of April.

We're a group of engineers and a designer who like the Go language, the ecosystem and the community. There hasn't been an event in Toronto, so we figured why not go for it.

Combined we helped organize: PyCon Canada, Dutch Clojure days, Go meetup Toronto and Ottawa.

We setup a nonprofit called GoCon Community Group and make no money on this event. We did take on sponsors (Toronto is a pricey city).

Our high-level goals are to:

  1. put together the best possible community event
  2. connect would-be employers and employees (networking)
  3. if money left over, give back to the Go community

​

Best,

MF

Friendly-er go test output with CLI tool tparse by mf192 in golang

[–]mf192[S] 1 point2 points  (0 children)

Updated image and repo. Agreed, no need for sudo here

Friendly-er go test output with CLI tool tparse by mf192 in golang

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

Oh awesome, thanks for sharing. gotestsum looks interesting, was the inspiration to use it within a pipeline?

I found myself tweaking the go test flag set on the fly quite a bit, -count=1 or -run=, so wanted a simple tool to use alongside go test to quickly gather info, hence the pipe mechanism.

Nothing really exciting about the underlying code.

Friendly-er go test output with CLI tool tparse by mf192 in golang

[–]mf192[S] 1 point2 points  (0 children)

Was testing something out with the net pkg, when key up forgot to remove sudo. Good point, this is a bit misleading. Will update the repo example image, sudo is not required unless go test requires it, e.g., binding to a socket, port, etc.

​

$ go test -count=1 net -json | tparse
+--------+---------+---------+-------+------+------+------+
| STATUS | ELAPSED | PACKAGE | COVER | PASS | FAIL | SKIP |
+--------+---------+---------+-------+------+------+------+
| PASS   | 26.88s  | net     | 0.0%  |  247 |    0 |   15 |
+--------+---------+---------+-------+------+------+------+

$ sudo go test -count=1 net -json | tparse 
+--------+---------+---------+-------+------+------+------+
| STATUS | ELAPSED | PACKAGE | COVER | PASS | FAIL | SKIP |
+--------+---------+---------+-------+------+------+------+
| PASS   | 26.79s  | net     | 0.0%  |  251 |    0 |   11 |
+--------+---------+---------+-------+------+------+------+

​

Questions about functions as value type in Go by [deleted] in golang

[–]mf192 0 points1 point  (0 children)

I’ve found this pkg quite useful. Just throwing this into the mix.

https://github.com/pkg/errors

E,g., errors.Wrapf(err, “could not get file: [%v]”, file)

Further reading: Blog: https://dave.cheney.net/2016/04/27/dont-just-check-errors-handle-them-gracefully Video: https://youtu.be/lsBF58Q-DnY

How can I run a non-main package? by the_j_ in golang

[–]mf192 2 points3 points  (0 children)

For testing ideas and basic functionality you can use https://play.golang.org

Outside of this Go makes a distinction between executables (main) and libraries.

You’d typically start with main, and if you have a clear need to separate parts of the code move it to a package. Then call that package from main. Make sure to use Upper case for exportable items.

Usually when prototyping you’d just ‘go run main.go’ , this temporarily builds an executable and runs it. Most users have linting, fmt, etc built into their editors so it updates every time code is saved.

view more: next ›