Tomáš Deml

A courageous developer with a passion for hard sci-fi, anime and all sorts of #queer stuff.

[Tomáš Deml @tomasdeml]

"Complexity is like a bug light for smart people. Can't resist it even though we know it's bad for us. The stuff is just so cool to work on"

[Tomáš Deml @tomasdeml]

Help Vampires: A Spotter’s Guide https://t.co/gAbsH3D47S

[Matt Boyle @MattJamesBoyle]

One really interesting thing you may not have spotted in the release notes of #golang 1.21 is the following line:

"Package initialization order is now specified more precisely"

This is quite a big change, as it impacts how the init() function works. Previously it could be difficult to know what order the init function in different packages would be run (https://t.co/jtSGbJmqEr) but this changes that. The new Algorithm is:

- Sort all packages by import path.
- Repeat until the list of packages is empty:Find the first package in the list for which all imports are already initialized.
- Initialize that package and remove it from the list.

This is a positive change, but it does mean that this is a breaking one; you should test your applications thoroughly if you are upgrading to 1.21.

Does this mean we can/should use init more?
I don't think so, no.

Init was always been seen as anti-pattern by many and some style guides such as Thanos(https://t.co/AHF7Drf6il) go as far a to say "no init". This is because they can cause global changes that have side-effects which can be difficult to track down .

The only init function I use regularly is to setup:
https://t.co/LI3ilSyrg5 (under the hood it calls init)

How do you use init functions? Does this change change the way you think about them?

[Tomáš Deml @tomasdeml]

Your Computer Should Say What You Tell It To Say https://t.co/wbAtiCIKrZ

[Tomáš Deml @tomasdeml]

Yep

[Tomáš Deml @tomasdeml]

Front-end vs Back-end 😁
#homeproject

[Tomáš Deml @tomasdeml]

Brute-forcing a macOS user’s real name from a browser using mDNS https://t.co/4FtobtuaKp

[Tomáš Deml @tomasdeml]

The great Polish Sea -or- We forgot Poland! https://t.co/VleEDXXwqy

[Tomáš Deml @tomasdeml]

GopherCon 2018: Bryan C. Mills - Rethinking Classical Concurrency Patterns https://t.co/29ZEKzUMAC

[Tomáš Deml @tomasdeml]

JavaScript Gom Jabbar https://t.co/AMWhuvw63W

[Tomáš Deml @tomasdeml]

It's alive! My first e-ink display powered by ESP32 🚀

[Tomáš Deml @tomasdeml]

css-only-chat: A truly monstrous async web chat using no JS whatsoever on the frontend https://t.co/OgQZPc24ao

[Tomáš Deml @tomasdeml]

Going through a Kubernetes training with autogenerated captions and about half are coming up like this: https://t.co/jQTmHzwpma 😂

[Tomáš Deml @tomasdeml]

Portuñol: Blending Spanish and Portuguese https://t.co/cXnUek1C8q

[Tomáš Deml @tomasdeml]

Cyberpunk 2077: Phantom Liberty Feels Like A Whole New Game https://t.co/WAtIf34NRK

[Tomáš Deml @tomasdeml]

Put an io_uring on it - Exploiting the Linux Kernel https://t.co/8RiOUcgOnF

[Tomáš Deml @tomasdeml]

io_uring disabled across Google platforms https://t.co/VQu7cChho5

[Tomáš Deml @tomasdeml]

Mind the Gap: Broken Promises of CPU Reservations in Containerized Multi-tenant Clouds https://t.co/AIMmYuhDWC

[Tomáš Deml @tomasdeml]

Freaky Leaky SMS: Extracting User Locations by Analyzing SMS Timings https://t.co/2CHM2hL9bK

[Form3 Engineering @Form3Tech]

🎙️ Our newest podcast episode is live! https://t.co/3eni8bJ6pX
Host @classic_addetz is joined by @thedevel, Director at @synadia and #nats expert. He joins us to discuss #eventdriven and #resilient microservice architectures. Then, he gives us a peek into new NATS features.

[Tomáš Deml @tomasdeml]

Interview with an Emacs Enthusiast in 2023 😂https://t.co/rMFRLMp8As