387 private links
Get the event information of a keydown event :)
An REPL for Rust
A library to handle right and permissions.
It is very useful if both backend and frontend are written in JS.
A wrapper that throws warnings about security risks
A package.json can be provided in order to scan dependencies. It searches for risks.
A playlist of rust video about rust.
How to make this better with little css.
Inherit font-size, line-height, word-spacing, border and padding.
There are also
IndexedDB can be used to store a lot of data. It has some caveats though.
Storage:
About deletion, use soft delete to smoothen the synchronization if a user deletes a record and another one update it.
About record collection, use unique IDs (UUID v4) or property related ids with (UUID v5).
About ordering, it is easier to use fractional indices! Read more on https://www.figma.com/blog/realtime-editing-of-ordered-sequences/, or https://www.steveruiz.me/posts/reordering-fractional-indices, or use a dedicated library.
Sync is made with pull and push
Update:
- Send atomic changes from a client is the more convenient way. We can send only the model’s ID and its updated fields.
- send operations instead of changed data,
Conflict resolution:
- In some cases, last-write wins at the record field level will be enough
- in others, we strongly need a full-fledged CRDT.
Depending on the vessel (ship):
Stern (back), port (left), bow (forward), starboard (right). These directions are based on the vessel "cap".
Depending on the skiers:
"skier's Left" is based on a skier facing down the mountain.
Depending on the reader:
- inline is how a sentence is read
- block is the perpendicular of inline
- start is where the flow... starts
- end is where the flow ... ends
I find it still hard to explain and I got it with examples. Read more on mdn
block/inline and start/end can be mixed up to target a specific location. From our Latin reader perspective, it applies as follows: https://i0.wp.com/css-tricks.com/wp-content/uploads/2022/03/block-dir.png?w=720&ssl=1
It's user-centric because its language direction is respective. [...] We can embrace diversity, complexity, and unpredictability and rely on the browser engines to properly lay it out.
Why all of these? Because right, left, top, and bottom can be interpreted differently between the explainer's and the public points of view.
A clear starting point on logical properties!
I keep:
- Container query: indeed
- Scroll snap
- Grid Pile: centering everything in one cell with
display: grid; place-content: center;and in all direct children:grid-area: 1/1 - Quick circles with
inline-size: 25ch; aspect-ratio: 1; border-radius: 50%; - Logical properties :D
They are better because:
- Hum they are logical
- They are ready for language translation
So why?
- People needs to know about them
- Legacy projects that needs both syntax or a complete rewrite
- Conflicts: if a non-logical and a logical property currently affect the same thing, it’s a specificity (including source order) game.
- The rollout doesn't feel totally done: linear gradients with to left and to bottom, translate, etc...
A chart library
We care about the number of concepts that changed in a particular PR.
The smaller the PR the more likely it will be to get merged quickly
Rules:
- Don't waste your reviewer's time by showing them all your failed experiments in your Git history.
- Maintain a Git history closest to the true essence of the work done, creating many small PRs that each make one releasable change to the codebase and keeping the number of commits as low as possible.
What I can improve is to remove (fixup or squash) all these tries/little fixes that I add in the commit history.
Always a way to optimize the startup time of vite :D
Vite can transform some files before the first request, increasing the speed of the first possible interaction.
It could also be integrated to Vite core as Evan You is in favor of it https://twitter.com/youyuxi/status/1641402565631025152