https://blogtitle.github.io/authors/rob/ Recent content in Rob on Blog Title Hugo -- gohugo.io en-us Mon, 16 Dec 2024 22:19:23 +0100 https://blogtitle.github.io/go-advanced-concurrency-patterns-part-4-unlimited-buffer-channels/ Mon, 16 Dec 2024 22:19:23 +0100 https://blogtitle.github.io/go-advanced-concurrency-patterns-part-4-unlimited-buffer-channels/ Preface It’s been almost 6 years since I added to this series, but I thought it was time to resume working on it. Since “perfect is the opposite of done” I thought I would talk about a simple pattern that I haven’t covered yet. A couple of years ago I worked on a toy library to see if the new-ish generics proposal would finally allow to express some of the most common channel patterns in Go. https://blogtitle.github.io/lets-go-to-go2/ Fri, 07 May 2021 09:04:30 +0200 https://blogtitle.github.io/lets-go-to-go2/ Preface In my previous post I summarized the latest generics proposal for Go. In this post I’m gonna use it a bit, and misuse it a lot. The problem Sometimes I find myself writing code to run the same function in parallel with itself with different inputs, for example to process a batch of data. This is not super complicated code, but it’s not exactly straightforward and can sometimes be tricky to get right. https://blogtitle.github.io/go-generics/ Fri, 07 May 2021 05:54:36 +0200 https://blogtitle.github.io/go-generics/ Preface Go doesn’t have generics yet, but there is a proposal that looks promising, and this post refers to that. Here is a version of the playground you can use to try this proposal out if you want to experiment without installing any tools. Functions Converting a slice into a channel. This is not necessarily the most useful function but it’s a good and simple example: func chanFromSlice[T any](in []T) chan T { c := make(chan T, len(in)) for _, v := range in { c <- v } return c } Here you can see that this looks and feels like Go, with the only difference of the [T any] bit. https://blogtitle.github.io/go-safe-html/ Tue, 30 Jun 2020 13:03:31 +0200 https://blogtitle.github.io/go-safe-html/ Disclaimer: this is not an official Google post or communication, it is just me commenting on something that is now available. The Google infosec team just released the Go “safehtml” package. If you are interested in making your application resilient to server-side XSS you might want to adopt it instead of “html/template”. Migration to safehtml should be quite straightforward as it is just a hardened fork of the original html/template standard package. https://blogtitle.github.io/i-am-switching-to-js/ Wed, 01 Apr 2020 00:00:00 +0300 https://blogtitle.github.io/i-am-switching-to-js/ After 5 years of using Go I am finally moving on. Go has served me well and has been the best language I could have possibly used for the longest time, but it is now the moment for me to let it Go. Over time Go has not failed to show me its limitations and its issues, to the point where I decided to switch to something more future proof and with a more thriving community. https://blogtitle.github.io/sneaky-race-conditions-and-granular-locks/ Wed, 11 Dec 2019 09:33:58 +0100 https://blogtitle.github.io/sneaky-race-conditions-and-granular-locks/ Race conditions are the main problem you have to care about when writing concurrent code. Go provides high level primitives that make it easier to get concurrency and parallelism right, but those are often times not enough. This is one of the reasons why Go has a race detector. You should always run your tests and, where possible, a portion of your production fleet with -race enabled. Beware that this might still not be enough: the detector only triggers when a race manifests and not all races are detected by it. https://blogtitle.github.io/go-advanced-concurrency-patterns-part-3-channels/ Thu, 05 Dec 2019 20:07:04 +0100 https://blogtitle.github.io/go-advanced-concurrency-patterns-part-3-channels/ Edit (16 Dec 2024) This post is still here for historical reasons, but it’s now quite old. The sync package has evolved since then and some primitives have become available. While all the channel and select semantics have stayed the same, please consider this as a post on how to better understand channels semantics rather than documentation or replacement for the sync package. Previous Post Today I’m going to dive into the expressive power of Go channels and the select statement. https://blogtitle.github.io/robn-go-security-pearls-cross-site-scripting-xss/ Wed, 11 Sep 2019 23:23:40 +0200 https://blogtitle.github.io/robn-go-security-pearls-cross-site-scripting-xss/ This post is part of my developer-friendly security series. You can find all other posts here. XSS is a vulnerability that allows attackers to run arbitrary JavaScript code in applications they shouldn’t be able to control. This can lead to complete account compromises for every victim that follows a malicious link or visits a compromised page. There are two major families of XSS: server side and client side. https://blogtitle.github.io/robn-go-security-pearls-fundamentals/ Thu, 05 Sep 2019 12:25:40 +0200 https://blogtitle.github.io/robn-go-security-pearls-fundamentals/ Welcome to this introductory series on web security. I’ll use simple snippets and hands-on examples to introduce fundamentals on the topic. Most server-side code will be in Go but you’ll be able to understand it if you know any C-like language. This first post is about the fundamentals: URI, HTTP, TLS, HTML, escaping and cookies. If you are already familiar with those concepts please feel free to skip to the next post. https://blogtitle.github.io/using-javascript-sharedarraybuffers-and-atomics/ Fri, 22 Mar 2019 12:42:05 +0100 https://blogtitle.github.io/using-javascript-sharedarraybuffers-and-atomics/ I’m not a big fan of JavaScript but I like parallel programming and JS has some interesting concepts of it. In addition to the event loop I’ve recently got to know the concept of Web Workers. They are real threads that execute in parallel with the main thread, and are allowed to wait and block as much as they want. Modern devices are going in the direction of having a lot of FPS and web developers want to maintain the user experience smooth.