You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/posts/meetup-49-wrapup.md
+27-4
Original file line number
Diff line number
Diff line change
@@ -12,9 +12,10 @@ tags:
12
12
Hybrid Meetup #49 took place
13
13
[2025-03-25](https://www.meetup.com/leipzig-golang/events/305626247) 19:00 at
14
14
[CHECK24](https://www.check24.de/) Leipzig Office and we had a great
15
-
introduction to memory management with Go.
15
+
introduction to memory management with Go by [Fabian](https://www.linkedin.com/in/fabian-g%C3%A4rtner-913584141/).
16
16
17
-
Slides and quiz can be found at [mentimeter.com](https://www.mentimeter.com/app/presentation/alog8a9xsqj6hwbyi6t32m5qzh295rue/view?question=9bym8yfwp7c4).
Where does the name tailscale come from? From the 2013 Google paper [The tail
71
+
at scale](https://dl.acm.org/doi/pdf/10.1145/2408776.2408794).
72
+
73
+
> The long tail of products are never going to be that big [ie. as a
74
+
> hyperscaler]— almost everybody building almost everything doesn't have
75
+
> any of those problems. -- [Avery Pennarun](https://apenwarr.ca/log/) at [45:56...](https://www.buzzsprout.com/1822302/episodes/9890092-tailscale-with-avery-pennarun-brad-fitzpatrick)
0 commit comments