@mattpocockuk Daily driver for many years. Since wsl2 always have project files in Ubuntu home folder. Sync-scripts for .ssh, git and configs between Ubuntu and Windows
Would be way better use of the money than having them pile up in a few people's bank accounts, spent on excessive luxury, or whatever they do at the moment.
https://t.co/lZ9upY44Di
I need to write a "state of JS frameworks" blog article. The summary is that there's a lot of interesting things going on, with innovations happening with local-first, with View Transitions and more. But all of it is blocked by the elephant in the room: React's popularity.
Or use this CSS:
```
.log {
scroll-snap-type: y proximity;
align-content: end;
}
.log::after {
display: block;
content: "";
scroll-snap-align: end;
}
```
“… remains snapped to the bottom …unless the user has scrolled away from that edge” — https://t.co/lUaMtD32uB
As of today, we are now 6 full-time engineers working on @ladybirdbrowser! 🤯🐞
I'm so grateful to all of our sponsors, both large and small, for making this possible!
Feels like I'm living in a dream sometimes. Truly. 🌠
1/7 @webkit team, let's talk about Safari iOS. Why are features available on iPadOS stripped from iOS? Fullscreen API absence means web games can't utilize the entire screen. Is this intentional crippling of web capabilities?
@EisenbergEffect Not sure if where things run in the stack needs to influence the naming unless it's for a specific target.
But if this package is required for the framework maybe even "runtime" could be one option.
Wonder what I was doing in Helsinki last month? Here's a blog post from my colleagues at @igalia talking about some interesting things coming up in JS standardization https://t.co/Gc0UBpiae4
Releasing ✨neoqs✨, a drop-in replacement for the bloated `qs` package
🤌 3.9KB min+brotli (3x smaller than `qs`)
🚥 Zero dependencies
🎹 TypeScript. Throw away @types/qs
❎ No polyfills
🛸 ESM-first
📜 Legacy mode: ES5, CommonJS and Node 10+
🌐 Just works™ in all browsers
@Mr__Disagree @brianleroux The custom-properties api would only be the "allowed to be changed" values, start with the things that you know will change based on current knowledge, add new properties when requirements change 🙂
@Mr__Disagree @brianleroux But could potentially be based on some attributes/data-attributes as well and have the variable values be overridden in those selectors, like:
button:disabled, wc-button[disabled] {
--button-background: ...;
}
🤩 View Transitions excitement!
The Firefox team recently had a kick-off meeting to implement View Transitions.
https://t.co/327hhIkgGL
“Goal and scope of the project: Single page in H2 2024”