1. Writing mode
2. Gap in flex or grid layouts
3. Flip with transform
4. scroll-behavior: smooth;
5. Scroll-snapping with scroll-snap-type for the container and scroll-snap-align for the children
6. Resize elements both with overflow: auto; resize: both;
7. Line clamp based on how many lines is expected.
8. Linear gradient and apply the gradient on text only
9. object-fit: cover to avoid the fill effect of images. The image is not fully displayed thoughts.
10. pointer-events: none; make elements not selectable anymore.

Well I knew them 😁

What are the life and breath of the web?

• Simplicity: keep it simple, stupid!
• Modular design: read https://www.w3.org/DesignIssues/Modularity.html later

It is also necessary to realize that your own system, no matter how big and wonderful it seems now, should always be designed to be a part of another larger system.

• Tolerance: this principle can be contentious. When browsers are lax about what they expect, the system works better but also it encourages laxness on the part of web page writers.

• Decentralization: if we make a knowledge representation system which requires anyone who uses the concept of "automobile" to use the term "http://www.kr.org/stds/industry/automobile" then we restrict the set of uses of the system to those for whom this particular formulation of what an automobile is works.

• Test of Independent Invention: designing a system to be a part of an as-yet unspecified larger system

• Principle of Least Power: The reason for this is that the less powerful the language, the more you can do with the data stored in that language. The Semantic Web is an attempt, largely, to map large quantities of existing data onto a common language so that the data can be analyzed in ways never dreamed of by its creators.

In the hypertext architecture, when making a reference, such as a hypertext link, we don't just refer to an information resource. Well, we can, but we can also refer to a particular part of or view of a resource. The string which, within the document, defines the other end of the link has two parts. It has the identifier of the document as a whole, and then optionally it has a hash sign "#" and a string representing the view of the object required.

A kind is a type constructor that takes a type, and produces a new type.

The quthor recreates a map function

How to help the web? Report browser bugs with a proper reproduction.

For Walker, this disconnect is where motonormativity comes into play. “We wanted to demonstrate that when you talk about driving, people are not applying their normal values,” he said.

The Mozilla Documentation Network published a curriculum to become a frontend developer.

It seems to contain relevant resources, also for confirmed developers.

Memory safe languages.

Better metrics to measure software security. One example is through time: how fast a vendor patches to a security vulnerability.

The rustypaste project is hosted on github: https://github.com/orhun/rustypaste

A framework for embedded systems

What's your favorite solution for not-quite-component components?

With those I mean components that are more boilerplates to be expanded upon, instead of actual ready-to-go components you just tweak a few details of. Components that would grow too complex if you'd need to account for all possible interaction and design versions through props or CSS custom properties.

I think often the alternative is composability: ie. what's the minimum functionality that the cookie consent component could have? Could it be a wrapper that provides cookie-setting functionality to whatever UI component it wraps? Could it be a little JS module different components could import to reuse?

The author avoided debt, but was it worth it?