A bit C++ and game engine focused (to be expected since this is were this kind of techniques originate from), bit very good explanation on how to have packed layouts for your objects and reduce pressure on memory allocation for data intensive tasks.
Good thinking about abstraction levels on top of a platform. It's very much focused on the Web platform but applies more generally. Good food for thought on the libraries vs framework debate, why escape hatches matter and why you want a layered architecture.
Illustrated with Rust in this case, but definitely one of the big advantages of having type systems. Adding constraints (even runtime ones) to your types make it harder for bugs to hide.
Excellent points. Don't be fooled by alluring architecture changes. Always keep the complexity in check and favor tuning what's already here or changing your use patterns to meet the performance you need.
Good reminder on how the W3C works and what it evaluates. If Web Environment Integrity would become a "standard" it'd likely be more of a "de facto" thing because a major player shoved it everyone's throat.
A good reminder on how the "five why" are just a starting pont. For proper investigation and risk management you need to go deeper.
Not as detailed as I would like on the proposed solution. A good starting point for inspiration though. Should help with geospatial and fleet management problems.
Nicely explain how to secure your webhooks step by step.
Beware of the problems coroutines might bring. Some are "obvious" and related to concurrency in general, but some are running deep in their design in C++.
Doesn't go much in depth, but this is a nice resource with interesting references to follow to dig deeper and learn mDNS.
Those who listen (not mandate) to their employees and hire whatever the location will come out on top. It'll require planning real estate ahead of course but the writing is probably on the wall.
I admit I'd love it if it made a come back. That'd be a big boost to self-hosting websites for people. Our infrastructures are not quite ready for it though.
Definitely this. There's still so much to achieve through FOSS, lots of missed opportunities. The mentioned factors clearly played a huge part in the current situation.
This is based on fingerprinting and sometimes fail. If Web Environment Integrity gets through it'll be just worse.
Excellent piece against the Web Environment Integrity proposal from Google.
Don't be fooled of the title. Yes, it concludes about an opinion piece about the latest changes in policy around RHEL. Still, it starts with a very nice retelling of the history around UNIX and computing since the 70s. This is an invaluable resource.
Indeed, too many websites or apps break or hijack basic features of the browser. To me it also shows the tension between trying to have a document browser and an application provider shoved in the same GUI.
Definitely a clever combination of two Python constructs.
Good explanations of why you might want to revert the Z axis on your projection matrices. Of course it boils down to how float precision works.
Kind of overlooking the cost of producing videos in my opinion. That being said, if you keep videos out of the picture this little article is spot on. Remote work is about more asynchronous and longer form communication first.