Not relatable. "Internet is not real, and strangers' opinions don't mean anything" is an ethos that I have been religiously following for as long as I can remember.
Also, I do a lot of things offline. Read physical books, run after work, and tend to stay out of the internet mob altogether. Oh, having no Instagram or Twitter helps a lot.
The faster you realize that we have a limited time on this planet the more ruthless you become with your time. My time is expensive and my employer buys it at a premium. So I am extremely judicious about what I am reading, watching and who I am interacting with.
Building the muscle takes time but it's not that hard afterwards.
icache pressure was the bane of my optimization work around 2002. Mostly because it fluctuated unpredictably even from fairly small fairly faraway changes. The system got large enough, with a long enough hot code path that was very hot, that it was almost pointless to benchmark a subsystem in isolation. Simplistic attempts to make any subsystem faster typically made the whole system slower.
In general, whatever subsystem took the cache misses showed up as the slow part, and I owned the very first component in the pipeline... It was fun to compile time disable my component to demonstrate that nothing got faster, though.
Go syntax and the Go runtime would be the perfect combo for me. Oh well...
I love Rust for what it is, but for most of my projects, I can’t justify the added complexity. Sure, there are a bunch of things I miss from the Rust world when I’m working on large-scale distsys services in Go, but introducing Rust in that space would be a recipe for disaster.
I guess the Go team knows that if they start adding everyone’s favorite Rust features, the language would become unrecognizable. So we’re not getting terser error-handling syntax or enums. Having union types would be nice too.
But I work in platform engineering, so my needs are quite different from someone writing business logic in Go. I understand that having a more expressive syntax is nice when you’re writing complex business code, but in reality, that almost always comes with a complexity/fragility tradeoff. That’s part of the reason no one wants to use Rust to write their business logic, despite it being so much more expressive.
For distsys, programming ergonomics matter far less compared to robustness and introspectability. So the Go runtime with Go syntax is perfect for this. But of course, that’s not true for all use cases.
Sorry for the rant - completely uncalled for. This is a cool project nonetheless :)
This is great. But I’ve bookmarked at least 10 of these aggregators over the years, and I never revisit any of them. Partly because I don’t have the time to browse and discover new content.
I also don’t read the blog spam from prolific writers who pop up here every two days, especially the low-quality ones constantly yapping about AI. So the number of blogs I revisit is a handful, and I have a page on my site listing them [1]. Some of the blogs I’ve listed also have backlinks to my site. It’s super simple and works fairly well for me. Plus there’s rss.
Europe doesn’t do software better - not because it can’t, but because it can’t afford to drop the GDP of a country to build a single app like some of its US counterparts can.
It might feel performative to some people, but Europe just doesn’t trust the US, and arguably shouldn’t. So it’s not about demonstrating superiority in software, but rather showing that there are alternatives you can choose if you want to.
> The quieter but bigger change: the classic encoding/json (v1) package is now backed by the v2 implementation under the hood.
This is fantastic content nevertheless.