My “author interview” for my book “Functional Programming in Go” is out! partnerships.packt.com/inter… 😁
And the book itself is also ready for pre-order on Amazon 😎packt.link/TFhFS
Just seen the new Dr Strange movie and I can’t help but wonder.. are there some serious fans of Mortal Kombat involved with this one? 😅 Definitely expected to hear a voice shout “Fatality!” In some fight scenes 😆
Generics.
Fuzzing.
Software Bill of Materials (go version -m).
Workspace mode (go.work file).
15% ARM64 performance improvements with register ABI.
Reduced garbage collection overhead with pacer improvements.
And so much more!
Go Go Go 1.18 #golang
“Go 1.18 Beta 1 is available, with generics” 🎉 🎉
— go.dev/blog/go1.18beta1
This is a huge step for Go, with a ton of work behind it. Thanks to everyone who helped us get this far. Huge thanks to the team here, who did a lot of heavy lifting.
– @_rsc#golang
Stepping away from a problem can be the best way to solve it... Late last night -> stuck on AoC day 14 for wayyy to long -> eventually decide that sleep is necessary.
Wake up -> open vim -> notice a bug on one line -> fix bug -> solve problem. 🤦♂️
Too lazy to even check array bounds on the _first_ AoC problem..
Just placing this at top of the "sliding window" function.. :-)
```
defer func() { recover() }()
```
AoC is definitely not the place for production code 😄
I worry about the bf2042 devs having a bad time with this release full of bugs.
In an industry where “crunch time” is pretty much normalized and w/ pressure from stakeholders, that just can’t be good for mental well-being.
And sadly I am quite sure devs were aware of the issues but pressured into a release anyway.
It doesn’t help that online they seem to catch a lot of the blame. Making software is hard enough without tight deadlines and long hours..