News from the web #5
I hope you’re well. This time, you’ll learn about asynchronous preemption, inlining in Go and be able to read GW-BASIC source code.
Do you think that in the future computers will replace us? This is an example of code generation using OpenIA.
Source code from 10th Feb 1983 is open sourced! If you know assembly or interested in archaeology - it’s a perfect place for you. They give a brief background of the project and explain why they didn’t use C etc for it.
Microsoft published (without their will) another piece of code. The operating system is only used in a small number of systems worldwide so a source code leak isn’t a significant security issue but still :)
The guy had a simple idea: clone an open source project, change variable names to something “weird” and start selling it. The problem is that he violated the GPL.
It’s a list of good practices to keep your productivity as high as possible as the team. You’ll learn why
git blame isn’t a good tool for you, why communication matters as well as how and why record only the present day.
There are only a few well working tactics for getting the very first 1000 users. From this post, you’ll learn how the biggest apps go their first costumers. It may help you in running your own business.
WebAssembly is an interesting technology. There’s still not that much materials about it. From this link, you’ll learn how to pass basic data structures to WebAssembly like: numbers, arrays or strings.
Go: Asynchronous Preemption #golang
If you want to know a bit more about the scheduler in Go. In Go 1.14, the behaviour changed so it’s worth reading materials like that.
Dgraph, GraphQL, Schemas, and CRUD #graphql #dgraph
Quite long article about Graphs and GraphQL. I’d say it’s very basic and shows how to run a simple CRUD application using GQL and Dgraph but it can be a good starting point for experiments.
Personally, I love articles like this one. It’s very detailed but easy to understand summary of 3 bugs in Go MySQL driver that left there for a while.
Mid-stack inlining in Go #golang
Dave gives us another cool post. This time about inlining in Go. Inlining is a compiler optimisation that allows reducing the overhead of calling functions by embedding small functions into their callers. If you want to know more about it - read it.
Go had a limitation on composing interfaces. Two interfaces couldn’t be embedded into the same type if both of them contain the same function definition. Now it’s fixed.
Go and CPU Caches #golang #performance
Modern PCs have 3 level cache. Each of them has different access time and size. If you’re working on high performance applications, knowing such stuff is a must. From this article, you’ll learn how it works and how to take advantage of it in Go.
How to run gRPC app on GCP? Yeah, it can be easy. You’ll learn how to do it with protobuf.
That’s all I prepared for you this week. I hope you like it. Don’t forget to let your friends know about the newsletter and see you next week!Buy me a coffee