TLDR Index
TLDR Web Dev

TLDR WEB DEV 2024-10-15

6 sections21 entrieslinks blockcomplete parse

Parse notes

  • Subscription/account footer truncated before parsefooter_truncated

01GENERAL

02ARTICLES & TUTORIALS

HOW FIGMA MIGRATED TO KUBERNETES

Figma migrated from AWS ECS to Kubernetes because as the team's needs became more complex, they were hitting the limitations of ECS. Kubernetes, on the other hand, lets Figma avoid vendor lock-in, benefit from the open-source community, and hire engineers with previous Kubernetes experience. Figma migrated to Kubernetes over the span of multiple months, making sure to loadtest, incrementally shift traffic through weighted DNS, and use real workloads along the way.

blog.quastor.org6 min read

PYTHON 3.12 VS PYTHON 3.13 – PERFORMANCE TESTING

A benchmark of Python 3.12 and Python 3.13 found that Python 3.13 generally outperformed Python 3.12, showing a geometric mean improvement of 1.08x on the AMD system and 1.05x on the Intel system. However, Python 3.13 experienced performance drops in some benchmarks, especially in areas like coverage and regex on both systems.

en.lewoniewski.info10 min read

UPGRADING UBER'S MYSQL FLEET TO VERSION 8.0

Uber's MySQL infrastructure underwent a major upgrade from version 5.7 to 8.0 to address security concerns and improve performance. The company went for a side-by-side upgrade approach to minimize downtime, reduce risk, and allow for thorough testing. The upgrade was a multi-stage process with node replication, a soak period, traffic diversion, and primary node promotion.

uber.com14 min read

03OPINIONS & ADVICE

THAT'S NOT AN ABSTRACTION, THAT'S JUST A LAYER OF INDIRECTION

Not all abstractions in software are beneficial. While good abstractions hide complexity and simplify development, layers of indirection often masquerade as abstractions, adding cognitive overhead without real value. Abstractions are not free: they come with costs in performance and complexity.

fhur.me5 min read

CODE REVIEW ANTIPATTERNS

Reviewers can often hinder code review progress by nitpicking endlessly ("Death of a Thousand Round Trips"), using reviews as leverage for unrelated tasks ("Ransom Note"), or by constantly contradicting each other ("Double Team"). Reviewers shouldn't act as gatekeepers but keep the project's success in context.

chiark.greenend.org.uk14 min read

HTML WHITESPACE IS BROKEN

There are numerous issues with whitespace handling in HTML, from unexpected rendering inconsistencies to formatting problems. A possible solution is quoting strings in HTML to clearly differentiate between significant and insignificant whitespace. A more pragmatic solution would be adding a new HTML entity (&ncsp;) to represent a non-collapsible space.

blog.dwac.dev46 min read

04LAUNCHES & TOOLS

Sponsored

NEED TO OWN YOUR USER DATA? SURVEYJS MAKES IT EASIER THAN EVER TO BUILD YOUR OWN FORMS THAT WORK WITH ANY BACKEND

With increasingly demanding data protection rules, using online form builders is rarely worth the risk. SurveyJS UI libraries let you build a JSON-based form management system that integrates with any backend—giving you full data ownership and no user limits [11]. Includes support for advanced question types, skip logic, integrated CSS editor, PDF export, real-time analytics, and more. Get started

surveyjs.ioSponsor

VORTEX

Vortex is a toolkit for working with compressed Apache Arrow arrays in memory, on disk, and over the wire. It's designed to succeed Apache Parquet with faster random access reads and scans.

github.comGitHub repository

GOSUB

The Gosub browser engine is still under development but aims to become a standalone web browser library for parsing HTML5 and CSS3, rendering web pages, and executing JavaScript.

github.comGitHub repository

ARIA DEVTOOLS (CHROME EXTENSION)

ARIA DevTools is an open-source extension for developers that helps them build accessible web applications by highlighting missing ARIA labels, misused roles, and incomplete keyboard support.

chromewebstore.google.com

05MISCELLANEOUS

SPLITTING ENGINEERING TEAMS INTO DEFENSE AND OFFENSE

A startup founder's 4-person engineering team tackled the challenge of balancing customer support and feature development by splitting their team into "defense" and "offense" roles. Two engineers focused on long-term projects in uninterrupted blocks while the other two handled customer support, bug fixes, and other urgent tasks. This "fortress" approach allowed the "offense" engineers to be more focused and productive.

greptile.com4 min read