394 private links
The author tried it with PHP, but it somehow didn't work.
It can be useful to create a distinction between iterators and traversables.
I created a Cargo subcommand called cargo-wizard that simplifies the configuration of Cargo projects for maximum runtime performance, fastest compilation time or minimal binary size.
Cross-posting on multiple platform.
The project is hosted on Github: https://github.com/rknightuk/echo
It can be useful :)
- Writing mode
- Gap in flex or grid layouts
- Flip with transform
- scroll-behavior: smooth;
- Scroll-snapping with
scroll-snap-typefor the container andscroll-snap-alignfor the children - Resize elements both with
overflow: auto; resize: both; - Line clamp based on how many lines is expected.
- Linear gradient and apply the gradient on text only
object-fit: coverto avoid the fill effect of images. The image is not fully displayed thoughts.pointer-events: none;make elements not selectable anymore.
Well I knew them 😁
A kind is a type constructor that takes a type, and produces a new type.
The quthor recreates a map function
The Mozilla Documentation Network published a curriculum to become a frontend developer.
It seems to contain relevant resources, also for confirmed developers.
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?
Now I get it.
How to apply css for RSS feeds
Maybe useful for later