and my favourite vertical shots

#photographer #streetphotography #photography

not anymore

same

@labeler.urbanism.plus listcommands

@labeler.urbanism.plus label

respectfully disconnect your life support

when we tried powering on this board for the first time before the rgh3, it would short the PSU and my first guess was an issue with the capacitors being fucky (i had suggested removing one of the most obvious leaky caps, which we did but to no success). Weeks another cap had turned into this.

the drive labels did not deceive you, two of those really are connected via usb3 and prayers

in my head i can hear the first couple seconds of the lego island intro *le- le lego, le- le- lego -go*

also i meant to say GC, not GCI

yeah JVM perf. and esp. resource uses is just catastrophic. Go solves a real problem, I mean that's why Google engineers build it in the first place. They were deep in the JVM full-stack space and with the shift to a more client-sided web with angularjs, a faster backend solution had to come about.

If you use it for what it was intended to be used for: building fast server apps and services, you'll find that using Go isn't really complicated and fairly fun.

Also if err != nil return err, isnt that bad. I tend to do if err != nil return fmt.Errorf("myprefix: %w", err). Helps with debugging ngl