Imagine you are working on the next big thing that runs in the browser, and it requires some heavy-duty code, which need to run fast and efficient. You remember that your friend Jack told you about WebAssembly (Wasm), which supposedly runs faster than JavaScript (JS), so you decide to check it out.
The thing you are working on involves sorting large amounts of data, so you test a pure JS implementation first.
Problem # The error handling of Go is not up to snuff compared to other languages like Java for example. Errors are treated equally to other values, meaning, they have no special type. This means, they do not carry information of origin in them. Which makes tracking down the error origin more difficult.
Let me show that to you.
package main import ( "errors" "fmt" ) func main() { err := NewErrorWithStackTrace() if err !
Introduction # You might have heard of the Option type, if not, let me introduce that concept shortly.
An Option type is data structure which either has a value or no value contained in itself, it kind of acts as a box (Schrödinger’s cat 😉). Usually, the Option type is created with a constructor such as Some(value) or None(). From there, the type usually offers methods which can act in case a value exists.
You have built this amazing React application with lots of components and everything works smooth but somehow, it feels slugish at certain places. You got that nice lazy loading that the stakeholder wanted but it slows everything down over time.
Now, how would you go ahead and improve this? Let’s have a look at profiling a React application!
Your customer has been bothering you for weeks about his project TortoiseBook, and it is nearly finished, but, the most recent complaint was about performance issues!
Did you ever run your Go code, and you felt like something was off? Ever thought this might be related to the variable scope? Then you might be onto something!
